Sie sind auf Seite 1von 3

adpatch options

Few of our dbas are still not clear about the helpful features of adpatch utilit
y with command line options.If you are in a production downtime to do some patch
ing activity, especially for some rollup upgrade, your downtime will end up with
series of pre and post patches.
In Such a scenario, it is always helpful to use command line options, and never
forget to use prereq option, because this will perform prerequisite patch checki
ng prior to running patch driver files. Default value is noprereq. There is anot
her thing I noticed. We seem to be able to apply a patch using adpatch many time
s, there is no warning given by adpatch that the patch is already applied. If yo
u use prereq option, issue can be avoided
Here are adpacth options you can use. Always use everything in command line form
at, so that you can reduce downtime by avoiding prompt value each time.
adpatch help=y
adpatch help=y
usage: adpatch [help=y]
adpatch Pre-Install Mode
[preinstall=y|n]
adpatch Test Mode
[apply=y|n]
adpatch Non-Interactive mode
[defaultsfile=<$APPL_TOP/admin/SID/defaultsfile>]
[logfile=][interactive=y|n][workers=]
[patchtop=][driver=][restart=y|n]
[abandon=y|n][wait_on_failed_job=y|n]
adpatch
[localworkers=][workers=]
[printdebug=y|n][parallel_index_threshold=]
[order=] [flags=][options=]
adpatch Upload Patch History From Filesystem
[uploadph=y|n]
where
* help=y Prints help information about adpatch options.
* preinstall To run adpatch in Pre-Install Mode.
Default No.
* apply To run adpatch in Test Mode.
Default Yes.
* uploadph To upload the patch history from the filesystem to the
database and exit. This feature can be used when the system
is not in maintenance mode.
Default No.
* interactive Invokes adpatch in Non-Interactive mode when
interactive=no is specified.
Default Yes.
Following are usually specified in Non-Interactive Mode, however not all
are compulsory. Some are also valid for interactive mode.
* defaultsfile Defaults file name.
Default none. No default file read or written.
* logfile Adpatch log file name.
Default none. Adpatch prompts for this value.
* workers Specifies the number of workers to run.
Default none. Adpatch prompts for this value.
* patchtop Top-level directory for the current patch.
Default none. Adpatch prompts for this value.
* driver Name of the patch driver file.
Default none. Adpatch prompts for this value.
* restart To restart an existing session.
Default none. Adpatch prompts for this value.
* abandon To abandon the previous failed session.
Default No.
* wait_on_failed_job To prevent adpatch from exiting, when all
workers have failed in Non-Interactive Mode.
Default No.
* localworkers Used in Distributed AD to specify the number of
workers to be run on the current machine.
Default Value specified for workers.
* printdebug To display extra debugging information.
Default No.
* parallel_index_threshold Threshold block count in each table, which when
exceeded for a table causes its indexes to be
created using parallel slaves.
Default none. Adpatch does not create indexes
in parallel.
* order = To organize list of jobs to run in a phase. Default forward.
* forward The order in which jobs are listed in the
patch driver file.
* backward Opposite to how the jobs are listed in the
patch driver file.
* flags = Generic flags passed to adpatch
* hidepw To omit the HIDEPW: comments in the log file.
Default hidepw.
* trace To log all database operations to a trace file.
Default notrace.
* logging To create indexes in LOGGING or NOLOGGING mode.
Default nologging.
* options = Generic options passed to adpatch.
* checkfile To skip running exec, SQL, and exectier
commands if they are recorded as already run.
Default checkfile.
* compiledb To compile invalid objects in the database
after running actions in the database driver.
Default compiledb.
* compilejsp To compile out-of-date JSP files, if the patch
has copy actions for at least one JSP file.
Default compilejsp.
* copyportion To run commands found in a copy driver.
Default copyportion.
* databaseportion To run commands found in a database driver.
Default databaseportion.
* generateportion To run commands found in a generate driver.
Default generateportion.
* integrity To perform patch integrity checking.
Default nointegrity.
* maintainmrc To maintain the MRC schema after running
actions found in the database driver.
Default maintainmrc.
* autoconfig To run AutoConfig.
Default autoconfig.
* actiondetails To get the details of actions turned off.
Default actiondetails.
* parallel To run actions that update the database or
actions that generate files in parallel.
Default parallel.
* prereq To perform prerequisite patch checking prior
to running patch driver files.
Default prereq.
* revcache To load the package revision cache (if adpatch
determines it is needed).
Default revcache.
* validate To connect to all registered Oracle
Applications schemas at the start of the patch.
Default novalidate.
* hotpatch A patch which can be applied in Normal mode.
Default hotpatch.
* phtofile The patch history will be saved to files.
Default nophtofile.

Das könnte Ihnen auch gefallen