• Embed Doc
  • Readcast
  • Collections
  • CommentGo Back
Download
AD Command Line Options

This document contains information about AD command line options. You should
read and understand all content described here before you begin using these
options. The most current version of these notes is document 233038.1 on
OracleMetaLink. There is a change log at the end of this document.
This document contains the following sections:

\u2022
Section 1: Overview
Introduction of AD command line options and how they are used.
\u2022
Section 2: Command Line Options For All Major AD Utilities
Details of valid command line options for all major AD utilities.
\u2022
Section 3: Command Line Options For AutoPatch
Details of valid command line options for AutoPatch.
\u2022
Section 4: Command Line Options For One or More AD Utilities
Details of valid command line options for one or more AD utilities.
\u2022
Section 5: Available Documentation
Additional documentation for AD utilities.
Section 1: Overview

In addition to their standard functionality, AD utilities can accept command line
options to modify the actions performed by the utility. This document describes
the AD command line options. Some AD command line options are not
documented here because they are either obsolete or not normally specified by
end users.
For simplicity, AD utilities are referred to in these examples by their executable
names instead of their utility names. For details about the AD utilities, seeOracle

Applications Maintenance Utilities. Here is a mapping of executable names to
utility names:
Executable Name
Utility Name
adpatch
AutoPatch
adadmin
AD Administration
adaimgr
AutoUpgrade
adctrl
AD Controller

All AD command line options have the format:token=value. In general, you
should enter AD command line options in lowercase. Thet o ke n is converted to
lower\u00adcase internally, but thevalue is not. In some cases,value is a comma\u00ad
separated list of options. AD command line options cannot contain embedded
whitespace characters.
Examples of valid command\u00adline argument syntax are:

adpatch options=nocopyportion,nogenerateportion
adpatch printdebug=y
Examples of invalid command\u00adline argument syntax are:
adpatch options=nocopyportion, nogenerateportion(contains imbeded
whitespace)
adpatch OPTIONS=NOCOPYPORTION,NOGENERATEPORTION(keyword will
be recognized, but values won't)
Example of using multiple command\u00adline options:
adpatch printdebug=y options=validate flags=hidepw
Section 2: Command Line Options For All Major AD Utilities
help=y|n
Purpose:
Summarizes available command line options.
Valid values:
yor n
Default value:n
Example
adpatch help=y
logfile=log-file-name
Purpose:
Tells AD utilities what log file to use. Normally
used in non-interactive mode.
Valid values:
A file name (not a fully-qualified path name)
Default value:none, meaning that the utility will prompt for the
log file name
Example
adpatch logfile=test.log
printdebug=y|n
Purpose:

Tells AD programs to display extra debugging
information. In some cases, the amount of extra
debugging information is substantial.

Valid values:
yor n
Default value:n
Example
adpatch printdebug=y
flags=list-of-flags
Purpose:
Generic flags passed to AD utilities. See table
below for more information.
Valid values:
A comma-separated list of flags
Default value:none, meaning that no flags have been passed
Example
adpatch flags=hidepw
Table of flags:
Flag
Purpose
Default
Comments
hidepw Tells password

hider feature
whether to omit
the 'HIDEPW:'

comments in AD
utility log files
nohidepwStarting in AD Mini-pack H, lines in an

AD utility log file containing
passwords can be automatically
masked to not display the passwords.

\u2022

Whenno hidepw is specified, each line
containing masked passwords is
followed by a corresponding line
prefixed with 'HIDEPW:' which
contains the original line with
passwords included.

\u2022

Whenhidepw is specified, the
additional 'HIDEPW:' line is not
displayed.

The intent of this feature is to include
passwords protected by 'HIDEPW:'
comments in the AD program log file
by default so that debugging is easier
and stripping the passwords (using

grep -v 'HIDEPW:' file > file_no_pwson

UNIX, for example) is easy. For cases
where security is more important than
ease of debugging,hidepw can be
specified to prevent any passwords
from being listed in the AD utility log
file.

logging Tells the AD utility

whether to create
indexes using
LOGGING or
NOLOGGING
mode

loggingin
adpatch
nologging
in
adaimgr

Use of NOLOGGING when creating indexes
may increase performance. However it also
makes database media recovery incomplete and
does not work with standby databases.

\u2022

LOGGING is the default in adpatch so
that database media recovery and
standby databases work by default. Use
offlags=nolo gging in adpatch is
discouraged for production systems
unless a complete backup is taken both

of 00

Leave a Comment

You must be to leave a comment.
Submit
Characters: ...
You must be to leave a comment.
Submit
Characters: ...