Your SlideShare is downloading. ×
Adpatch options
Adpatch options
Adpatch options
Adpatch options
Adpatch options
Adpatch options
Adpatch options
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Adpatch options

128

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
128
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. ADPATCH OptionsYou can execute adpatch by logging in as the applications OS user and sourcingthe appropriate environment file.#su – applmgr$cd SAMAPPL$. ./APPSORA.env$adpatchBy default adpatch does not take any clause, but there are some clauses thatyou could use with adpatchRunning a patch in test modeYou can use the apply clause with adpatch to specify weather to run the patch inTEST mode or not, when you run the patch in test mode it does not do anychanges but runs generates a log fiule with all the actions it would haveperformed.$adpatch apply=n|yThe default is apply=yPre-install ModeYou can also run a patch in pre install mode, this would be done normally duringan upgrade or consolidated update. When a patch is applied in a preinstall modethe all the AD utilities are updated before the upgrade or update.$adpatch preinstall=yThe default is preinstall=n
  • 2. Other Options with adpatchYou can use the options clause to specify some of the other options availablewith adpatch.AutoconfigYou can use the options=noautoconfig top specify autopatch that you do notwish to run autoconfig as a part of the patch application. This can be usefulwhen applying a large number of patches when they are not merged. By defaultautoconfig is run as a part of adpatch.$adpatch options=noautoconfig CheckfileThe chekfile option of adpatch tells adpathc to check for already executed exec,SQL, and exectier commands.You can use options=nocheckfile skips thischeck, however this can cause performance overheds so should be used onlywhen specified.$adpatch options=nocheckfileCompile DatabaseBy defaulty autopatch compiles the invalid objects after the patch application, incase you wish not to do so you can specify options=nocompiledb along withautopatch.$adpatch options=nocompiledbCompile JSPBy defaulty autopatch compiles the java server pages (jsp) after the patchapplication, in case you wish not to do so you can specifyoptions=nocompilejsp along with autopatch.$adpatch options=nocompilejsp
  • 3. Copy PortionIf you wish adpatch not to execute the commands present in the copy driverportion of the patch you can use the options=nocopyportion .$adpatch options=nocopyportionDatabase PortionIf you wish adpatch not to execute the commands present in the database driverportion of the patch you can use the options=nodatabaseportion .$adpatch options=nodatabaseportionGenerate PortionIf you wish adpatch not to execute the commands present in the generate driverportion of the patch you can use the options=nogenerateportion$adpatch options=nogenerateportionMaintenance ModeIf you wish to apply a patch regardless of the system being in maintenance modeyou can use options=hotpatch .$adpatch options=hotpatchIntegrity CheckIf 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 notrequired to do an explicit check and the default value is nointegrity.$adpatch options=integrityMaintain MRCYou can use the maintainmrc option to specify weather you wish adpatch to
  • 4. execute the Maintain MRC schema as a part of the patch application or not. Bydefault maintain MRC is done for standard patches and is disbaled for tarnslationand documentation patches.$adpatch options=nomaintainmrcPre requisite Patch CheckIf you wish adpatch not to check for pre requisite patches before application ofthe main patch you can use options=noprereq .By default pre requsitechecking is enabled.$adpatch options=noprereqValidate SchemasIf you wish adpatch to explicitly validate all the registed schems by making aconnection you can use options=validate . By default this validation is notperformed.$adpatch options=validateJava ClassesIf you wish adpatch not to copy new java classes from the patch you can useoptions=nojcopy.By default java classes are copied.$adpatch options=nojcopyForce CopyBy default adpatch copies the files without check the version of the existing filesalready present on the system.If you do not wish the newer version of the file tobe replaced by the older version contained in the patch useoptions=noforcecopy .$adpatch options=noforcecopy
  • 5. RelinkingIf you wish adpatch not do perform relinking you can use options=nolink .$adpatch options=nolinkGenerate FormsIf you wish adpatch not to generate the forms files you can specifyoptions=nogenform .$adpatch options=nogenformGenerate ReportsIf you wish adpatch not to generate the report files you can specifyoptions=nogenrep .$adpatch options=nogenrepYou could specify multiple options at the command line using the , delimiter.$adpatch options=hotpatch,nojcopy
  • 6. autoconfig Purpose: Tells AutoPatch to run AutoConfig automatically. Default: autoconfig. Use options=noautoconfig if you are applying a number of patches in sequence and want to run AutoConfig once, after applying the last patch of the sequence. Comments: The more common method is to merge the patches first with AD Merge Patch.checkfile Purpose: Tells AutoPatch to either skip running EXEC, SQL, and EXECTIER commands if they are recorded as already run, or to record them as having run after running them. Default: checkfile. Use options=nocheckfile to turn off the checkfile feature. Comments: checkfile provides significant performance benefits.compiledb database after running actions normally found in the database driver. Default: compiledb for standard patches. nocompiledb for standard patch translations, documentation patches, and documentation patch translations. Use options=nocompiledb to save time when multiple non-merged patches are applied in a maintenance window. Comments: Merging multiple patches and applying a single merged patch is usually a better strategy.compilejsp Purpose: Tells AutoPatch whether to automatically compile out-of-date JSP files. JSP files are only compiled if the patch contains copy actions for at least one JSP file. Default: compilejsp for standard patches. nocompilejsp for standard patch translations, documentation patches, and documentation patch translations. Use options=nocompilejsp to save time when multiple non-merged patches are applied in a maintenance window. Comments: Merging multiple patches and applying a single merged patch is usually a better strategycopyportion Purpose: Tells AutoPatch whether to run commands normally found in a copy driver. Default: copyportion. Use options=nocopyportion to tell AutoPatch not to perform copy driver actions. Comments: Useful mostly with unified drivers.databaseportion Purpose: Tells AutoPatch whether to run commands normally found in a database driver. Default: databaseportion. Use options=nodatabaseportion to tell AutoPatch not to perform database driver actions. Comments: Useful mostly with unified drivers.generateportion Purpose: Tells AutoPatch to apply a patch regardless of whether the Oracle Applications system is in maintenance mode. AutoPatch aborts the patching session if maintenance mode is disabled and the options=hotpatch command is not used.
  • 7. Default: nohotpatch.integrity Purpose: Tells AutoPatch whether to verify that the version of each file referenced in a copy action matches the version present in the patch. Default: nointegrity Comments: Using options=nointegrity is safe and avoids some AutoPatch overhead.parallel Purpose: Tells AutoPatch whether to run actions that update the database in parallel (like sql) and actions that generate files in parallel (like genform). Default: parallel Comments: We do not recommend changing the default, as Oracle Applications patches are tested on systems using parallel processing.phtofile Purpose: Tells AutoPatch whether to upload patch history information to the database after applying the patch or to write it to the patch history files in the file system. Default: nophtofile Use options=phtofile to tell AutoPatch not to upload patch history information to the database. Comments: Using phtofile allows you to defer the uploading of patch history information to the database until after the system downtime. Use the adpatch uploadph=y command to upload patch history information from the patch history files to the database during uptime.prereq Purpose: Tells AutoPatch whether to check that prerequisite patches have been applied prior to running patch driver files that contain actions normally found in the copy driver. Default: noprereq Use options=prereq to turn on prerequisite patch checking. Comments: options=prereq prevents you from applying a patch without first applying all required prerequisite patches.validate Purpose: Tells AutoPatch whether to connect to all registered Oracle Applications schemas at the start of the patch. Default: novalidate. Use options=validate to validate password information for all Oracle Applications schemas. Comments: Useful for finding problems with incorrectly registered Oracle Applications schemas or schemas with invalid passwords.

×