Patching Note
Patching Note
in existing program/product/software.
For Basic Apps patches terminology & other related details please refer to the
following links:
http://onlineappsdba.com/index.php/2006/08/10/oracle-apps-patch-basics/
http://onlineappsdba.com/index.php/2006/08/11/oracle-apps-patch-basics-ii/
Before going on steps for patching just a brief on Maintenance Mode, Maintenance
Mode is mode of operation introduced with AD.I.2, in which the oracle application
system is made accessible only for patching activities. Greatly improves
performance by minimizing downtime.
If you wish to apply patch without putting applications in maintenance mode (for
small patches) use options=hotpatch with adpatch.
STEP 1 :Before applying a patch you must check whether the patch is already there
or not. For this we query the database:
If you have downloaded the patch at desktop then move it to directory where you
want it to unzip.
This will unzip the patch in current directory & will make the required patch
directories & sub directories.
Select option 5. The status of maintenance mode is displayed at the top of change
maintenance mode menu.Again it will show following options & ask for choice:
STEP 5: Run autopatch from the patch directory by entering the following command:
$ adpatch
After this answer the questions of autopatch. As autopatch finishes its tasks, it
writes timing information to the AD timing report for jobs running in parallel (if
any ) and reminds you to run the log files for any errors.
If you don#t see the #autopatch is complete# message at the end of the Autopatch
log file, Autopatch did not complete successfully.
The most important step after autopatch completes is to check the log files for any
errors that may occurred during the patching process. Check the main Autopatch log
file first,then additional log files as necessary.
The default name of main autopatch log file is adpatch.log .The file is located in