Displays or writes to a specified output file the contents
of database, storage area (.rda), and snapshot (.snp) files,
including root information.
NOTE
The Start and End qualifiers apply only when the Areas,
Lareas, Snapshots, Abms_Only or Spams_Only qualifier is
specified.
1 – Description
Use this command to examine the contents of your database root
(.rdb), storage area (.rda), and snapshot (.snp) files, to
display current settings for database definition options, and
to display a list of active database users. The list of database
users is maintained clusterwide in a VMScluster environment.
You can display the contents of all pages in any data storage
area of the database or display the contents of just those pages
in which rows and indexes for a specific table are stored.
See the chapter that explains the internal database page format
in the Oracle Rdb Guide to Database Maintenance for tutorial
information.
Depending on your selection of qualifiers, the RMU Dump command
can list:
o A formatted display of any number of pages in the storage area
of the database.
o A formatted display of any number of pages in a uniform
logical area of the database.
o A formatted display of any number of pages in the snapshot
area of the database.
o Header information. (This is listed by default if no
qualifiers are specified.)
o Current users of the database.
2 – Format
(B)0[m RMU/Dump root-file-spec
[4mFile[m [4mQualifiers[m x [4mDefaults[m
x
/ABMS_Only x See description
/[No]Areas [= storage-area-list] x /Noareas
/End=integer x See description
/[No]Header[=detail-opt, type-opts] x See description
/[No]Lareas [ = logical-area-list] x /Nolareas
/Option={Normal | Full | Debug} x /Option=Normal
/Output = file-name x /Output=SYS$OUTPUT
/Restore_Options=file-name x None
/[No]Snapshots [ = storage-area-list] x /Nosnapshots
/Spams_Only x See description
/Start=integer x See description
/State=Blocked x See description
/[No]Users x /Nousers
3 – Parameters
3.1 – root-file-spec
A file specification for the database root file whose root file
header information, user information, storage area file pages, or
snapshot area file pages you want to display.
4 – Command Qualifiers
4.1 – ABMS Only
Specifies that the RMU/DUMP command will only dump ABM pages
in uniform storage areas or in logical areas contained within
uniform storage areas.
The ABM pages can be dumped within a limited page range specified
by the START and END qualifiers.
If there are no ABM pages within the specified page range or
the storage area is a mixed format area or the logical area
is contained within a mixed storage area, no ABM pages will be
dumped.
This qualifier cannot be specified in the same Dump command as
the SPAMS_Only qualifier. This qualifier cannot be specified in
the same Dump command with the Snapshots qualifier.
4.2 – Areas
Areas [=storage-area-list]
Noareas
Specifies a display that consists of storage area pages. You can
specify storage areas by name or by the area's ID number.
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.
You can also specify the Areas=* qualifier to display all storage
areas. If you do not specify the Areas qualifier, none of the
storage areas are displayed.
You can use the Start and End qualifiers to display a range of
storage area pages.
The Areas qualifier can be used with indirect file references.
See the Indirect-Command-Files help entry for more information.
4.3 – End
End=integer
Specifies the highest-numbered area or snapshot page to include
in the display. The default is the last page.
If you also use the Lareas qualifier, note that the Start and End
qualifiers specify a page range relative to the logical area, not
a specific storage area page number.
4.4 – Header
Header
Noheader
Header[=(detail-opt, type-opts)]
Indicates whether to include the database header in the output.
Specify the Header qualifier to include all database header
information in the output. Specify the Noheader qualifier to
suppress the database header listing. Specify the Header=(detail-
opt, type-opts) qualifier to limit the output from the header to
specific items of interest. Use the detail-opt options (Brief or
Detail) to limit the amount of output. Use the type-opt options
to limit the output to specific types of information.
RMU Dump Command Header Options summarizes the Header options and
the effects of specifying each option.
Table 8 RMU Dump Command Header Options
Option Effect
All Generates the full output of all the header
information. If you specify this option and
other Header options, the other options are
ignored. This is the default option.
Areas Output displays information about active
storage areas and snapshot areas.
Backup Output displays information about backup and
recovery.
Brief Generates a summary of the requested database
root file information.
Buffers Output displays information about database
buffers.
Corrupt_Page Output displays the Corrupt Page Table (CPT).
Detail Generates a complete report of the requested
database root file information. This is the
default.
Fast_Commit Output displays information about whether
fast commit is enabled or disabled, whether
commit to AIJ optimization is enabled or
disabled, the AIJ checkpointing intervals,
and the transaction interval.
Hot_Standby Output displays information regarding hot
standby databases.
Locking Output displays information about database
locking, such as whether or not adjustable
record locking, carry-over lock optimization,
and lock tree partitioning are enabled or
disabled, and fanout factors.
Journaling Output displays information about RUJ and AIJ
journaling.
Nodes Output displays names of nodes that are
accessing the specified database.
Parameters Output displays basic root file header
information.
Root_Record Output describes the Oracle Rdb specific
section of the database root. This includes
backup, restore, verify, and alter timestamps,
as well as flags that indicate that no such
operation has been performed. The bootstrap
DBKEY is used to locate the RDB$DATABASE
row for this database, and then the other
system tables. If an alternate bootstrap
DBKEY exists, then this database has been
converted using RMU Convert Nocommit command.
In this case, the current metadata version is
displayed.
Row_Caches Output displays information about row caches.
Security_Audit Output displays information about security
auditing.
Sequence_Numbers Output displays database sequence numbers.
Users Output displays information about active
database users.
If you specify both the Detail option and the Brief option,
Detail takes precedence. If you specify the All option and other
detail-opt options, the All option takes precedence. If you
specify the Brief option or the Detail option only, the default
for the type-opt is All. If you specify type-opts options, but do
not specify a detail-opt option, the default for the detail-opt
is Detail.
If you specify more than one option, separate the options with
commas and enclose the list within parentheses.
See the Usage_Notes help entry under this command for information
on understanding the derived values found in the database header.
The Header=All and Header=Root_Record qualifiers output
information on the use of the RMU Alter command on the specified
database. For example, you see the following line in the output
if you have never used the RMU Alter command on the database:
Database has never been altered
Do not confuse this with alterations made by SQL ALTER
statements. Information about alterations made with the SQL
ALTER statement is not included in the output from the RMU Dump
command.
If you specify the Areas, Lareas, or Snapshots qualifier, the
Noheader qualifier is the default. Otherwise, Header=(All,
Detail) is the default.
It is invalid to specify the Header=Root_Record and the
Option=Debug qualifiers in the same Oracle RMU command line.
See the Oracle Rdb7 and Oracle CODASYL DBMS: Guide to Hot
Standby Databases manual for information about the "Hot Standby"
references in the database header.
For complete information on the contents of the database header,
see the Oracle Rdb Guide to Database Maintenance.
4.5 – Lareas
Lareas[=logical-area-list]
Nolareas
Specifies a display that consists of storage area pages allocated
to a logical area or areas. In a single-file database, each table
in the database is stored in its own logical area.
You cannot use the Lareas qualifier with logical areas that are
stored in storage areas that have a mixed page format.
If you specify more than one logical area name, separate the
storage area names in the logical area list with a comma, and
enclose the list within parentheses.
You can also specify the Lareas=* qualifier to display all
logical areas that have a uniform page format.
The default is the Nolareas qualifier.
The Lareas qualifier can be used with indirect file references.
See the Indirect-Command-Files help entry for more information.
4.6 – Option
Option=type
Specifies the type of information and level of detail the output
will include. Three types of output are available:
o Normal
The output includes summary information. This is the default.
o Full
In addition to the Normal information, the output includes
more detailed information.
o Debug
In addition to Normal and Full information, the output
includes internal information about the data. In general,
use the Debug option for diagnostic support purposes.
4.7 – Output
Output=file-name
Specifies the name of the file where output is to be sent. The
default is SYS$OUTPUT. The default output file type is .lis, if
you specify a file name.
4.8 – Restore Options
Restore_Options=file-name
Generates an options file designed to be used with the Options
qualifier of the RMU Restore command.
The Restore_Options file is created by reading the database root
file. Therefore, there is no guarantee that this options file
will work with all backup files you attempt to restore with
a Restore operation. For example, if areas have been added or
deleted from the database since the backup file was created,
there will be a mismatch between the Restore_Options file and the
backup file. Similarly if the backup file was created by a backup
by-area operation, the Restore_Options file may refer to areas
that are not in the backup file.
By default a Restore_Options file is not created. If you
specify the Restore_Options qualifier and a file, but not a file
extension, Oracle RMU uses an extension of .opt by default.
4.9 – Snapshots
Snapshots[=storage-area-list]
Nosnapshots
Specifies a display that consists of snapshot file pages. The
RMU Dump command does not display snapshot pages if you omit the
Snapshots qualifier or if you specify the Nosnapshots qualifier.
In a single-file database, there is only one snapshot file. In
a multifile database, each storage area has a corresponding
snapshot file. Note that this parameter specifies the storage
area name, not the snapshot file name. If you specify more than
one storage area name, separate the storage area names with
commas, and enclose the storage-area-list within parentheses.
If you specify the Snapshots qualifier without a storage area
name, information is displayed for all snapshot files.
You can use the Start and End qualifiers to display a range of
snapshot file pages.
The default is the Nosnapshots qualifier.
The Snapshots qualifier can be used with indirect file
references. See the Indirect-Command-Files help entry for more
information.
4.10 – Spams Only
Spams_Only
Allows you to dump only the space area management (SPAM) pages in
the selected areas and page range.
A common usage for the RMU Dump command is to track down problems
with storage allocation and record placement. When this qualifier
is used, the SPAM pages are dumped, allowing you to locate the
individual data pages that you want to examine.
There is no negated form for this qualifier, and, if it is
omitted, all the selected pages are dumped.
The Start and End qualifiers can be used with the Spams_Only
qualifier.
4.11 – Start
Start=integer
Specifies the lowest-numbered area or snapshot page to include in
the display. The default is the first page; that is, the Start=1
qualifier.
If you also use the Lareas qualifier, note that the Start and End
qualifiers specify a page range relative to the logical area, not
a specific storage area page number.
4.12 – State
State=Blocked
Specifies a list of all unresolved distributed transactions in
the blocked database. A blocked database is a database that is
not committed or rolled back and is involved in an unresolved
distributed transaction. The State=Blocked qualifier displays the
following information about each transaction:
o Process identification (PID)
o Stream identification
o Monitor identification
o Transaction identification
o Name of the recovery journal
o Transaction sequence number (TSN)
o Distributed transaction identifier (TID)
o Name of the node on which the failure occurred
o Name of the node initiating the transaction (parent node)
You can use the State=Blocked qualifier only with the Users
qualifier. For information on resolving unresolved transactions
with the RMU Dump command, see the Oracle Rdb7 Guide to
Distributed Transactions.
4.13 – Users
Users
Nousers
Lists information about the current users of the database,
including all users in a VMScluster environment. Oracle RMU does
not consider a process that is running the Performance Monitor
(with the RMU Show Statistics command or through the Windowing
interface) to be a database user.
The default is Nousers.
5 – Usage Notes
o To use the RMU Dump command with the Areas qualifier or the
Lareas qualifier or the Snapshots qualifier for a database,
you must have the RMU$DUMP privilege in the root file access
control list (ACL) for the database or the OpenVMS SYSPRV or
BYPASS privilege.
To use the RMU Dump command with the Header qualifier for a
database, you must have the RMU$DUMP, RMU$BACKUP, or RMU$OPEN
privileges in the root file access control list (ACL) for the
database, or the OpenVMS SYSPRV or BYPASS privilege.
To use the RMU Dump command with the Users qualifier, you must
have the RMU$DUMP, RMU$BACKUP, or RMU$OPEN privileges in the
root file access control list (ACL) for the database or the
OpenVMS WORLD privilege.
o The Spams_Only qualifier conflicts with the Lareas and
Snapshots qualifiers; an error is generated if you specify
the Spams_Only qualifier with either of the other qualifiers.
o The Header=All and Header=Buffers qualifiers provide two
derived values to provide an estimated size of the global
section. These appear in the dump file as:
Derived Data...
- Global section size
With global buffers disabled is 43451 bytes
With global buffers enabled is 941901 bytes
The first value (With global buffers disabled) indicates the
approximate size of the global section when local buffers are
being used. The second value (With global buffers enabled)
indicates the approximate size of the global section if you
were to enable global buffers.
You can use these values to determine approximately how
much bigger the global section becomes if you enable global
buffers. This allows you to determine, without having to
take the database off line, how much larger to make the
VIRTUALPAGECNT and GBLPAGES SYSGEN parameters to accommodate
the larger global section.
However, note that you must take the database off line if
you decide to enable global buffers and you must shut down
and reboot the system to change the SYSGEN parameters. It
is recommended that you run AUTOGEN after you change SYSGEN
parameters.
Also note that these changes may require you to change the
MONITOR account quotas as well to ensure the paging file quota
is adequate.
6 – Examples
Example 1
The following example displays the header information for the
mf_personnel database on the terminal screen:
$ RMU/DUMP MF_PERSONNEL
Example 2
The following example generates a list of unresolved transactions
for the mf_personnel database:
$ RMU/DUMP/USERS/STATE=BLOCKED MF_PERSONNEL
Example 3
The following example shows the command you might use to view the
SPAM pages associated with the area EMPIDS_LOW:
$ RMU/DUMP/NOHEADER/AREAS=(EMPIDS_LOW)/SPAMS_ONLY -
_$ MF_PERSONNEL/OUTPUT=DUMP.LIS
Example 4
The following example demonstrates the use of the Restore_Options
qualifier. The first command performs a dump operation on the mf_
personnel database and creates a Restore_Options file. The second
command shows a portion of the contents of the options file. The
last command demonstrates the use of the options file with the
RMU Restore command.
$ RMU/DUMP MF_PERSONNEL.RDB /RESTORE_OPTIONS=MF_PERS.OPT -
_$ /OUTPUT=DUMP.LIS
$ TYPE MF_PERS.OPT
! Options file for database USER1:[DB]MF_PERSONNEL.RDB;1
! Created 19-JUL-1995 14:55:17.80
! Created by DUMP command
RDB$SYSTEM -
/file=USER2:[STO]MF_PERS_DEFAULT.RDA;1 -
/extension=ENABLED -
/read_write -
/spams -
/snapshot=(allocation=100, -
file=USER2:[SNP]MF_PERS_DEFAULT.SNP;1)
DEPARTMENTS -
/file=USER3:[STO]DEPARTMENTS.RDA;1 -
/blocks_per_page=2 -
/extension=ENABLED -
/read_write -
/spams -
/thresholds=(70,85,95) -
/snapshot=(allocation=100, -
file=USER3:[SNP]DEPARTMENTS.SNP;1)
.
.
.
$ RMU/RESTORE MF_PERSONNEL.RBF/OPTIONS=MF_PERS.OPT
Example 5
The following command generates a detailed display of backup,
recovery, RUJ, and AIJ information for the mf_personnel database.
$ RMU/DUMP/HEADER=(BACKUP,JOURNALING) MF_PERSONNEL.RDB
See the Oracle Rdb Guide to Database Maintenance and the Oracle
Rdb7 Guide to Distributed Transactions for more examples showing
the RMU Dump command and the output.
Example 6
The following example dumps all ABM pages contained in all
uniform storage areas in the specified Rdb database.
$ RMU/DUMP/ABMS_ONLY/OUT=DMP.OUT MF_PERSONNEL
Example 7
In the following example, only the ABM pages contained in the
named uniform storage area in the specified Rdb database are
dumped.
$ RMU/DUMP/ABMS_ONLY/AREA=RDB$SYSTEM MF_PERSONNEL
Example 8
In the following example, only the ABM pages contained in the
named logical area in a uniform storage area in the specified Rdb
database are dumped.
$ RMU/DUMP/ABMS_ONLY/LAREA=RDB$RELATIONS MF_PERSONNEL
Example 9
In the following example, only the ABM pages contained within
the specified page range in the named uniform storage area in the
specified Rdb database are dumped.
$ RMU/DUMP/ABMS_ONLY/AREA=RDB$SYSTEM/START=1/END=5 MF_PERSONNEL