ADPATCH Options
ADPATCH Options
After having talked about the best practices related to applications patching. In today’s post i will talk about some frequently used options with adpatch. It is important to note here that the options described here are for information purposes only and you must understand them completely before using them on your system. Also any special instructions specified in the patch readme file automatically overrides the information cointained in this post.
You can execute adpatch by logging in as the applications OS user and sourcing the appropriate environment file.
#su - applmgr
$cd SAMAPPL
$. ./APPSORA.env
$adpatch
By default adpatch does not take any clause, but there are some clauses that you could use with adpatch
Running a patch in test mode
You can use the apply clause with adpatch to specify weather to run the patch in TEST mode or not, when you run the patch in test mode it does not do any changes but runs generates a log fiule with all the actions it would have performed.
$adpatch apply=n|y
The default is apply=y
Pre-install Mode
You can also run a patch in pre install mode, this would be done normally during an upgrade or consolidated update. When a patch is applied in a preinstall mode the all the AD utilities are updated before the upgrade or update.
$adpatch preinstall=y
The default is preinstall=n
Other Options with adpatch
You can use the options clause to specify some of the other options available with adpatch.
Autoconfig
You can use the options=noautoconfig top specify autopatch that you do not wish to run autoconfig as a part of the patch application. This can be useful when applying a large number of patches when they are not merged. By default autoconfig is run as a part of adpatch.
$adpatch options=noautoconfig
Checkfile
The chekfile option of adpatch tells adpathc to check for already executed exec, SQL, and exectier commands.You can use options=nocheckfile skips this check, however this can cause performance overheds so should be used only when specified.
$adpatch options=nocheckfile
Compile Database
By defaulty autopatch compiles the invalid objects after the patch application, in case you wish not to do so you can specify options=nocompiledb along with autopatch.
$adpatch options=nocompiledb
Compile JSP
By defaulty autopatch compiles the java server pages (jsp) after the patch application, in case you wish not to do so you can specify options=nocompilejsp along with autopatch.
$adpatch options=nocompilejsp
Copy Portion
If you wish adpatch not to execute the commands present in the copy driver portion of the patch you can use the options=nocopyportion.
$adpatch options=nocopyportion
Database Portion
If you wish adpatch not to execute the commands present in the database driver portion of the patch you can use the options=nodatabaseportion.
$adpatch options=nodatabaseportion
Generate Portion
If you wish adpatch not to execute the commands present in the generate driver portion of the patch you can use the options=nogenerateportion
$adpatch options=nogenerateportion
Maintenance Mode
If you wish to apply a patch regardless of the system being in maintenance mode you can use options=hotpatch.
$adpatch options=hotpatch
Integrity Check
If you wish to check the integrity of the patch you can use the options=integrity. Since metalink patches are pre checked for their integrity it is generally not required to do an explicit check and the default value is nointegrity.
$adpatch options=integrity
Maintain MRC
You can use the maintainmrc option to specify weather you wish adpatch to execute the Maintain MRC schema as a part of the patch application or not. By default maintain MRC is done for standard patches and is disbaled for tarnslation and documentation patches.
$adpatch options=nomaintainmrc
Pre requisite Patch Check
If you wish adpatch not to check for pre requisite patches before application of the main patch you can use options=noprereq.By default pre requsite checking is enabled.
$adpatch options=noprereq
Validate Schemas
If you wish adpatch to explicitly validate all the registed schems by making a connection you can use options=validate. By default this validation is not performed.
$adpatch options=validate
Java Classes
If you wish adpatch not to copy new java classes from the patch you can use options=nojcopy.By default java classes are copied.
$adpatch options=nojcopy
Force Copy
By default adpatch copies the files without check the version of the existing files already present on the system.If you do not wish the newer version of the file to be replaced by the older version contained in the patch use options=noforcecopy.
$adpatch options=noforcecopy
Relinking
If you wish adpatch not do perform relinking you can use options=nolink.
$adpatch options=nolink
Generate Forms
If you wish adpatch not to generate the forms files you can specify options=nogenform.
$adpatch options=nogenform
Generate Reports
If you wish adpatch not to generate the report files you can specify options=nogenrep.
$adpatch options=nogenrep
You could specify multiple options at the command line using the , delimiter.
$adpatch options=hotpatch,nojcopy
Comments
Force Copy
By default adpatch copies the files without check the version of the existing files already present on the system.If you do not wish the newer version of the file to be replaced by the older version contained in the patch use options=noforcecopy.
Correction
1. By Default adpatch Checks the Version and copies the files except for certain kind of Image Files and GIF Files.
2. forcecopy is used for copying gif/jpg image files
forcecopy/noforcecopy is not for bypassing version checking or anything.
Posted by: Murali | January 11, 2007 02:36 AM
Hi Sam,
Your blog is quite informative, especially for beginner Apps DBAs. Keep up the good work.
Regards,
Rajesh.M.K
Posted by: Rajesh.M.K | January 16, 2007 12:17 PM
Hi Sam,
Your blog is quite informative, especially for beginner Apps DBAs. Keep up the good work.
Regards,
Rajesh.M.K
Posted by: Rajesh.M.K | January 16, 2007 01:07 PM
Hi Sam,
Your blog is quite informative, especially for beginner Apps DBAs. Keep up the good work.
Regards,
Rajesh.M.K
Posted by: Rajesh.M.K | January 16, 2007 01:16 PM
Thanks Rajesh(thrice)
Murali, Thanks for pointing that out i will test it on our systems and make the put the correction in place as soon as possible.
I apologize for the delay in replying and publishing your comments mainly due to my vacation and also due the large number of junk comments i am getting.. its a pain picking the genuine ones out ;)
Sam
Posted by: Sam | January 16, 2007 09:56 PM
Hi Sam,
How to enable HTML interface to an exiting 11.5.10 CU2 Financials implementation?
Regards
Tiru
Posted by: Tiru | January 23, 2007 08:51 PM
Hi Sam,
I started reading your blog recently and I must say this is the best for any apps user!
I've a query..
How can we deploy XML Publisher reports between instances? I've read about FNDLOAD with xdotmpl.lct to get the metadata & XDOLoaderto move the physical files.. Could you please elaborate on how this can be done? Do we need to run an explicit FNDLOAD with afcpprog.lct to move the concurrent program information? What do you mean by "moving the physical files like rtf using XDOloader"
-Vani
Posted by: Vani | January 25, 2007 01:05 PM
Excellent web site, extremely useful for all admins.Appreciate your efforts - Shiva
Posted by: shiva | February 27, 2007 09:09 PM