This action might not be possible to undo. Are you sure you want to continue?
1. Introduction 2. What are patches? Why to apply patch? Who will decide to apply patch? 3. Types of patches 4. Structure of a patch 5. Pre Patch Steps 6. Patching Application in interactive Mode 7. Post patch application steps 8. Controlling/Managing Patch Session 9. Patch History 10.Applying Patches in non-interactively 11.Merging Of Patches 12.Patch Troubleshooting 13.How to reduce downtime while applying patches 14.Applying Patches to Multi-node system 15.Applying Unified drivers 16.Testing a Patch Before Applying it
• AutoPatch or Adpatch is a utility that is used to apply patches and release updates. • Before AutoPatch replaces a file with one from the patch, it compares the version numbers to ensure that your file will be replaced only with a newer one. Unless adpatch is run with forcecopy on the command line: adpatch options=forcecopy • Before replacing any file, AutoPatch always makes a backup copy
2. What are patches? Why to apply patch? Who will decide to apply patch?
• Patches are oracle delivery Mechanism • Patches are the process of bug fixing and product Enhancements • Patches are Apply To bring the Unstable oracle state to stable oracle state
• The Implementation team & Oracle support services will decide to apply patches 3. Types of patches 1. 2. 3. 4. 5. 6. 7. 8. One of Patches Mini Pack Patches Family Pack Patches Rollup Patches Maintenance Pack Patches IOP(interoperability Patch) NLS Patches Diagnostic Patches
One-of, individual or Standalone These are terms used to describe an individual patch that is created to fix one particular. It is single Patch to resolve single bug Mini Pack ‘Patch Set’ was the original term used in R10. In R11 the same type of patch is now being called a ‘Mini Pack’. Both terms mean a large, cumulative patch, for a particular product, that fixes most or all bugs that have been fixed for that release and product. Mini Pack are consisting of collection one of patches Version 11i_AD_G Module name (ad) Version 11i_GL_D Module name (gl) If you want to get the additional utilities of 11.5.10 in 11.5.9 then you have to apply a mini pack
A ‘Maintenance Pack’ is a collection of all Mini Packs that are bundled together onto a set of CDs that can be ordered and easily installed by the customer • with the full installation of this type of patch.G or 11i.3 to 11. consult the NLS Installation manual. Family Packs will be named similar to: 11i. Procurement. Some examples of product families are ERP. ap.FINAP_PF.5. the 3rd digit of Applications Release will change. ont. Maintenance Pack Maintenance Pack is the term that Oracle began using for R11. then the prior Maintenance Packs do not need to be applied. while Release Update was used for R10. For more information on other variables and steps.<character set>. CRM.5) • As with Mini Packs. NLS Patches If your install has multiple languages. The American patch needs to be applied first. ar. substituting the appropriate character set for your language. fa) The same bulleted information for Mini Packs applies for Family Packs.Family Pack ‘Family Pack’ is a group of related Mini Packs products that are bundled together. 3 . and then an NLS version of the same patch needs to be applied for each language. Family pack of financial suite consist of (gl.OM_PF.A The ‘_PF’ in the name indicates it is a Family Pack and not a Mini Pack. The only difference is the naming structure. When applying the NLS patch. but there are many others. (Ex 11. be sure to set the NLS_LANG variable to AMERICAN_AMERICA. So if 11. Maintenance Packs are cumulative.5.5. or Order Management.5 is applied. and possibly some additional individual fixes that have been created after the Mini Packs. additional patches may need to be installed for each language.
or object modules. Structure of a patch WHAT DOES A PATCH LOOK LIKE? • A patch may consist of many files. in what order to apply these steps Three types of patch drivers. each with its own naming convention: • c<bugno>. (Create packages. • This file tells AutoPatch what steps need to be done to apply the patch and . These include: Patch driver files • Every patch comes with one or more patch driver files. • This file tells the user what bug it is fixing. Add a New table or View to database. or copy driver. • These are usually forms. • The patch driver file lists the files (and version numbers) included in the patch. what files are to be changed.drv).drv is the file. and runs SQL scripts and programs That updates the database. responsible for copying files and linking executables. Add a new column to a table) • g<bugno>. SQL scripts.) d<bugno>. A readme file • Every patch should come with a readme file. relinks executables. reports.txt.drv is the generation driver. usually named readme.4. and special steps the user needs to perform (if any). • The names were chosen because the order in which they must be applied is Alphabetical: c (for copying). Create new error messages. and regenerates jar files.drv is the database driver. and Message files. (This driver copies files from patch to directories. • 4 . you actually receive a compressed archive (zip format) of several files. d (for database). and generates forms. • These are files that replace the ones you have on your current system or add files that are not on your current system. • When you receive a patch. "Replacement" files • These files are listed in the file driver (c<bugno>. and g (for generation). reports.
fmb c123456.txt g123456. Scripts and executables • These are SQL scripts and executables that need to be run to apply that patch. suppose I have patch 123456. not from where the patch was unloaded.drv d123456.sql d123456. which replaces a report file in PO and includes database update steps. 5 . • These scripts often modify the database and are typically called by the database driver. For example.drv | | | | patch | 110 |________ | | Sql driver | | b123456. files are grouped by product.rdf US | POXPOMPO. I receive a compressed tar archive.drv | | | reports forms | | POXPOCPS. Patch files are grouped by directory based on their patch number.• They are organized by subdirectory within the patch directory based on where they belong on your file system.drv A few notes about this example: • The directory name for this patch is the same as the bug number we are patching. • They are organized by subdirectory within the patch directory but actually run from APPL_TOP. Within each patch. then by their location in the <PROD>_TOP directory. which expands to this: 123456 | | | po readme.
Shutdown all The Application Services. Ensure you have sufficient temporary disk space. After Downloading Patch files from Metalink. POXPOVPS.rdf is located in the po/reports Directory.drv are all at the top level of this patch. Take the backup of APPL_TOP.env To run the environment file. From 11. Log in as applmgr. This is normally <db_name>.drv. Run the environment file for the Oracle Applications product group you want to update. 6 . such as a C shell. you may have already run this file when logged in 3. • You should also have space in the operating system’s default temporary directory (usually /tmp or /usr/tmp). On the file system it is located in PO_TOP/reports directory. You should have at least 50 MB in the temporary directories denoted by APPLTMP and REPORTS25_TEMP.drv) • It is unified driver which consist of c.txt. make sure you are in a Bourne or Korn Shell and type: $ . Make sure this account is using a Bourne shell (or Korn shell on some platforms). Note that within the patch. c123456. Instance should up and running & Listener should be up and running 5. That is the directory that holds the patch files. d& g drivers Order of applying Patch • For single Node first apply ‘c’ then ‘d’ and finally ‘g’ • For Multi Node Firstly apply patch on DBtier in order ‘c’ then ‘d’ and finally ‘g’ Secondly apply same patch on Application tier only ‘c’ and ‘g’ 5.• • The readme.5.env • Depending on your setup. d123456.Pre Patch Steps 1.drv. It may not work properly if you are using other shells. 2. and g123456. COMN_TOP &DATABASE 4.9 onwards oracle has introduces U-driver (U12345. $APPL_TOP/<db_name>. 6. Copy the patch files to your own PATCH_TOP directory.
adctrl 3. Read the readme.admrgch 2. adadmin 6. adpatch .drv c123456. This information may include: • • • • Software requirements. [applmgr@testserver Applivs]$ cd /uo1/Patches [applmgr@testserver Patches]$ ls p2145632_11i_LINUX.drv These are the contents of patch dir you can see readme. Patching Application in interactive Mode: Installing a Patch Following are the basic steps to installing a patch on R11i.Now at this stage read the readme file carefully and if there are any steps to execute before starting the patch. Unzipped the patch file. if the patch is particularly large Time requirements (a patch can take anywhere from 15 minutes to several hours to run) Details Problems that are fix in this patch Tools To Know Before Applying Patches 1. It provides information you'll need to run AutoPatch. they must be executed first. such as other patches you need to apply first.zip [applmgr@testserver Patches]$ unzip p2145632_11i_LINUX. Such as applying a prerequisite patch 7 . or what Applications release you should have Disk space requirements.txt.7.txt .drv d123456.txt file.txt g123456. and then you will get directory with a patch number in that directory you will find readme.zip Now you will get a directory with patch no in this case directory name is 2145632 [applmgr@testserver Patches]$ cd 214532 [applmgr@testserver Patches]$ls po readme.
You are about to use or modify Oracle Applications product tables in your ORACLE database ’apptest’ using ORACLE executables in ’/d01/oracle/prod/8. 8 . You can be notified by email if a failure occurs. exit AutoPatch (by typing ‘ABORT’) and edit your ORACLE_HOME and ORACLE_SID or TWO_TASK variables as needed.[applmgr@testserver Patches]$ adpatch Autopatch confirms your APPL_TOP (return) Your default directory is ’/d01/appl/110’. for different instances. Please enter the email id(s) (separated by space) that notifications should be sent to [applmgr] : Some SQL scripts perform row set processing. Auto patch ask for your logfile name AutoPatch records your AutoPatch session in a text file you specify. Do you wish to activate this feature [Yes]? You chose to be notified by email when a failure occurs.0. Some customers may have multiple APPL_TOPs. Is this the correct APPL_TOP [Yes]? This is just confirming your APPL_TOP. You can set the number of rows these scripts process. Filename [adpatch. Please enter the batchsize : AutoPatch asks you to confirm the database and database home directory.5’.log You can receive an email message if AutoPatch encounters a failure.log]: Default name is adpatch. Is this the correct database [Yes]? If these values are not correct. and this helps prevent someone from accidentally applying a patch to the wrong APPL_TOP. Enter your AutoPatch log file name or press [Return] to accept the default file name shown in brackets.
And at the end a success message is displayed. AutoPatch may have written informational messages to the file /d01/appl/110/admin/V1103/log/adpatch.drv.drv]: • • This is usually c<bugno>. Log and Info File sync point: Thu Apr 20 2000 10:29:13 Autopatch is exiting successfully. AutoPatch takes over. Please enter the name of your AutoPatch driver file [patch... or g<bugno>. determine to installation configuration.Connected successfully.. Enter the directory where your Oracle Applications patch has been unloaded The default directory is [d01/app1/110/patches123456]: AutoPatch asks for the name of your patch driver file.AutoPatch asks for the SYSTEM password. AutoPatch then validates the ORACLE usernames and passwords for Applications products.lgi 9 . AutoPatch is complete..Connected successfully.. The ORACLE username specified below for Application Object Library uniquely identifies your existing product group: APPLSYS Enter the ORACLE password of Application Object Library [APPS]: APPS AutoPatch asks for the directory that holds the patch files.. and asks you if you want to continue. AutoPatch tells you what patches you are about to apply.drv. what products they will change. Enter the password for your’SYSTEM’ ORACLE schema: manager Connecting to SYSTEM. It then determines the username for your Application Object Library user AutoPatch needs the password for your ’SYSTEM’ ORACLE schema in order to Connecting yourSYSTEM. d<bugno>. • • AutoPatch displays messages to show its progress..... At this point.drv.
adpatch asks and confirms the same things as in a regular run. Restarting a failed patch. Enter No to continue with your previous AutoPatch session. You can be notified by email if a failure occurs. you answer with yes. [No]: • If you answer this question with No. adpatch asks and confirms the same 10 . Do you wish to activate this feature [Yes]? • After this question. APPL_TOP is set to /d01/appl/110 Backing up restart files. 2. if any….log For errors. • Autopatch will ask several questions that have to be carefully answered. • If you answer this question with Yes.Done. You are about to apply a patch to the installation of Oracle Applications in your ORACLE database 'atlcol06_v1103' using ORACLE executables in '/db02/webhome/v1103'. you answer with No and the following question will come up. Adpatch will ask you to confirm the database and database home directory. you will continue with the following question. If you want to continue. If you don’t want to continue. Do you wish to continue with your previous AutoPatch session [Yes]? 1.You should check the file /d01/appl/110/admin/V1103/log/adpatch. Your previous AutoPatch session did not run to completion. Is this the correct database [Yes]? • After this question. you will continue with the old adpatch session as described above.
Restrict access to these files after you've confirmed the patch was successful. Clean up or read-protect log/. • You should check your main log file (adpatch. Take backup Immediately III.log. you can delete backup copies of files (ones that end in O) to free up disk space. I. and out/ directories under the admin base directory.4 patch History going to be located in APPL_TOP/admin/adptch. "ORA-".log. adwork*. "PLS-". adpatch. Post patch application steps There are a few post-AutoPatch steps to complete.5. you should check the log files for errors • Log files are located in APPL_TOP/admin/<db_name>/log. This contains messages on actions that AutoPatch did not perform. and others). Run the form or report that you have generated by applying patch to see Weather it is working fine or not IV Remove obsolete file (Once you're sure the patch works. "FRM-". Perform manual update steps • Check your readme. • Log. admvcode. • Make all searches case insensitive Look for "Error:" (with the colon) and not "Error" Re-run AutoPatch as necessary. and "REP-". Patch History In prerelease 11. • AutoPatch also produces an informational log file. After running AutoPatch. .7.log. "APP-". restart/.txt file for any manual update steps you might need to perform at this time. by default) as well as other files generated by AutoPatch (such as adrelink. 8. Search for words like "Error:".log. output.txt Now it is going to store in database tables I AD_APPLIED_PATCHES (this will give applied patch no’s) II AD_PATCH_DRIVERS (this will give applied patch drivers) III FND_PRODUCTS_INSTALLATIONS (this will give you patch set or mini pack level &Family pack level) • 11 . "Warning". and restart files record passwords to your Oracle Applications products.lgi. Compile Invalid Objects II.
this will give you information what are all patches you have applied. Applying patches in non-interactively If you want apply a patch non-interactive mode then you have to take help of a file called adalldefaults.txt [applmgr@testserver Applivs]$adpatch defaultsfile=$APPL_TOP/admin/<SID>/def./patchset.txt. This will compare patch level that you have with available patches on Metalink and give the comparison .txt to APPL_TOP/admin/<SID>/def.log interactive=no patchtop=/u1o/patches/1234 adworkers=5 Now it will apply c.log interactive=no patchtop=/u1o/patches/1234 adworkers=5 driver=c1234.A part from this oracle has given a shell script which will be available on Metalink (patchset.txt logfile==p1234.drv :wq 12 .txt which is in APPL_TOP/admin/adalldefaults.you had to download this script from Metalink Login as applmgr $ . d & g all three driver and it will not going to ask anything You can make a shell script of above command line executable and you can run that file Ex: [applmgr@testserver Applivs]$ vi patch.txt logfile==p1234.sh adpatch defaultsfile=$APPL_TOP/admin/<SID>/def.txt \ $APPL_TOP/admin/<SID>/def. You have to copy this file to from APPL_TOP/admin/adalldefaults.sh 9.sh).txt This file is going to pass as argument when you run the adpatch [applmgr@testserver Applivs]$cp $APPL_TOP/admin/adalldefaults.
How to merge the patch Merging only compatible patches Patches of different platform. d &g) (2) unified driver (u) We merge can’t these two drivers Login as applmgr [applmgr@testserver Applivs]$ cd /u01/Patches [applmgr@testserver Applivs]$admrgpch –s source_dire_name -d dest_dir_name \ -merged_name= new_patch_name -s = this option is used specify name of your source directory that contains patches which are to be merged in the above case 12345. different versions and different release cannot be merged Particularly NLS patches are going to be merged PATCH_TOP Source directory destination directory 12345 23456 34567 In source directory we have 3 patches now we are going to merge those three patches and put them in destination directory You should be at patch top level for merging patches for merging patches Use admrgpch There two types of drivers (1) split drivers (c./patch.sh It will only apply c driver not d and g 10.[applmgr@testserver Applivs]$ . 23456& 34567 -d = this option is use to define the name of destination directory where your patches is going to kept after merging 13 .
which requires prerequisite patch to complete Then you start one more session rename FND_INSTALL_PROCESS & AD_DEFFERED_JOBS. 6. Make sure table fnd_install_process_bak exits and has records : Select count (*) from fnd_install_process_bak. 2. drop the associated indexes of these tables and go to $APPL_TOP/admin/SID/ there you will find restart directory rename it. Now apply The pre-requisite or recommended patches rename back those two tables and restart directory Now if you start running the adpatch it will start applying the original patch that has failed Steps: 1.log for troubleshooting . Scenario 2 Suppose if your adpatch session has successfully completed running ‘c’ driver and it got hanged While running your‘d’ driver . Create table ad_deffered_jobs_bak as select * from ad_deffered_jobs Make sure table ad_deffered_jobs_bak exits and has records Select count (*) from ad_deffered_jobs_bak. Login to sqlplus as users applsys Make sure the FND_INSTALL_PROCESS exits: create backup table of the FND_INSTALL_PROCESS tables: Create table fnd_install_process_bak as select * from fnd_install_process 4.txt\ logfile=<logfile_name> Patchtop=/u01/Patches/ dest_dir_name interactive=no Patch Troubleshooting Basic patch troubleshooting If’d’ driver has failed then the adctrl utility will specify which driver has failed If it tells that adworker02 has failed Then go and refer adworker02. If your application is 11.8 then backup the AD_DEFFERED_JOBS table.5. 14 .they are located in $APPL_TOP/admin/<SID>/log.-merged_name=we are specifying name of patch which we get after merging those three patches Now we are running merge patch [applmgr@testserver Applivs]$ cd /u01/Patches/dest_dir_name [applmgr@testserver dest_dir_name]$adpatch defaultsfile=$APPL_TOP/admin/SID/def. 3. 5.
Login to sqlplus as apps and create a synonym or fnd_install_process: Create synonym fnd_install_process for applsys. Login to sqlplus as applsys. COMN_TOP which you have backed before applying patch If ‘d’ has failed restore APPL_TOP. Drop the tables ad_deffered_jobs & fnd_install_process and associated indexes Drop table ad_deffered_jobs Drop table fnd_install_process 8. go to $APPL_TOP/admin/<sid> 10. 6. 4. in patch directory it will create a backup directory which contains the files that ‘c’ driver is going to change If ‘c’ has failed restore APPL_TOP. Now when you run adpatch it will start applying the original patch that failed. Backing out when a Patch fails Suppose if ‘c’ driver has failed.5. 2. COMN_TOP & DATABASE. Change directories to the location where the restart files are stored: cd $APPL_TOP/admin/<sid> Rename the backed up restart directory: mv restart_bak restart 5. Now apply new Patch After new Patch completes successfully 1. Login as applmgr user 9. 3.7. 7.8. Recreate the fnd_install_process table: Create table fnd_install_process as select * from fnd_install_process_bak. recreate the AD_DEFERRED_JOBS table: Create table ad_deffered_jobs as select * from ad_deffered_jobs_bak. which you have backed before applying patch How to reduce downtime while applying patches Using a Staged Applications System 15 . Rename restart directory 11. Log in to UNIX as the applmgr user. fnd_install_process. If you are running Applications Release 11.
AutoPatch will correct the historical information. you will have to recreate the staged system. and updating the production system. Complete the following tasks: 1. ■ You must have different Applications system names for the staged and the production systems. See Using AutoConfig to Manage 16 . do not apply any other patches to the production system. Note the following conditions: ■ The APPL_TOPs in the staged system must have the same name as the APPL_TOPs in the production system to ensure consistency of the patching history in the production system. If you do. and each APPL_TOP to use as the staged system. If necessary. Update production system snapshot. ■ The database in the staged system should have a different <SID> to avoid accidental connections to the production system. it must have the same APPL_TOP names. Each physical APPL_TOP in the production system must exist in the staged system. Run the task on all APPL_TOPs in your system. you are ready to update the production system. use the s_ifile AutoConfig variable to create a tnsnames file in the staged system with entries for the production system.Action There are several phases to creating a staged system. consider merging the patches to further reduce downtime. the application tier components. You must be able to connect to the production database from the staged system. If you need to apply more than one patch. Apply patches to the staged system: You patch the staged system in the same way that you patch any other system by using AutoPatch to apply the patch drivers. Passwords. 2. Update the production database: Once the patching is complete on the staged system. While you are completing this phase. Complete prerequisite tasks: A staged system must be an exact duplicate of the production system. Create a clone of the production database. and any process or service-related parameters can be changed as well to further reduce risks. Verify that your system current view snapshot is up-to-date by running the Maintain Current Snapshot task in AD Administration. ports. patching it. Create the staged system. When patch history data is imported from the staged system to the production system.
Apply the database driver for the patch you wish to apply.log $COMMON_TOP/html/iby_error. you can complete this task while the production database is being updated. ■ The COMMON_TOP directory. shut down all services on the production system. Make sure the database name in the AutoPatch prompt is correct. To minimize downtime. You can use a simple copy or a utility such as rdist. Set the environment.cfg $COMMON_TOP/html/US/ICXINDEX. you can use a distfile to exclude these files. you must copy each one to the production system.htm $COMMON_TOP/html/_pages $APPL_TOP/log/ $APPL_TOP/patches/ $COMMON_TOP/html/iby_debug. If you applied multiple patches to the staged system. Run AutoPatch. Update the production APPL_TOP: The production APPL_TOP must be synchronized with the staged APPL_TOP. which may reside outside the APPL_TOP. ■ If you share a single APPL_TOP. and enable maintenance mode.System Configurations with Oracle Applications 11i (OracleMetaLink document 165195. and environment scripts are specific to an APPL_TOP. you need to synchronize only one system. Certain configuration files. merge the database drivers for each patch before applying it to the production system. 2.1). nogenerateportion to the AutoPatch start command (adpatch). Do not copy the following files and directories when you copy the APPL_ TOP: $COMMON_TOP/util/apache $COMMON_TOP/admin/scripts $APPL_TOP/admin/<SID> $FND_TOP/out $FND_TOP/log $COMMON_TOP/html/bin/appsweb. Then. complete the following tasks: 1. must be updated for each APPL_TOP. Create a complete production patch history: 17 . log directories. Note these conditions: ■ If your system contains multiple APPL_TOPs. For patches with a unified driver.log If you use the rdist utility. add the argument options=nocopyportion.
pl (located in AD_TOP/bin). To create a complete copy of the patch history on the production system.log to ensure the data files represent the patch runs you wish to export. We recommend you export patch history separately for each APPL_TOP. The script generates two data files for each run of AutoPatch on the staged APPL_ TOP. you must export patch history for each APPL_TOP in the staged system and import if for the corresponding APPL_TOP in the production system.pl -help to see all valid options for running the utility. Verify export data. Check adphmigr. Specify nodatabaseportion=Y on the command line to ensure that the patch history data for the database portion of the patches applied is not exported. Users do not have to log off the production system while you perform the import and export tasks. For example: perl $AD_TOP/bin/adphmigr. Export applied patches information. and the database portion of the patch history is stored in both the staged system database and the production system database.pl utility to load the applied patches information from the copy and generate portions of all patches into the production database. Import applied patches information.pl userid=apps/apps \ startdate=’2003/10/10 00:00:00’ enddate=’2003/14/10 00:00:00’ \ appsystemname=stage appltopname=tafnwl nodatabaseportion=Y 2. Run adphmigr. The next time you run AutoPatch in this APPL_TOP. and that the start and end times specified did not include any unwanted AutoPatch runs. 18 . Type adphmigr. or before you use any patch-related Oracle Applications Manager (OAM) features. one for java updates and one for all other patch actions. Finish consolidating the production system patch history before you apply any additional patches to it. the copy and generate portions of the patch history for patches applied to the staged system are stored in the staged system database. 3. copy the data files extracted for the corresponding APPL_TOP in the staged system to the $APPL_TOP/admin/<SID> directory. use the adphmigr. it will automatically upload these files. Complete these tasks: 1.At this point. For each patch applied to the staged system. as you will need to import it separately. For each APPL_TOP in the production system.
servers are installed on more than one node. 2. au. 4. Unzip the patch in a designated patch top directory. Applying patches to Multi Node system In a multi-node system. 9. 8. Any changes made to a shared APPL_TOP are immediately available on all nodes. exit AutoPatch by typing abort at the patch driver file prompt. 6. The adphmigr. You can maintain the APPL_TOPs separately. At that point. 5. Apply the copy and database drivers to the APPL_TOP on node 1 (administration and concurrent processing). 3. Start the concurrent managers. 19 . answer the prompts until you are prompted for the name of the patch driver file. Applying Unified drivers Action Perform the following steps: 1. 12 Apply the generate driver to the APPL_TOP on node 2. and fnd) and all product directories are installed under the APPL_TOP on all nodes. 10 Apply the copy driver to the APPL_TOP on node 2 (forms and Web servers). Shut down services. Note: The FNDLOAD method of transferring patch history is no longer recommended. one with an administration server and a concurrent processing server. 2. ad. Start services and restart the Web server. except for any node that contains only a RDBMS. Respond to the AutoPatch prompts. Action Complete the following steps. 1.pl method is more efficient and easier to use. or you can configure your system to share an APPL_TOP. Complete prerequisite or manual steps. Log in as applmgr and set the environment. and the other with a forms server and a Web server.To load the files immediately. if necessary. The core technology directories (admin. the APPL_TOP and the COMMON_TOP file systems are installed on a shared disk resource mounted to each node in the system. Enable Maintenance Mode. Start AutoPatch. In a shared APPL_TOP system. run AutoPatch interactively. 7. The example assumes a system with two nodes. 13 Disable Maintenance Mode. Unzip the patch in a designated patch top directory. Log in as applmgr and set the environment. 11 Apply the generate driver to the APPL_TOP on node 1. 14.
Complete steps 9 and 10 in the Applying a Patch interactively section. and sequences (optional). When directed to run AutoPatch. Follow the steps in the Applying a Patch Interactively 2. Respond to the AutoPatch prompts. 13. applying only the database portion of the patch. Restart server processes. Delete or archive AutoPatch backup files . Shut down services. At the prompt for the driver name. 10. The command line syntax should look like this: $ adpatch options=nocopyportion. Review log files. 12. Enable Maintenance Mode. 6. 20 . 11. 8. add the test mode argument to the command line: adpatch apply=no 3. functions. specify the unified (u) driver.3. Review customizations. Type the adpatch command as indicated in Step 6. Complete prerequisite or manual steps. You must also complete steps 12 and 13 if you shut down your servers and enabled maintenance mode before you applied the patch. nogenerateportion 7. 9. nogenerateportion. 5. Disable Maintenance Mode. Testing a Patch before Applying It Action Complete the following steps: 1. adding the following options on the command line: nocopyportion. Pre-allocate space for packages. 14. AutoPatch runs the driver. 4.