1 – Acl
Acl
Noacl
Allows you to specify whether to restore the root file access
control list (ACL) that was backed up.
If you specify the Acl qualifier, the root file ACL that was
backed up is restored with the database. If the root file ACL
was not backed up and you specify the Acl qualifier with the RMU
Restore command, then RMU Restore restores the database without a
root file ACL.
If you specify the Noacl qualifier, the root file ACL is not
restored with the database.
The default is the Acl qualifier.
2 – Active IO
Active_IO=max-reads
Specifies the maximum number of read operations from the backup
file that RMU Restore attempts simultaneously. The value of the
Active_IO qualifier can range from 1 to 5. The default value is
3. Values larger than 3 might improve performance with multiple
tape drives.
3 – 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
interested in creating an extensible .aij file only. (An
extensible .aij file is one that is extended by a specified
amount when it reaches a certain threshold of fullness-
assuming there is sufficient space on the disk where it
resides.)
Specifies how RMU Restore 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, the RMU process 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 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
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 the .aij files. For
example, suppose your database has .aij file sequence number 1
when you back it up. If you issue an RMU Restore command with
the Noafter_Journal 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 recovers the
journal state (enabled or disabled) and tries to reuse the
.aij file or files. (See the Description help entry under this
command for details on when automatic .aij file recovery is
not attempted.)
When you specify an .aij file name, you should specify a new
device and directory for the .aij file. If you do not specify a
device and directory, you receive a warning message. To protect
yourself against media failures, put the .aij file on a different
device from that of your database files.
If the original database is lost or corrupted but the journal
files are unaffected, you would typically restore the database
without the use of either the Aij_Options or the After_Journal
qualifier.
The After_Journal qualifier conflicts with the Area and
Incremental qualifiers; you cannot specify the After_Journal
qualifier and either of these two other qualifiers in the same
RMU Restore command line.
You cannot use the After_Journal qualifier to create fixed-size
.aij files; use the Aij_Options qualifier.
4 – Aij Options
Aij_Options=journal-opts
Noaij_Options
Specifies how RMU Restore 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 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
restored database, they will be fixed-size .aij files (as long
as at least two .aij files are always available). Depending on
what is specified in the options file, after-image journaling
can either be disabled or enabled.
o If you specify the Aij_Options qualifier, but do not provide
a journal-opts file, RMU Restore disables journaling and does
not create any new .aij files.
o If you specify the Noaij_Options qualifier, RMU Restore
reuses the original .aij file configuration and recovers the
journaling state (enabled or disabled) from the backed-up .aij
file.
o If you do not specify an After_Journal, Noafter_Journal, Aij_
Options, or Noaij_Options qualifier, RMU Restore recovers the
journaling state (enabled or disabled) and tries to reuse the
.aij file or files. (This is the same as specifying the Noaij_
Options qualifier.)
See the Description help entry under this command for details
on when automatic .aij file recovery is not attempted.
The Aij_Options qualifier conflicts with the Area and Incremental
qualifiers; you cannot specify the Aij_Options qualifier and
either of these two other qualifiers in the same RMU Restore
command line.
If the original database is lost or corrupted but the journal
files are unaffected, you would typically restore the database
without the use of either the Aij_Options or the After_Journal
qualifier.
See Show After_Journal for information on the format of a
journal-opts-file.
5 – Area
Area
Specifies that only the storage areas listed in the storage-area-
name parameter on the command line or in the Options file are
to be restored. You can use this qualifier to simplify physical
restructuring of a large database.
By default, the Area qualifier is not specified. When the Area
qualifier is not specified, all the storage areas and the
database root (.rdb) file are restored. Therefore, if you want
to restore all the storage areas, omit the Area qualifier. If
you specify the Area qualifier, a valid database root must exist.
(First issue the RMU Restore Only Root command with a full backup
file to create a valid database if one does not exist.)
By using the RMU Backup and RMU Restore commands, you can back up
and restore selected storage areas of your database. This Oracle
RMU backup- and restore-by-area feature is designed to:
o Speed recovery when corruption occurs in some (not all) of the
storage areas of your database.
o Reduce the time needed to perform backup operations because
some data (data in read-only storage areas, for example) does
not need to be backed up with every backup operation performed
on the database.
NOTE
When you perform a by-area restore operation, an area may
be marked as inconsistent; that is, the area may not be at
the same transaction state as the database root when the
restore operation completes. This may happen, for example,
when automatic aij recovery is disabled with the Norecovery
qualifier, or if automatic recovery fails. You can check
to see if an area is consistent by using the RMU Show
Corrupt_Pages command. If you find that one or more areas
are inconsistent, use the RMU Recover command to apply the
.aij files. If the .aij files are not available, refer to
the section on Clearing an Inconsistent Flag in the Oracle
Rdb Guide to Database Maintenance for information on the
implications of setting a corrupt area to consistent. Then
refer to Set Corrupt_Pages for information on using the Set
Corrupt_Pages command to clear the inconsistent flag.
If you attempt to restore a database area that is not in the
backup file, you receive an error message and, typically, the
database will be inconsistent or unusable until the affected area
is properly restored.
In the following example, the DEPARTMENTS storage area is
excluded from the backup operation; therefore, a warning message
is displayed when the attempt is made to restore DEPARTMENTS,
which is not in the backup file. Note that when this restore
operation is attempted on a usable database, it completes, but
the DEPARTMENTS storage area is now inconsistent.
$ RMU/BACKUP /EXCLUDE=DEPARTMENTS MF_PERSONNEL.RDB -
_$ PERS_BACKUP5JAN88.RBF
$ RMU/RESTORE /NEW_VERSION /AREA PERS_BACKUP5JAN88.RBF DEPARTMENTS
%RMU-W-AREAEXCL, The backup does not contain the storage
area - DEPARTMENTS
If you create a backup file by using the RMU Backup command and
the Exclude qualifier, it is your responsibility to ensure that
all areas of a database are restored and recovered when you
use the RMU Restore and RMU Recover commands to duplicate the
database.
The Area qualifier conflicts with the After_Journal and Aij_
Options qualifiers.
6 – Cdd Integrate
Cdd_Integrate
Nocdd_Integrate
Integrates the metadata from the database root (.rdb) file into
the data dictionary (assuming the data dictionary is installed on
your system).
If you specify the Nocdd_Integrate qualifier, no integration
occurs during the restore operation.
You might want to delay integration of the database metadata with
the data dictionary until after the restore operation finishes
successfully.
You can use the Nocdd_Integrate qualifier even if the DICTIONARY
IS REQUIRED clause was used when the database was defined.
The Cdd_Integrate qualifier integrates definitions in one
direction only-from the database file to the dictionary. The
Cdd_Integrate qualifier does not integrate definitions from the
dictionary to the database file.
7 – Close Wait
Close_Wait=n
Specifies a wait time of n minutes before RMU Restore
automatically closes the database. You must supply a value for
n.
In order to use this qualifier, the Open_Mode qualifier on the
RMU Restore command line must be set to Automatic.
8 – Commit
Commit
NoCommit
Instructs Oracle RMU to commit the converted database to the
current version of Oracle Rdb before completing the restore
operation. Use this qualifier only when the backup file being
restored is from a previous version of Oracle Rdb. The conversion
is permanent and the database cannot be returned to the previous
version. The NoCommit qualifier instructs Oracle RMU not to
commit the converted database. In this case, you can rollback the
database to its original version using the RMU Convert command
with the Rollback qualifier, or you can permanently commit it to
the current version by issuing the RMU Convert command with the
Commit qualifier. It is important to either Commit or Rollback
the conversion after you have verified that the conversion
was successful otherwise unnecessary space is taken up in the
database to store the obsolete alternate version of the metadata.
(RMU will not let you convert to a newer version if the previous
Convert was never committed, even if it was years ago.)
The Commit qualifier is the default.
9 – Confirm
Confirm
Noconfirm
Specifies that RMU Restore notify you of the name of the database
on which you are performing the incremental restore operation.
You can thus be sure that you have specified the correct .rdb
file name to which the incremental backup file will be applied.
This is the default for interactive processing.
Confirmation is especially important on an incremental restore
operation if you have changed the .rdb file name or created a new
version of the database during a restore operation from the full
backup file. (You must specify the Root qualifier also to create
new version or change the .rdb file name.)
Specify the Noconfirm qualifier to have RMU Restore apply the
incremental backup file to the database without prompting for
confirmation. This is the default for batch processing.
RMU Restore ignores the Confirm and Noconfirm qualifiers unless
you use the Incremental qualifier.
10 – Directory
Directory=directory-spec
Specifies the default destination for the restored database
files. If you specify a file name or file extension, all restored
files are given that file name or file extension. There is no
default directory specification for this qualifier. If you do not
specify the Directory qualifier, RMU Restore attempts to restore
all the database files to the directories they were in at the
time the backup file was created; if those directories no longer
exist, the restore operation fails.
See the Usage Notes for information on how this qualifier
interacts with the Root and File qualifiers and for warnings
regarding restoring database files into a directory owned by a
resource identifier.
11 – Disk File
Disk_File[=(Reader_Threads=integer)]
Specifies that you want to perform a multithreaded restore
operation from disk files, floppy disks, or other disks external
to the PC. This qualifier must have been specified on the RMU
Backup command when the backup files from which you are restoring
were created.
The Reader_Threads keyword specifies the number of threads that
Oracle RMU should use when performing a multithreaded restore
operation from disk files. You can specify no more than one
reader thread per device specified on the command line (or in the
command parameter options file). By default, one reader thread is
used.
This qualifier and all qualifiers that control tape operations
(Label, Loader_Synchronization, Master, Media_Loader, and Rewind)
are mutually exclusive.
12 – Duplicate
Duplicate
Noduplicate
Specifies a new database with the same content but different
identity from that of the original database. The default is the
Noduplicate qualifier.
The Duplicate qualifier creates a copy of your database that is
not expected to remain in sequence with the original database.
Note that you cannot interchange after-image journal (.aij) files
between the original and duplicate copy of the database because
each database is unique.
You can create a duplicate database when you use the Duplicate
qualifier or create the original database again when you use the
Noduplicate qualifier.
The Duplicate qualifier conflicts with the Incremental, Area, and
Online qualifiers.
13 – Encrypt
Encrypt=({Value=|Name=}[,Algorithm=])
The Encrypt qualifier decrypts the save set file of a database
backup.
Specify a key value as a string or, the name of a predefined
key. If no algorithm name is specified the default is DESCBC.
For details on the Value, Name and Algorithm parameters see HELP
ENCRYPT.
This feature requires the OpenVMS Encrypt product to be installed
and licensed on this system.
14 – Global Buffers
Global_Buffers=global-buffer-options
Allows you to change the default global buffer parameters when
you restore a database. The following options are available:
o Disabled
Use this option to disable global buffering for the database
being restored.
o Enabled
Use this option to enable global buffering for the database
being restored. You cannot specify both the Global_
Buffers=Disabled and Global_Buffers=Enabled qualifiers in
the same RMU Restore command.
o Total=total-buffers
Use this option to specify the number of buffers available for
all users. The minimum value you can specify is 2; the maximum
value you can specify is the global buffer count stored in the
.rdb file.
o User_Limit=buffers-per-user
Use this option to specify the maximum number of buffers
available to each user.
If you do not specify a Global_Buffers qualifier, the database
is restored with the values that were in effect when the database
was backed up.
When you specify two or more options with the Global_Buffers
qualifier, use a comma to separate each option and enclose the
list of options within parentheses.
15 – Incremental
The Incremental qualifier restores a database from an incremental
backup file.
Use the Incremental qualifier only when you have first issued an
RMU Restore command that names the full backup file that was the
basis for this incremental backup file. Each incremental backup
file is tied to a particular full backup file.
After restoring both the full and the incremental backup files,
you have restored the database to the condition it was in when
you performed the incremental database backup operation.
By default, RMU Restore performs a full restore operation on the
backup file.
You cannot specify the After_Journal or Just_Corrupt qualifier
with the Incremental qualifier.
16 – Journal
Journal=file-name
Allows you to specify a journal file to be used to improve tape
performance by a restore operation (including a by-area or just-
corrupt restore operation).
The backup operation creates the journal file and writes to it
a description of the backup operation. This description contains
identification of the tape drives, the tape volumes and their
contents. The Journal qualifier directs RMU Restore to read the
journal file and select only the useful tape volumes.
The journal file must be the one created at the time the backup
operation was performed. If the wrong journal file is supplied,
RMU Restore returns an informational message and does not use the
specified journal file to select the volumes to be processed.
If you omit the Label qualifier, the restore operation creates a
list of volume labels from the contents of the journal file.
A by-area restore operation also constructs a list of useful
tape volume labels from the journal file; only those volumes are
mounted and processed.
17 – 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 command should be the same Label qualifier
you specified with the RMU Backup command that backed up your
database.
You can use the Label qualifier with indirect file references.
See the Indirect-Command-Files help entry for more information.
18 – 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 Reader_Threads=n
Use the Reader_Threads option to specify the number of backup
data streams to read from the Librarian utility. The value of
n can be from 1 to 99. The default is one reader thread. The
streams are named BACKUP_FILENAME.EXT, BACKUP_FILENAME.EXT02,
BACKUP_FILENAME.EXT03, up to BACKUP_FILENAME.EXT99. BACKUP_
FILENAME.EXT is the backup file name specified in the RMU
Backup command.
The number of reader threads specified for a database restore
from the Librarian utility should be equal to or less than the
number of writer threads specified for the database backup.
If the number of reader threads exceeds the number of writer
threads, the number of reader threads is set by Oracle RMU
to be equal to the number of data streams actually stored
in the Librarian utility by the backup. If the number of
reader threads specified for the restore is less than the
number of writer threads specified for the backup, Oracle RMU
will partition the data streams among the specified reader
threads so that all data streams representing the database are
restored.
The Volumes qualifier cannot be used with the Librarian
qualifer. Oracle RMU sets the volume number to be the actual
number of data streams stored in the specified Librarian
utility.
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 utility documentation for
the name and location of this image and how it should be
installed. For a parallel RMU backup, define RMU$LIBRARIAN_
PATH as a system-wide logical name so that the multiple
processes created by a parallel backup can all translate the
logical.
$ DEFINE /SYSTEM /EXECUTIVE_MODE -
_$ RMU$LIBRARIAN_PATH librarian_shareable_image.exe
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.
For a parallel RMU backup, the RMU$DEBUG_SBT logical should
be defined as a system logical so that the multiple processes
created by a parallel backup can all translate the logical.
The following lines are from a backup plan file created by the
RMU Backup/Parallel/Librarian command:
Backup File = MF_PERSONNEL.RBF
Style = Librarian
Librarian_trace_level = #
Librarian_logical_names = (-
logical_name_1=equivalence_value_1, -
logical_name_2=equivalence_value_2)
Writer_threads = #
The "Style = Librarian" entry specifies that the backup is going
to a Librarian utility. The "Librarian_logical_names" entry is
a list of logical names and their equivalence values. This is an
optional parameter provided so that any logical names used by a
particular Librarian utility can be defined as process logical
names before the backup or restore operation begins. For example,
some Librarian utilities provide support for logical names for
specifying catalogs or debugging.
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.
19 – Loader Synchronization
Loader_Synchronization
Allows you to preload tapes in order to minimize the need for
operator support. When you specify the Loader_Synchronization
qualifier and specify multiple tape drives, the restore operation
reads from the first set of tape volumes concurrently, then waits
until all concurrent tape operations conclude before assigning
the next set of tape volumes. This ensures that the tapes can be
loaded into the loaders or stackers in the order required by the
restore operation.
The Loader_Synchronization qualifier does result in reduced
performance. For maximal performance, no drive should remain
idle, and the next identified volume should be placed on the
first drive that becomes idle. However, because the order in
which the drives become idle depends on many uncontrollable
factors and cannot be predetermined, the drives cannot be
preloaded with tapes.
Because the cost of using the Loader_Synchronization qualifier is
dependent on the hardware configuration and the system load, the
cost is unpredictable. A 5% to 20% additional elapsed time for
the operation is typical. You must determine whether the benefit
of a lower level of operator support compensates for the loss of
performance. The Loader_Synchronization qualifier is most useful
for large restore operations.
The Loader_Synchronization qualifier has no effect unless you
specify the Volumes qualifier also.
20 – Local Buffers
Local_Buffers=local-buffer-options
Allows you to change the default local buffer parameters when you
restore a database. The following options are available:
o Number=number-buffers
Use this option to specify the number of local buffers
available for all users. You must specify a number between
2 and 32,767 for the number-buffers parameter.
o Size=buffer-blocks
The size (in blocks) for each buffer. You must specify a
number between 2 and 64 for the buffer-blocks parameter.
If you specify a value smaller than the size of the largest
page defined, RMU Restore automatically adjusts the size of
the buffer to hold the largest page defined. For example, if
you specify the Local_Buffers=Size=8 qualifier and the largest
page size for the storage areas in your database is 64 blocks,
RMU Restore automatically interprets the Local_Buffers=Size=8
qualifier as though it were a Local_Buffers=Size=64 qualifier.
The value you specify for the Size option determines the
number of blocks for each buffer, regardless of whether local
buffering or global buffering is enabled for the database.
If you do not specify a Local_Buffers qualifier, the database is
restored with the values that were in effect when the database
was backed up.
21 – Log
Log
Log=Brief
Log=Full
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,
or the Nolog qualifier to suppress this report. If you specify
the Log=Brief option, which is the default if you use the Log
option without a qualifier, the log contains the start and
completion time of each storage area. If you specify the Log=Full
option, the log also contains thread assignment and storage area
statistics messages.
If you do not specify the Log or the Nolog qualifier, the default
is the current setting of the DCL verify switch. (The DCL SET
VERIFY command controls the DCL verify switch.)
22 – Master
Master
Allows you to explicitly state how drives should be used when
they are to be accessed concurrently. This is a positional
qualifier that designates a tape drive as a master tape drive.
When the Master qualifier is used, it must be used on the first
drive specified. All additional drives become slaves to that
master until the end of the command line, or until the next
Master qualifier, whichever comes first.
If the Master qualifier is used on a drive that does not have
an independent I/O path (not a hardware master), performance
decreases.
If the Master qualifier is not used, and concurrent tape access
is requested (using the Volumes=n qualifier), RMU Restore uses
the same automatic configuration procedure it employs with the
backup operation to select the master drives.
Using the Master qualifier is an error if you do not specify
concurrent tape access (you do not specify the Volumes=n
qualifier). See the description of the Volumes qualifier for
further information on specifying concurrent tape access.
23 – Media Loader
Media_Loader
Nomedia_Loader
Use the Media_Loader qualifier to specify that the tape device
from which RMU Restore is reading the backup file 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
should recognize this fact. However, occasionally RMU Restore
does not recognize that a tape device has a loader or stacker.
Therefore, after reading the first tape, RMU Restore 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 behaves as though a tape device has a loader or
stacker when actually it does not.
If you find that RMU Restore is not recognizing that your
tape device has a loader or stacker, specify the Media_Loader
qualifier. If you find that RMU Restore expects a loader or
stacker when it should not, specify the Nomedia_Loader qualifier.
24 – New Version
New_Version
Nonew_Version
Specifies whether new versions of database files should be
produced if the destination device and directory contain a
previous version of the database files.
If you use the New_Version qualifier, the new database file
versions are produced. The New_Version qualifier conflicts with
the Incremental qualifier.
If you use the Nonew_Version qualifier, the default, an error
occurs if an old copy exists of any of the database files being
restored.
A restore operation that creates a new database root (.rdb) file
must always either disable after-image journaling or create a
new .aij file. Attempting to use a pre-existing .aij file with a
restored database corrupts the journal and makes future recovery
from .aij files impossible. The New_Version qualifier cannot and
does not apply to the .aij file.
25 – 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 accepts 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.
You cannot specify the Nodes_Max qualifier if you use the
Incremental or Area qualifier.
26 – Online
Online
Noonline
Specifies that the restore operation be performed while other
users are attached to the database. You can specify the online
qualifier only with the Area or Just_Corrupt qualifier. The pages
to be restored are locked for exclusive access, so the operation
is not compatible with any other use of the data in the specified
pages.
The default is the Noonline qualifier.
27 – Open Mode
Open_Mode=Automatic
Open_Mode=Manual
Allows you to change the mode for opening a database when you
restore that database. When you specify Open_Mode=Automatic,
users can invoke the database immediately after it is restored.
If you specify Open_Mode=Manual, an RMU Open command must be used
to open the database before users can invoke the database.
The Open_Mode qualifier also specifies the mode for closing a
database. If you specify Open_Mode=Automatic, you can also use
the Close_Wait qualifier to specify a time in minutes before the
database is automatically closed.
If you do not specify the Open_Mode qualifier, the database is
restored with the open mode of the database that was in effect
when the database was backed up.
28 – 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 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. You can include any or all of the area
qualifiers in the options file. (See the format help entry under
this command for the list of Area qualifiers.) You can use the
DCL line continuation character, a hyphen (-), or the comment
character (!) in the options file. The default file extension is
.opt.
29 – Page Buffers
Page_Buffers=number-buffers
Specifies the maximum number of buffers Oracle Rdb uses during
the RMU Restore operation while the database files are being
created. The value of the Page_Buffers qualifier can range from
1 to 5. The default is 3 buffers. Values larger than 3 might
improve performance, especially during incremental restore
operations.
When RMU Restore enters the stage of reconstructing internal
structures at the end of the restore operation, a high value
for the Page_Buffers qualifier can be useful for very large
databases. However, the cost of using these extra buffers is
that memory use is high. Thus, the trade-off during a restore
operation is memory use against performance.
30 – Path
Path=cdd-path
Specifies a data dictionary path into which the database
definitions be integrated. If you do not specify the Path
qualifier, RMU Restore uses the CDD$DEFAULT logical name value
of the user who entered the RMU Restore command.
If you specify a relative path name, Oracle Rdb appends the
relative path name you enter to the CDD$DEFAULT value. If the
cdd-path parameter contains nonalphanumeric characters, you must
enclose it within quotation marks ("").
Oracle Rdb ignores the Path qualifier if you use the Nocdd_
Integrate qualifier or if the data dictionary is not installed
on your system.
31 – Prompt
Prompt=Automatic
Prompt=Operator
Prompt=Client
Specifies where server prompts are to be sent. When you specify
Prompt=Automatic, prompts are sent to the standard input device,
and when you specify Prompt=Operator, prompts are sent to the
server console. When you specify Prompt=Client, prompts are sent
to the client system.
32 – Recovery
Recovery[=Aij_Buffers=n]
Norecovery
The Recovery=Aij_Buffers=n qualifier allows you to specify the
number of recovery buffers to use during an automatic recovery.
The default value of n is 100 recovery buffers.
The Recovery qualifier explicitly specifies that RMU Restore
should attempt an automatic recovery of the .aij files during the
restore operation.
Specify either the Recover=Aij_Buffers=n qualifier and the
Recovery qualifier only if .aij files are being retained. If
you specify either qualifier in a situation where .aij files
are not retained (the Aij_Options, After_Journal, or Duplicate
qualifier has been specified), a warning message is displayed and
RMU Restore performs the restore operation without attempting to
recover the .aij files.
The Norecovery qualifier specifies that RMU Restore should not
attempt an automatic recovery of the .aij files during the
restore operation. Specify this qualifier if you want to use
the RMU Recover command with the Until qualifier or if you intend
to perform an incremental restore operation.
33 – Rewind
Rewind
Norewind
Specifies that 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 returns an error message if you use these
qualifiers and the target device is not a tape device.
34 – Root
Root=root-file-spec
Specifies the database root (.rdb) file specification of the
restored database. 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.
35 – Transaction Mode
Transaction_Mode=(mode-list)
Sets the allowable transaction modes for the database root
file restored by the restore operation. The primary use of
this qualifier is when you restore a backup file (of a master
database) to create a Hot Standby database. Because only read-
only transactions are allowed on a standby database, you should
use the Transaction_Mode=Read_Only qualifier setting. This
setting prevents modifications to the standby database at all
times, even when replication operations are not active. For more
information on Hot Standby see the Oracle Rdb7 and Oracle CODASYL
DBMS: Guide to Hot Standby Databases. 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
Your restore operation must include the database root file.
Otherwise, RMU Restore returns the CONFLSWIT error when you issue
an RMU Restore command with the Transaction_Mode qualifier.
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, it indicates
that a mode is not an allowable access mode. For example, if
you specify the Noexclusive_Write access mode, it indicates
that exclusive write is not an allowable access mode for the
restored 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.
36 – 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.
You cannot specify the Users_Max qualifier if you use the
Incremental qualifier or the Area qualifier.
37 – Volumes
Volumes = n
Allows you to specify that concurrent tape access is to be used
to accelerate the restore operation.
The Volumes qualifier indicates concurrent tape access and
specifies the number of tape volumes in the backup file. The
number of volumes must be specified accurately for the restore
operation to complete.
If you are restoring from a multidisk backup file, the value of
"n" indicates the number of disk devices containing backup files
needed for the restore operation.
If you do not specify the Volumes qualifier, the restore
operation does not use concurrent tape access.
38 – Blocks Per Page
Blocks_Per_Page=integer
Lets you restore a database with larger mixed page sizes than
existed in the original database. This creates new free space on
each page in the storage area file and does not interfere with
record clustering. RMU Restore ignores this qualifier when it
specifies an integer less than or equal to the current page size
of the area.
You might want to increase the page size in storage areas
containing hash indexes that are close to full. By increasing
the page size in such a situation, you prevent the storage area
from extending.
39 – Extension
Extension=Disable
Extension=Enable
Allows you to change the automatic file extension attribute
when you restore a database. These qualifiers are positional
qualifiers.
Use the Extension=Disable qualifier to disable automatic file
extension for a storage area.
Use the Extension=Enable qualifier to enable automatic file
extension for a storage area.
If you do not specify the Extension=Disable or Extension=Enable
qualifier, the storage areas are restored with the automatic file
extension attributes that were in effect when the database was
backed up.
40 – File
File=file-spec
Requests that the storage area to which this qualifier is applied
be restored in the specified location.
This qualifier is not valid for single-file databases. This is a
positional qualifier.
See the Usage Notes for information on how this qualifier
interacts with the Root, Directory, and Snapshot qualifiers and
for warnings regarding restoring database files into a directory
owned by a resource identifier.
41 – Just Corrupt
Just_Corrupt
This qualifier replaces the Just_Pages qualifier beginning in
Oracle Rdb V7.0.
Allows you to restore the corrupt pages and areas in the
database as recorded in the corrupt page table (CPT). The CPT
is maintained in the .rdb file. (Note that if the corrupt page
table becomes full, the area with the highest number of corrupt
pages is marked corrupt and the individual pages for that area
are removed from the CPT.)
Often, only one or a few pages in the database are corrupted
due to hardware or software faults. The Just_Corrupt qualifier
allows you to recover that database in minimal time with minimal
interference; availability of the uncorrupted data is unaffected.
It allows you to restrict the restoration to the pages (or areas)
logged as corrupt in the corrupt page table.
The Just_Corrupt qualifier is a positional qualifier. If you use
it in the global position, RMU Restore restores all the corrupt
pages and all the corrupt areas as logged in the corrupt page
table. If you use it in the local position, RMU Restore restores
only the corrupt pages (or the entire area) of the area name it
modifies.
It is possible to mix restoration of complete areas and just
corrupt pages in the same command. The following example restores
all of AREA_1 (regardless of whether or not it is corrupt), but
just the corrupt pages (logged to the CPT) in AREA_2.
$ RMU/RESTORE/AREA backup_file AREA_1, AREA_2/JUST_CORRUPT
Note that when the Just_Corrupt qualifier is used globally, all
the corrupt pages logged to the CPT for the areas specified
are restored. For example, the following command restores all
the corrupt pages logged to the CPT for AREA_1 and AREA_2.
(However, if one of the areas specified contains no corruptions,
an informational message is displayed and that area is not
restored.)
$ RMU/RESTORE/JUST_CORRUPT backup_file /AREA AREA_1, AREA_2
Restoration of corrupt pages and area can be performed on line.
Online operations lock only the corrupt pages or areas for the
duration of the restore operation. The remainder of the storage
area can be read or updated by an application. When an entire
area is restored on line, applications are locked out of the
entire area for the duration of the restore operation.
There are some restrictions on the use of the Just_Corrupt
qualifier:
o The backup file must be a full backup file that contains the
selected area.
o When space area management (SPAM) pages are restored, RMU
Restore rebuilds the SPAM page using information from the
range of data pages that the SPAM page manages.
o Area bit map (ABM) pages can be restored, but their content
is not reconstructed. If ABM pages have been corrupted,
regenerate them with the RMU Repair command.
o A by-page restore operation is like a by-area restore
operation in that after-image journal (AIJ) recovery is
required to make the restored data consistent with the rest
of the database.
Once the pages are restored, access to these restored pages is
prohibited until they are made consistent. Inconsistent pages
are stored in the corrupt page table (CPT) and have their
timestamp field flagged by Oracle Rdb.
o You can also use the Just_Corrupt qualifier in a restore
options file. However, you cannot use any of the following
qualifiers with the Just_Corrupt qualifier (neither within an
options file nor on the command line):
- Blocks_Per_Page
- Extension
- File
- Incremental
- Read_Only
- Read_Write
- Snapshot
- Spams
- Thresholds
You can use the Just_Corrupt qualifier in conjunction with
the Journal=file qualifier to greatly speed up processing of
a large tape backup file. When you use the Journal qualifier,
only those tapes containing corrupt pages, areas, or both, are
mounted and processed.
42 – Just Pages
Just_Pages[=(p1,p2,...)]
This qualifier is replaced with the Just_Corrupt qualifier
beginning in Oracle Rdb V7.0. See the description of the Just_
Corrupt qualifier.
43 – Read Only
Use the Read_Only qualifier to change a read/write storage area
or a write-once storage area to a read-only storage area.
If you do not specify the Read_Only or the Read_Write qualifier,
the storage areas are restored with the read/write attributes
that were in effect when the database was backed up.
This is a positional qualifier.
44 – Read Write
Use the Read_Write qualifier to change a read-only storage area
or a write-once storage area to a read/write storage area.
If you do not specify the Read_Only or the Read_Write qualifier,
the storage areas are restored with the read/write attributes
that were in effect when the database was backed up.
This is a positional qualifier.
45 – Snapshot
Snapshot=(Allocation=n,File=file-spec)
If you specify the Allocation parameter, specifies the snapshot
file allocation size in n pages for a restored area. If you
specify the File parameter, specifies a new snapshot file
location for the restored storage area to which it is applied.
You can specify the Allocation parameter only, the File parameter
only, or both parameters; however, if you specify the Snapshots
qualifier, you must specify at least one parameter.
This is one of the commands used to alter the parameters of the
restored database from those defined at the time of the database
backup. Others are /DIRECTORY, /ROOT and /FILE.
See the Usage Notes for information on how this qualifier
interacts with the Root, File, and Directory qualifiers.
The Shapshot qualifier is a positional qualifier. It can be used
locally or globally, depending on where the qualifier is placed
on the command line. See Examples 22 and 23.
To save read/write disk space, you can specify that less space be
allocated for the storage area's .snp file when it remains as a
read/write file on a read/write disk. If the keyword Allocation
is omitted, the original allocation is used. This qualifier is
not valid for single-file databases.
You cannot specify an .snp file name for a single-file database.
When you create an .snp file for a single-file database, Oracle
Rdb does not store the file specification of the .snp file.
Instead, it uses the file specification of the database root
(.rdb) file to determine the file specification of the .snp file.
If you want to place the .snp file on a different device or
directory, Oracle Corporation recommends that you create a
multifile database. However, you can work around the restriction
by defining a search list for a concealed logical name. (However,
do not use a nonconcealed rooted logical name to define database
files; a database created with a non-concealed rooted logical
name can be backed up, but may not restore correctly when you
attempt to restore the files to a new directory.)
To create a database with an .snp file on a different device
or directory, define a search list by using a concealed logical
name. Specify the location of the root file as the first item in
the search list. When you create the database, use the logical
name for the directory specification. Then, copy the .snp file
to the second device. The following example demonstrates the
workaround:
$ ! Define a concealed logical name.
$ DEFINE /TRANS=CONCEALED/SYSTEM TESTDB USER$DISK1:[DATABASE], -
_$ USER$DISK2:[SNAPSHOT]
$
$ SQL
SQL> -- Create the database.
SQL> --
SQL> CREATE DATABASE FILENAME TESTDB:TEST;
SQL> EXIT
$ !
$ ! Copy the snapshot (.snp) file to the second disk.
$ COPY USER$DISK1:[DATABASE]TEST.SNP -
_$ USER$DISK2:[SNAPSHOT]TEST.SNP
$ !
$ ! Delete the snapshot (.snp) file from the original disk.
$ DELETE USER$DISK1:[DATABASE]TEST.SNP;
46 – Spams
Spams
Nospams
Enables the space area management (SPAM) pages for the specified
area. The Nospams qualifier disables the SPAM pages for the
specified area. The default is to leave the attribute unchanged.
The Spams and Nospams qualifiers are not allowed for a storage
area that has a uniform page format. This is a positional
qualifier.
47 – Thresholds
Thresholds=(val1[,val2[,val3]])
Specifies a storage area's fullness percentage threshold. You
can adjust SPAM thresholds to improve future space utilization in
the storage area. Each threshold value represents a percentage of
fullness on a data page. When a data page reaches the percentage
of fullness defined by a given threshold value, the space
management entry for the data page is updated to contain that
threshold value.
The Thresholds qualifier applies only to storage areas with a
mixed page format.
If you do not use the Thresholds qualifier with the RMU Restore
command, Oracle Rdb uses the storage area's original thresholds.
This is a positional qualifier.
See the Oracle Rdb7 Guide to Database Performance and Tuning for
more information on setting SPAM thresholds.