1 – Active IO
Active_IO=max-reads
Specifies the maximum number of read operations to the backup
file that the RMU Restore Only_Root command will attempt
simultaneously. The value of the Active_IO qualifier can range
from 1 to 5. The default value is 3.
2 – After Journal
After_Journal=file-spec
Noafter_Journal
NOTE
This qualifier is maintained for compatibility with versions
of Oracle Rdb prior to Version 6.0. You might find it more
useful to specify the Aij_Options qualifier, unless you are
only interested in creating extensible .aij files.
Specifies how RMU Restore Only_Root is to handle after-image
journaling and .aij file creation, using the following rules:
o If you specify the After_Journal qualifier and provide a file
specification, RMU Restore Only_Root creates a new extensible
.aij file and enables journaling.
o If you specify the After_Journal qualifier but you do not
provide a file specification, RMU Restore Only_Root creates
a new extensible .aij file with the same name as the journal
that was active at the time of the backup operation.
o If you specify the Noafter_Journal qualifier, RMU Restore
Only_Root disables after-image journaling and does not create
a new .aij file. Note that if you specify the Noafter_Journal
qualifier, there will be a gap in the sequence of .aij files.
For example, suppose your database has .aij file sequence
number 1 when you back it up. If you issue an RMU Restore
Only_Root command with the Noafter qualifier, the .aij file
sequence number will be changed to 2. This means that you
cannot (and do not want to) apply the original .aij file to
the restored database (doing so would result in a sequence
mismatch).
o If you do not specify an After_Journal, Noafter_Journal, Aij_
Options, or Noaij_Options qualifier, RMU Restore Only_Root
recovers the journal state (enabled or disabled) and tries to
reuse the .aij file or files.
If you choose this option, take great care to either set the
database root TSN and CSN correctly, or create a full and
complete backup file of the database. Failure to do so might
make it impossible for you to recover your database from the
.aij file should it become necessary.
However, if the .aij file or files are not available (for
example, they have been backed up), after-image journaling is
disabled.
You cannot use the After_Journal qualifier to create fixed-size
.aij files; use the Aij_Options qualifier.
3 – Aij Options
Aij_Options=journal-opts
Noaij_Options
Specifies how RMU Restore Only_Root is to handle after-image
journaling and .aij file creation, using the following rules:
o If you specify the Aij_Options qualifier and provide a
journal-opts file, RMU Restore Only_Root enables journaling
and creates the .aij file or files you specify for the
restored database. If only one .aij file is created for the
restored database, it will be an extensible .aij file. If two
or more .aij files are created for the database copy, they
will be fixed-size .aij files (as long as at least two .aij
files are always available).
o If you specify the Aij_Options qualifier, but do not provide a
journal-opts file, RMU Restore Only_Root disables journaling
and does not create any new .aij files.
o If you specify the Noaij_Options qualifier, RMU Restore Only_
Root disables journaling and does not create any new .aij
files.
o If you do not specify an After_Journal, Noafter_Journal, Aij_
Options, or Noaij_Options qualifier, RMU Restore Only_Root
recovers the journaling state (enabled or disabled) and tries
to reuse the .aij file or files.
If you choose this option, take great care to either set the
database root TSN and CSN correctly, or create a full and
complete backup file of the database. Failure to do so might
make it impossible for you to recover your database from the
.aij file should it become necessary.
However, if the .aij file or files are not available (for
example, they have been backed up), after-image journaling is
disabled.
See Show After_Journal for information on the format of a
journal-opts-file.
4 – Directory
Directory=directory-spec
Specifies the default directory for the database root and the
default directory for where the root can expect to find the
database storage areas and snapshot files.
See the Usage Notes for information on how this qualifier
interacts with the Root, File, and Snapshot qualifiers and for
warnings regarding restoring database files into a directory
owned by a resource identifier.
5 – Initialize Tsns
Initialize_Tsns
Noinitialize_Tsns
Initializes all transaction sequence number (TSN) values for
the entire database by setting the values to zero. Each time a
transaction is initiated against a database, a TSN is issued.
The numbers are incremented sequentially over the life of the
database.
TSN and CSN values are each contained in a quadword with the
following decimal format:
high longword : low longword
The high longword can hold a maximum user value of 32768
(215) and the low longword can hold a maximum user value of
4,294,967,295 (232). A portion of the high longword is used by
Oracle Rdb for overhead.
When you specify a TSN or CSN, you can omit the high longword and
the colon if the TSN or CSN fits in the low longword. For example
0:444 and 444 are both valid input values.
As your next TSN value approaches the maximum value allowed,
you should initialize the TSNs. You can determine the next TSN
and next commit sequence number (CSN) values by dumping the
database root file, using the RMU Dump command with the Header
and Option=Debug qualifiers.
The Initialize_Tsns qualifier takes much more time to execute
because all TSN values in the database are set to zero, which
requires writing to every page in the database. When the database
TSNs are reset, using the Initialize_Tsns qualifier, you should
use the After_Journal qualifier or the Aij_Options qualifier and
immediately perform a full database backup operation and create
a new .aij file. This ensures continuity of journaling and the
ability to recover the database.
The default Noinitialize_Tsns qualifier does not initialize the
database TSNs.
Note that you cannot use the Initialize_Tsns with the Set_Tsn
or Noset_Tsn qualifier in the same command. This restriction is
required because Initialize_Tsns directs RMU Restore Only_Root to
reset the TSN value to zero, while Set_Tsn directs RMU Restore
Only_Root to reset the TSN to the value you have indicated,
and Noset_Tsn leaves the TSN value unchanged. Never use the
Initialize_Tsns qualifier if Replication Option for Rdb transfers
have been defined for the database. The Initialize_Tsns qualifier
does not reset the Replication Option for Rdb transfers.
6 – Label
Label=(label-name-list)
Specifies the 1- to 6-character string with which the volumes
of the backup file have been labeled. The Label qualifier is
applicable only to tape volumes. You must specify one or more
label names when you use the Label qualifier.
You can specify a list of tape labels for multiple tapes. If you
list multiple tape label names, separate the names with commas,
and enclose the list of names within parentheses.
In a normal restore operation, the Label qualifier you specify
with the RMU Restore Only_Root command should be the same Label
qualifier you specified with the RMU Backup command you used to
back up your database.
The Label qualifier can be used with indirect file references.
See the Indirect-Command-Files help entry for more information.
7 – Librarian
Librarian=options
Use the Librarian qualifier to restore files from data archiving
software applications that support the Oracle Media Management
interface. The file name specified on the command line identifies
the stream of data to be retrieved from the Librarian utility. If
you supply a device specification or a version number it will be
ignored.
Oracle RMU supports retrieval using the Librarian qualifier only
for data that has been previously stored by Oracle RMU using the
Librarian qualifer.
The Librarian qualifier accepts the following options:
o Trace_file=file-specification
The Librarian utility writes trace data to the specified file.
o Level_Trace=n
Use this option as a debugging tool to specify the level of
trace data written by the Librarian utility. You can use a
pre-determined value of 0, 1, or 2, or a higher value defined
by the Librarian utility. The pre-determined values are :
- Level 0 traces all error conditions. This is the default.
- Level 1 traces the entry and exit from each Librarian
function.
- Level 2 traces the entry and exit from each Librarian
function, the value of all function parameters, and the
first 32 bytes of each read/write buffer, in hexadecimal.
o Logical_Names=(logical_name=equivalence-value,...)
You can use this option to specify a list of process logical
names that the Librarian utility can use to specify catalogs
or archives where Oracle Rdb backup files are stored,
Librarian debug logical names, and so on. See the specific
Librarian documentation for the definition of logical names.
The list of process logical names is defined by Oracle RMU
prior to the start of any Oracle RMU command that accesses the
Librarian application.
The following OpenVMS logical names must be defined for use with
a Librarian utility before you execute an Oracle RMU backup or
restore operation. Do not use the Logical_Names option provided
with the Librarian qualifier to define these logical names.
o RMU$LIBRARIAN_PATH
This logical name must be defined so that the shareable
Librarian image can be loaded and called by Oracle RMU backup
and restore operations. The translation must include the file
type (for example, .exe), and must not include a version
number. The shareable Librarian image must be an installed
(known) image. See the Librarian implementation documentation
for the name and location of this image and how it should be
installed.
o RMU$DEBUG_SBT
This logical name is not required. If it is defined, Oracle
RMU will display debug tracing information messages from
modules that make calls to the Librarian shareable image.
You cannot use device specific qualifiers such as Rewind,
Density, or Label with the Librarian qualifier because the
Librarian utility handles the storage meda, not Oracle RMU.
8 – Log
Log
Nolog
Specifies whether the processing of the command is reported
to SYS$OUTPUT. Specify the Log qualifier to request that the
progress of the restore operation be written to SYS$OUTPUT and
the Nolog qualifier to suppress this report. If you specify
neither, the default is the current setting of the DCL verify
switch. (The DCL SET VERIFY command controls the DCL verify
switch.)
9 – Media Loader
Media_Loader
Nomedia_Loader
Use the Media_Loader qualifier to specify that the tape device
from which the backup file is being read has a loader or stacker.
Use the Nomedia_Loader qualifier to specify that the tape device
does not have a loader or stacker.
By default, if a tape device has a loader or stacker, RMU Restore
Only_Root should recognize this fact. However, occasionally RMU
Restore Only_Root does not recognize that a tape device has a
loader or stacker. Therefore, when the first tape has been read,
RMU Restore Only_Root issues a request to the operator for the
next tape, instead of requesting the next tape from the loader
or stacker. Similarly, sometimes RMU Restore Only_Root behaves
as though a tape device has a loader or stacker when actually it
does not.
If you find that RMU Restore Only_Root is not recognizing that
your tape device has a loader or stacker, specify the Media_
Loader qualifier. If you find that RMU Restore Only_Root expects
a loader or stacker when it should not, specify the Nomedia_
Loader qualifier.
10 – New Snapshots
New_Snapshots
Nonew_Snapshots
Allows you to specify whether to create new snapshot (.snp) files
as part of a Restore Only_Root operation.
The default is the Nonew_Snapshots qualifier, which causes the
command to initialize the existing .snp files.
If you specify the New_Snapshots qualifier, the command creates
and initializes new .snp files. When you specify the New_
Snapshots qualifier, you should either delete the existing
.snp files before the restore operation or purge the .snp files
afterwards.
11 – Nodes Max
Nodes_Max=number-cluster-nodes
Specifies a new upper limit on the number of VMScluster nodes
from which users can access the restored database. The Nodes_Max
qualifier will accept values between 1 and 96 VMScluster nodes.
The actual maximum is the highest number of VMScluster nodes
possible in the current version of OpenVMS. The default value is
the limit defined for the database before it was backed up.
12 – Options
Options=file-spec
Specifies the options file that contains storage area names,
followed by the storage area qualifiers that you want applied to
that storage area.
You can direct RMU Restore Only_Root to create an options file
for use with this qualifier by specifying the Restore_Options
qualifier with the RMU Backup, RMU Dump, and RMU Dump Backup
commands. See Backup Database, Dump Database, and Dump Backup_
File for details.
If you create your own options file, do not separate the storage
area names with commas. Instead, put each storage area name on
a separate line in the file. The storage area qualifiers that
you can include in the options file are: Blocks_Per_Page, File,
Snapshot, and Thresholds. You can use the DCL line continuation
character, a hyphen (-), or the comment character (!) in the
options file. The default file extension is .opt. See Example 5
in the Examples help entry under this command.
13 – Rewind
Rewind
Norewind
Specifies whether the tape that contains the backup file will
be rewound before processing begins. The Norewind qualifier, the
default, causes the search for the backup file to begin at the
current tape position.
The Rewind and Norewind qualifiers are applicable only to tape
devices. RMU Restore Only_Root returns an error message if you
use these qualifiers and the device is not a tape device.
14 – Root
Root=root-file-spec
Requests that the database root (.rdb) be restored to the
specified location.
See the Usage Notes for information on how this qualifier
interacts with the Directory, File, and Snapshot qualifiers and
for warnings regarding restoring database files into a directory
owned by a resource identifier.
The Root qualifier is only meaningful when used with a multifile
database.
15 – Set Tsn
Set_Tsn=(Tsn=n, Csn=m)
Noset_Tsn
The Set_Tsn qualifier sets the database transaction sequence
number (TSN) and commit sequence number (CSN) to the specified
values. The correct value can be extracted from the original .rdb
file if it is still accessible, or from the last .aij file if one
is available. If that fails, you can use a TSN value larger than
the maximum number of transactions applied to the database since
it was created, or since TSNs were last initialized.
The TSN and CSN values do not have to be the same value. However,
you need to choose new values that are greater than the last
values assigned to a transaction. Set_Tsn values are expected
to be multiples of eight. If you specify a value that is not a
multiple of eight, RMU Restore Only_Root assigns the next highest
value that is a multiple of eight. (For example, if you specify
Set_Tsn=(Tsn=90, Csn=90), RMU Restore Only_Root assigns the Next
TSN a value of 96.)
The default value for the Set_Tsn qualifier is the TSN and CSN
values stored in the backup file plus 1,000,000 when TSNs are not
being initialized. The new TSN and CSN values for most database
applications should be larger than the number of transactions
committed since the database was last backed up. Set the TSN
and CSN values higher than this default increment value plus
the value in the backup file when needed. You can determine
the next TSN and CSN values by dumping the .rdb file, using the
Option=Debug qualifier.
The TSN and CSN values are each contained in a quadword with the
following decimal format:
high longword : low longword
The high longword can hold a maximum user value of 32768
(215) and the low longword can hold a maximum user value of
4,294,967,295 (232). A portion of the high longword is used by
Oracle Rdb for overhead.
When you specify a TSN or CSN, you can omit the high longword and
the colon if the TSN fits in the low longword. For example 0:444
and 444 are both valid TSN input values.
The Noset_Tsn qualifier specifies that the root will be restored
with the same TSN state as was recorded in the backup file.
When you use the Noset_Tsn qualifier in conjunction with the
Noupdate_Files qualifier, you can use a backup strategy that uses
recent by-area full backup files in place of a recent full and
complete backup file of the entire database. See Example 6 in the
Examples help entry under this command.
Note that you cannot use the Initialize_Tsns with the Set_Tsn
or Noset_Tsn qualifier in the same command. This restriction is
required because Initialize_Tsns directs RMU Restore Only_Root
to reset the TSN value to zero, while Set_Tsn directs RMU Restore
Only_Root to reset the TSN to the value you have indicated, and
Noset_Tsn leaves the TSN value unchanged.
16 – Transaction Mode=(mode-list)
Transaction_Mode=(mode-list)
Sets the allowable transaction modes for the database root file
created by the restore operation. The mode-list can include one
or more of the following transaction modes:
o All - Enables all transaction modes
o Current - Enables all transaction modes that are set for the
source database. This is the default transaction mode.
o None - Disables all transaction modes
o [No]Batch_Update
o [No]Read_Only
o [No]Exclusive
o [No]Exclusive_Read
o [No]Exclusive_Write
o [No]Protected
o [No]Protected_Read
o [No]Protected_Write
o [No]Read_Write
o [No]Shared
o [No]Shared_Read
o [No]Shared_Write
If you specify more than one transaction mode in the mode-list,
enclose the list in parenthesis and separate the transaction
modes from one another with a comma. Note the following:
o When you specify a negated transaction mode, for example
Noexclusive_Write, it indicates that exclusive write is not
an allowable access mode for the copied database.
o If you specify the Shared, Exclusive, or Protected transaction
mode, Oracle RMU assumes you are referring to both reading and
writing in that transaction mode.
o No mode is enabled unless you add that mode to the list, or
you use the All option to enable all transaction modes.
o You can list one transaction mode that enables or disables a
particular mode followed by another that does the opposite.
For example, Transaction_Mode=(Noshared_Write, Shared) is
ambiguous because the first value disables Shared_Write access
and the second value enables Shared_Write access. Oracle
RMU resolves the ambiguity by first enabling the modes as
specified in the modes-list and then disabling the modes as
specified in the modes-list. The order of items in the list is
irrelevant. In the example presented previously, Shared_Read
is enabled and Shared_Write is disabled.
17 – Update Files
Update_Files
Noupdate_Files
The Update_Files qualifier specifies that the root will be
restored, and RMU Restore Only_Root will attempt to link that
restored root to the area files. In addition, the snapshot (.snp)
file will be updated or created. This is the default.
The Noupdate_Files qualifier specifies that the restore operation
will restore the root, but it will not link that restored root
to any of the area files, nor will it create or update the .snp
files.
When you use the Noupdate_Files qualifier in conjunction with
the Noset_Tsn qualifier, you can use a backup strategy that uses
recent by-area full backup files in place of a recent full and
complete backup file of the entire database. See Example 6 in the
Examples help entry under this command
18 – Users Max
Users_Max=number-users
Specifies a new upper limit on the number of users that can
simultaneously access the restored database. The valid range is
between 1 and 2032 users. The default value is the value defined
for the database before it was backed up.