AUTOPATCH ARGUMENTS
apply Purpose: Tells AutoPatch whether to run in test mode.Default: y
driver Purpose: Tells AutoPatch the name of the patch driver file. This is usually used during non-interactive processing.
patchtop Purpose: Tells AutoPatch the top-level directory for the current patch. This is normally used during non-interactive processing. Values: A fully qualified directory name.
preinstall Purpose: Tells AutoPatch whether to run in pre-install mode. Pre-install mode is used to update AD utilities before an upgrade and to apply pre-upgrade patches.
uploadph Purpose: Tells AutoPatch to upload patch history information from the patch information files
AutoPatch Options
The options= argument is used to pass generic options to AutoPatch. It takes the form of a comma-separated list. Enter one option or a comma-separated list of options. For example, options=nocopyportion,nogenerateportion. As with AutoPatch arguments, there must be no space after the comma.
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. 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. checkfile provides significant performance benefits.
compiledb Purpose: Tells AutoPatch to automatically compile invalid objects in the database after running actions normally found in the database portion of the driver. Use 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.
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.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.
copyportion Purpose: Tells AutoPatch whether to run commands normally found in the copy portion of the driver.
databaseportion Purpose: Tells AutoPatch whether to run commands normally found in the database portion of the driver.
generateportion Purpose: Tells AutoPatch whether to run commands normally found in the generate portion of the driver. Use options=nogenerateportion to tell AutoPatch not to perform generate actions of the driver.
hotpatch Purpose: Tells AutoPatch to apply a patch regardless of whether the Oracle E-Business Suite system is in Maintenance mode.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, nointegrity is safe and avoids some AutoPatch overhead.
maintenancemode Purpose: Tells AutoPatch to enable Maintenance mode at the beginning of a patch session and disable it at the end (if patch application was successful). Default: nomaintenancemode
parallel Purpose: Tells AutoPatch whether to run actions that update the database in parallel (such as SQL) and actions that generate files in parallel (such as genform).
Default: parallel Comments: Oracle does not recommend changing the default, as Oracle E-Business Suite patches are tested on systems using parallel processing.
phtofile Purpose: Tells AutoPatch where to place patch history information after applying the patch.
Default: nophtofile. Use options=phtofile to tell AutoPatch to write patch history information to the patch information files in the file system ($APPL_TOP/admin/$TWO_TASK) instead of uploading it 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 information files (in $APPL_TOP/admin/$TWO_TASK) to the database during uptime.
validate Purpose: Tells AutoPatch whether to connect to all registered Oracle E-Business Suite schemas at the start of the patch. Use options=validate to validate password information for all Oracle E-Business Suite schemas. Comments: Useful for finding problems with incorrectly registered Oracle E-Business Suite schemas or schemas with invalid passwords.
apply Purpose: Tells AutoPatch whether to run in test mode.Default: y
driver Purpose: Tells AutoPatch the name of the patch driver file. This is usually used during non-interactive processing.
patchtop Purpose: Tells AutoPatch the top-level directory for the current patch. This is normally used during non-interactive processing. Values: A fully qualified directory name.
preinstall Purpose: Tells AutoPatch whether to run in pre-install mode. Pre-install mode is used to update AD utilities before an upgrade and to apply pre-upgrade patches.
uploadph Purpose: Tells AutoPatch to upload patch history information from the patch information files
AutoPatch Options
The options= argument is used to pass generic options to AutoPatch. It takes the form of a comma-separated list. Enter one option or a comma-separated list of options. For example, options=nocopyportion,nogenerateportion. As with AutoPatch arguments, there must be no space after the comma.
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. 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. checkfile provides significant performance benefits.
compiledb Purpose: Tells AutoPatch to automatically compile invalid objects in the database after running actions normally found in the database portion of the driver. Use 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.
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.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.
copyportion Purpose: Tells AutoPatch whether to run commands normally found in the copy portion of the driver.
databaseportion Purpose: Tells AutoPatch whether to run commands normally found in the database portion of the driver.
generateportion Purpose: Tells AutoPatch whether to run commands normally found in the generate portion of the driver. Use options=nogenerateportion to tell AutoPatch not to perform generate actions of the driver.
hotpatch Purpose: Tells AutoPatch to apply a patch regardless of whether the Oracle E-Business Suite system is in Maintenance mode.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, nointegrity is safe and avoids some AutoPatch overhead.
maintenancemode Purpose: Tells AutoPatch to enable Maintenance mode at the beginning of a patch session and disable it at the end (if patch application was successful). Default: nomaintenancemode
parallel Purpose: Tells AutoPatch whether to run actions that update the database in parallel (such as SQL) and actions that generate files in parallel (such as genform).
Default: parallel Comments: Oracle does not recommend changing the default, as Oracle E-Business Suite patches are tested on systems using parallel processing.
phtofile Purpose: Tells AutoPatch where to place patch history information after applying the patch.
Default: nophtofile. Use options=phtofile to tell AutoPatch to write patch history information to the patch information files in the file system ($APPL_TOP/admin/$TWO_TASK) instead of uploading it 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 information files (in $APPL_TOP/admin/$TWO_TASK) to the database during uptime.
validate Purpose: Tells AutoPatch whether to connect to all registered Oracle E-Business Suite schemas at the start of the patch. Use options=validate to validate password information for all Oracle E-Business Suite schemas. Comments: Useful for finding problems with incorrectly registered Oracle E-Business Suite schemas or schemas with invalid passwords.
