1 – Areas
Areas[=storage-area-list]
Areas=*
Specifies the storage areas to be analyzed. You can specify each
storage area by name or by the area's ID number.
If you are interested in the placement information for a
particular index, specify the area where the data resides, not
where the index resides. For example, if you are interested in
the placement information for the SH_EMPLOYEE_ID index of the
mf_personnel database, you should specify SALARY_HISTORY as the
storage area (which is where the data resides), not RDB$SYSTEM
(which is where the index resides).
If you do not specify the Areas qualifier, or if you specify
the Areas qualifier but do not provide a storage-area-list,
information for all the storage areas is displayed.
If you specify more than one storage area, separate the storage
area names or ID numbers in the storage-area-list with a comma
and enclose the list within parentheses.
If you specify more than one storage area with the Areas
qualifier, the analysis Oracle RMU provides is a summary for
all the specified areas. The analysis is not broken out into
separate sections for each specified storage area. To get index
information for a specific storage area, issue the RMU Analyze
Placement command, specifying only that area with the Areas
qualifier.
The Areas qualifier can be used with an indirect file reference.
See the Indirect-Command-Files help entry for more information.
The Areas qualifier (without a storage-area-list) is the default.
2 – Binary Output
Binary_Output[=file-option-list]
Nobinary_Output
Specifying the Binary_Output qualifier allows you to store
the summary results in a binary file, and to create a record
definition file that is compatible with the data dictionary for
the binary output file. The binary output file can be loaded
into an Oracle Rdb database by using the RMU Load command with
the Record_Definition qualifier that can then be used by a user-
written management application or procedure. The binary output
can also be used directly by the user-written application or
procedure.
The valid file options are:
o File=file-spec
The File option causes the RMU Analyze Placement command data
to be stored in an RMS file that contains a fixed-length
binary record for each index analyzed. The default file
extension for the binary output file is .unl. The following
command creates the binary output file analyze_out.unl:
$ RMU/ANALYZE/PLACEMENT -
_$ /BINARY_OUTPUT=FILE=ANALYZE_OUT MF_PERSONNEL.RDB
o Record_Definition=file-spec
The Record_Definition option causes the RMU Analyze Placement
command data record definition to be stored in an RMS file.
The output file contains the record definition in a subset of
the data dictionary command format. The default file extension
for the record definition output file is .rrd. Refer to the
rrd_file_syntax help topic for a description of .rrd files.
The following command creates the output file analyze_out.rrd:
$ RMU/ANALYZE/PLACEMENT -
_$ /BINARY_OUTPUT=RECORD_DEFINITION=ANALYZE_OUT MF_PERSONNEL.RDB
You can specify both file options in one command by separating
them with a comma and enclosing them within parentheses, as
follows:
$ RMU/ANALYZE/PLACEMENT/BINARY_OUTPUT= -
_$ (FILE=ANALYZE_OUT,RECORD_DEFINITION=ANALYZE_OUT) -
_$ MF_PERSONNEL.RDB
The default is the Nobinary_Output qualifier, which does not
create an output file.
3 – Exclude
Exclude=Metadata
Excludes information from the RMU Analyze Placement command data.
When you specify the Exclude=Metadata qualifier, information on
all the Oracle Rdb indexes (for example, the RDB$NDX_REL_NAME_NDX
and RDB$COLLATIONS_NDX indexes) is excluded from the RMU Analyze
Placement command output. When you do not specify the Exclude
qualifier, data is provided for all indexes in the database.
Data is accumulated for the indexes excluded with the Exclude
qualifier, but the data is excluded from the RMU Analyze
Placement command output.
You cannot specify the Exclude qualifier and one or more index
names in the same RMU Analyze Placement command.
4 – Option
Option=type
Specifies the type of information and level of detail the
analysis will include. Three types of output are available:
o Normal
Output includes only summary information. Normal is the
default.
o Full
Output includes histograms and summary information.
o Debug
Output includes internal information about the data,
histograms, and summary information. Output also displays
uncompressed index keys from compressed indexes. The
hexadecimal output is that of the uncompressed index key.
However, the lengths shown are of the compressed index key.
For more information on RMU Analyze Placement and the display
of index keys, refer to the Oracle Rdb7 Guide to Database
Performance and Tuning.
5 – Output
Output=file-name
Specifies the name of the file where output will be sent. The
default file type is .lis. If you do not specify the Output
qualifier, the default output is SYS$OUTPUT.
6 – Transaction Type
Transaction_Type=option
Allows you to specify the transaction mode for the transactions
used to perform the analyze operation. Valid options are:
o Automatic
o Read_Only
o Noread_Only
You must specify an option if you use this qualifier.
If you do not use any form of this qualifier, the Transaction_
Type=Automatic qualifier is the default. This qualifier specifies
that Oracle RMU is to determine the transaction mode used for the
analyze operation. If any storage area in the database (including
those not accessed for the analyze operation) has snapshots
disabled, the transactions used for the analyze operation are
set to read/write mode. Otherwise, the transactions are set to
read-only mode.
The Transaction_Type=Read_Only qualifier specifies the
transactions used to perform the analyze operation be set to
read-only mode. When you explicitly set the transaction type to
read-only, snapshots need not be enabled for all storage areas
in the database, but must be enabled for those storage areas that
are analyzed. Otherwise, you receive an error and the analyze
operation fails.
You might select this option if not all storage areas have
snapshots enabled and you are analyzing objects that are stored
only in storage areas with snapshots enabled. In this case, using
the Transaction_Type=Read_Only qualifier allows you to perform
the analyze operation and impose minimal locking on other users
of the database.
The Transaction_Type=Noread_Only qualifier specifies that the
transactions used for the analyze operation be set to read/write
mode. You might select this option if you want to eradicate
the growth of snapshot files that occurs during a read-only
transaction and are willing to incur the cost of increased
locking that occurs during a read/write transaction.