本文共 7273 字，大约阅读时间需要 24 分钟。
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=yPre-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=nOther 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=nogenerateportionMaintenance 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 SchemasIf 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
a) login as applmgr and set the environment. For the Windows environment also, you have to test that CLASSPATH contains %JAVA_TOP%, %JAVA_TOP%\loadjava.zip
b) create a PATCH_TOP directory in the Base Directory (at the same level as APPL_TOP, COMMON_TOP, etc: this is just a recommandation) for the patches which will be downloaded. If this directory exists, this step can be skipped. An OS environment variable could be created for this directory. This will be done only one time, when the first patch will be applied.
c) download the patch you want to apply in PATCH_TOP directory and unzip the patch.
d) understand the README.txt file and complete the prerequisite or manual steps. Here, if there are any patched to apply as pre-requisite, in general, is created a document with all the steps involving in the patching process and the pre-requisite patches will be applied before the initial patch.
e) assure that the PLATFORM variable environment (under UNIX, Linux, Solaris) is set
f) Shut down APPS services. The database services and the listener must be up and running.
g) Enable Maintenance Mode.
h) Start AutoPatch in interactive mode. this task must be done from the directory where the patch driver is/was unzipped. Also, respond to the adpatch prompts. If there are more drivers to apply (there is no unified drive: there could be a database (d), copy (c) or generate (g) drive) restart the adpatch and apply the other patches.
i) Review the log files. By default, the location is $APPL_TOP/admin/<SID>/log and the file is adpatch.log.
j) Review the customizations (if any). If a customization was modified by this patch, the customization must be applied again.
For the customizations please look into the $APPL_TOP/admin/applcust.txt file.
k) Disable Maintenance Mode
l) Restart APPS services
m) Archive or delete the AutoPatch backup files.
AutoPatch must be run in test mode (apply=no). The APPS services must be stopped and the Maintenance Mode must be enabled as well. To see which is the impact on the system, you can use Patch Impact Analysis in the Patch Wizard.
If this is possible the README.txt will let you know. If the patch README.txt file will not state this explicitly, that means you have to stop the APPS processes and to enable the Maintenance Mode. The help files can always be applied without stopping the APPS services.
If a patch can be applied without stopping the APPS services we have to use the option hotpatch.
More information about this subject ( ) you can get from
FROM: http://bereanstechnology.com/?q=node/44
转载地址：http://titai.baihongyu.com/