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:
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
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:
Tells AD programs to display extra debugging
information. In some cases, the amount of extra
debugging information is substantial.
hider feature
whether to omit
the 'HIDEPW:'
AD utility log file containing
passwords can be automatically
masked to not display the passwords.
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.
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
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.
whether to create
indexes using
LOGGING or
NOLOGGING
mode
Use of NOLOGGING when creating indexes
may increase performance. However it also
makes database media recovery incomplete and
does not work with standby databases.
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
Leave a Comment