Permits you to move one or more storage areas to different disks.
You can also choose to move the database root file to a different
disk.
1 – Description
The RMU Move_Area command lets you modify certain area parameters
when the move operation is performed. All the files are processed
simultaneously during the move operation. The performance of
the RMU Move_Area command is similar to that of the RMU Backup
command, and it eliminates the need for intermediate storage
media.
Note that when a snapshot file is moved, Oracle RMU does not
actually move the snapshot file; instead, Oracle RMU re-creates
and initializes the snapshot file in the specified location. See
the description of the Snapshot qualifier for more information
about using this qualifier, including information on its proper
usage.
NOTE
You must perform a full and complete Oracle RMU backup
operation immediately after the Oracle RMU move area
operation completes to ensure that the database can be
properly restored after a database failure or corruption.
2 – Format
(B)0[mRMU/Move_Area root-file-spec storage-area-list
[4mCommand[m [4mQualifiers[m x [4mDefaults[m
x
/[No]After_Journal[=file-spec] x See description
/[No]Aij_Options[=journal-opts-file] x See description
/All_Areas x See description
/[No]Area x See description
/[No]Cdd_Integrate x Nocdd_Integrate
/[No]Checksum_Verification x /Checksum_Verification
/Directory=directory-spec x None
/[No]Log x Current DCL verify value
/Nodes_Max=n x Keep current value
/[No]Online x Noonline
/Option=file-spec x None
/Page_Buffers=n x n=3
/Path=cdd-path x Existing value
/[No]Quiet_Point x /Quiet_Point
/Root=file-spec x None
/Threads=n x /Threads=10
/Users_Max=n x Keep current value
(B)0[m x
[4mFile[m [4mor[m [4mArea[m [4mQualifiers[m x [4mDefaults[m
x
/Blocks_Per_Page=n x None
/Extension={Disable | Enable } x Current value
/File=file-spec x None
/Read_Only x Current value
/Read_Write x Current value
/Snapshots=(Allocation=n,File=file-spec) x None
/[No]Spams x Leave attribute unchanged
/Thresholds=(n,n,n) x None
3 – Parameters
3.1 – root-file-spec
The name of the database root file for the database whose storage
areas you want to move.
3.2 – storage-area-list
The name of one or more storage areas that you want to move.
4 – Command Qualifiers
4.1 – 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 after-image journal
(.aij) files.
Specifies how Oracle RMU 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, Oracle RMU enables after-image journaling and
creates a new extensible after-image journal (.aij) file for
the database.
o If you specify the After_Journal qualifier but do not
provide a file specification, Oracle RMU enables after-image
journaling and creates a new extensible .aij file for the
database with the same name as, but a different version number
from, the .aij file for the database root file being moved.
o If you specify the Noafter_Journal qualifier, Oracle RMU
disables after-image journaling and does not create a new
.aij file.
o If you do not specify an After_Journal, Noafter_Journal,
Aij_Options, or Noaij_Options qualifier, Oracle RMU retains
the original journal setting (enabled or disabled) and the
original .aij file state.
You can only specify one, or none, of the following after-image
journal qualifiers in a single RMU Move_Area command: After_
Journal, Noafter_Journal, Aij_Options, or Noaij_Options.
You cannot use the After_Journal qualifier to create fixed-size
.aij files; use the Aij_Options qualifier.
You can facilitate recovery by creating a new .aij file because a
single .aij file cannot be applied across a move area operation
that changes an area page size. A single .aij file cannot be
applied across a move operation because the move operation is
never recorded in the .aij file (and therefore the increase in
page size is also not journaled). Therefore, when you attempt
to recover the database, the original page size is used for
recovery purposes. So, if the .aij file contains database insert
transactions, these updates might have more free space associated
with them than is available on the original page size. This
results in an inability to recover the insert transaction, which
in turn results in a bugcheck and a corrupted database.
This qualifier is valid only when no users are attached to the
database and only when the root file is moved.
4.2 – Aij Options
Aij_Options[=journal-opts-file]
Noaij_Options
Specifies how Oracle RMU 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, Oracle RMU enables journaling and creates
the .aij file or files you specify for the database. If
only one .aij file exists for the database, it will be an
extensible .aij file. If two or more .aij files are created
for the database, 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, Oracle RMU disables journaling and does not
create any new .aij files.
o If you specify the Noaij_Options qualifier, Oracle RMU retains
the original journal setting (enabled or disabled) and retains
the original .aij file.
o If you do not specify an After_Journal, Noafter_Journal,
Aij_Options, or Noaij_Options qualifier, Oracle RMU retains
the original journal setting (enabled or disabled) and the
original .aij file state.
See Show After_Journal for information on the format of a
journal-opts-file.
Note that you cannot use the RMU Move_Area command with the
Aij_Options qualifier to alter the journal configuration.
However, you can use it to define a new after-image journal
configuration. When you use it to define a new after-image
journal configuration, it does not delete the journals in the
original configuration. Those can still be used for recovery.
If you need to alter the after-image journal configuration, you
should use the RMU Set After_Journal command.
The Aij_Options qualifier is valid only when no users are
attached to the database and only when the root file is moved.
4.3 – All Areas
All_Areas
Noarea
Specifies that all database storage areas are to be moved. If
you specify the All_Areas qualifier, you do not need to specify a
storage-area-list.
By default, only areas specified in the storage-area-list are
moved.
4.4 – Area
Area
Noarea
NOTE
Due to the confusing semantics of the Area and Noarea
qualifiers, the Area and Noarea qualifiers are deprecated.
Oracle Corporation recommends that you use one of the
following methods to specify areas to be moved:
o To move all the storage areas in the database use the
All_Areas qualifier and do not specify a storage-area-
list parameter
o To move only selected areas in the database, specify the
storage-area-list parameter or use the Options qualifier
and specify an options file.
o To move only the database root file for a multifile
database, or to move an entire single-file database,
specify the root qualifier and do not specify a storage-
area-list parameter.
Controls whether specific storage areas are moved. If you specify
the Area qualifier, only the storage areas specified in the
option file or the storage-area-list are moved. If you specify
Noarea, all the storage areas in the database are moved.
The default is the Area qualifier.
4.5 – Cdd Integrate
Cdd_Integrate
Nocdd_Integrate
Integrates the metadata from the root (.rdb) file of the moved
database 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 move operation.
You can use the Nocdd_Integrate qualifier even if the DICTIONARY
IS REQUIRED clause was used when the database being moved 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.
The Nocdd_Integrate qualifier is the default.
4.6 – Checksum Verification
Checksum_Verification
Nochecksum_Verification
Requests that the page checksum be verified for each page moved.
The default is to perform this verification.
The Checksum_Verification qualifier uses CPU resources but can
provide an extra measure of confidence in the quality of the data
being moved.
Use of the Checksum_Verification qualifier offers an additional
level of data security when the database employs disk striping
or RAID (redundant arrays of inexpensive disks) technology. These
technologies fragment data over several disk drives, and use
of the Checksum_Verification qualifier permits Oracle RMU to
detect the possibility that the data it is reading from these
disks has been only partially updated. If you use either of these
technologies, you should use the Checksum_Verification qualifier.
Oracle Corporation recommends that you use the Checksum_
Verification qualifier with all move operations where integrity
of the data is essential.
4.7 – Directory
Directory=directory-spec
Specifies the destination directory for the moved database files.
Note that if you specify a file name or file extension, all moved
files are given that file name or file extension. There is no
default directory specification for this qualifier.
See the Usage Notes for information on how this qualifier
interacts with the Root, File, and Snapshot qualifiers and for
warnings regarding moving database files into a directory owned
by a resource identifier.
If you do not specify this qualifier, Oracle RMU attempts to move
all the database files (unless they are qualified with the Root,
File, or Snapshot qualifier) to their current location.
4.8 – Log
Log
Nolog
Specifies whether the processing of the command is reported to
SYS$OUTPUT. Specify the Log qualifier to request log output and
the Nolog qualifier to prevent it. 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.)
4.9 – Nodes Max
Nodes_Max=n
Specifies a new value for the database maximum node count
parameter. The default is to leave the value unchanged.
Use the Nodes_Max qualifier only if you move the database root
file.
4.10 – Online
Online
Noonline
Allows the specified storage areas to be moved without taking
the database off line. This qualifier can be used only when you
specify the storage-area-list parameter, or when you specify the
Options=file-spec qualifier. The default is Noonline. You cannot
move a database root file when the database is on line. The Root
qualifier cannot be specified with the Online qualifier in an RMU
Move_Area command.
4.11 – Option
Option=file-spec
Specifies an options file containing storage area names, followed
by the storage area qualifiers that you want applied to that
storage area. 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
Thresholds
If you specify the Snapshot qualifier, you must also move the
corresponding data files at the same time. To move a snapshot
file independently of its corresponding data file, use the RMU
Repair command with the Initialize=Snapshots=Confirm qualifier.
You can use the DCL line continuation character, a hyphen (-),
or the comment character (!) in the options file.
There is no default for this qualifier. Example 3 in the Examples
help entry under this command shows the use of an options file.
If the Option qualifier is specified, the storage-area-list
parameter is ignored.
4.12 – Page Buffers
Page_Buffers=n
Specifies the number of buffers to be allocated for each file
to be moved. The number of buffers used is twice the number
specified; half are used for reading the file and half for
writing the moved files. Values specified with the Page_Buffers
qualifier can range from 1 to 5. The default value is 3. Larger
values might improve performance, but they increase memory usage.
4.13 – Path
Path=cdd-path
Specifies a data dictionary path into which the definitions of
the moved database will be integrated. If you do not specify
the Path qualifier, Oracle RMU uses the CDD$DEFAULT logical name
value of the user who enters the RMU Move_Area 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.
4.14 – Quiet Point
Quiet_Point
Noquiet_Point
Allows you to specify that a database move operation is to occur
either immediately or when a quiet point for database activity
occurs. A quiet point is defined as a point where no active
update transactions are in progress in the database.
When you specify the Noquiet_Point qualifier, Oracle RMU proceeds
with the move operation as soon as the RMU Move_Area command is
issued, regardless of any update transaction activity in progress
in the database. Because Oracle RMU must acquire exclusive locks
on the physical and logical areas for the areas being moved,
the move operation fails if there are any active transactions
with exclusive locks on storage areas that are being moved.
However, once Oracle RMU has successfully acquired all the needed
concurrent-read storage area locks, it should not encounter any
further lock conflicts. If a transaction is started that causes
Oracle Rdb to request exclusive locks on the areas that are in
the process of being moved, that transaction either waits or
gets a lock conflict error, but the move area operation continues
unaffected.
If you intend to use the Noquiet_Point qualifier with a move
procedure that previously specified the Quiet_Point qualifier
(or did not specify either the Quiet_Point or the Noquiet_Point
qualifier), you should examine any applications that execute
concurrently with the move operation. You might need to modify
your applications or your move procedure to handle the lock
conflicts that can occur when you specify the Noquiet_Point
qualifier.
When you specify the Quiet_Point qualifier, the move operation
begins when a quiet point is reached.
The default is Quiet_Point.
4.15 – Root
Root=file-spec
Requests that the database root file be moved to the specified
location. If not specified, the database root file is not moved.
You must specify the Root qualifier when you use the RMU Move_
Area command on a single-file database. If you omit the Root
qualifier, you receive an error message. When you specify the
Root qualifier, specify the location where you want the root file
moved. For example:
$ RMU/MOVE_AREA/ROOT=DISK1:[DATABASE.TEST] MF_PERSONNEL
See the Usage Notes for information on how this qualifier
interacts with the Directory, File, and Snapshot qualifiers.
4.16 – Threads=number
Threads=number
Specifies the number of reader threads to be used by the move
process.
RMU creates so called internal 'threads' of execution to read
data from one specific storage area. Threads run quasi-parallel
within the process executing the RMU image. Each thread generates
its own I/O load and consumes resources like virtual address
space and process quotas (e.g. FILLM, BYTLM). The more threads,
the more I/Os can be generated at one point in time and the more
resources are needed to accomplish the same task.
Performance increases with more threads due to parallel
activities which keeps disk drives busier. However, at a certain
number of threads, performance suffers because the disk I/O
subsystem is saturated and I/O queues build up for the disk
drives. Also the extra CPU time for additional thread scheduling
overhead reduces the overall performance. Typically 2-5 threads
per input disk drive are sufficient to drive the disk I/O
susbsystem at its optimum. However, some controllers may be
able to handle the I/O load of more threads, for example disk
controllers with RAID sets and extra cache memory.
In a move operation, one thread moves the data of one storage
area at a time. If there are more storage areas to be moved than
there are threads, then the next idle thread takes on the next
storage area. Storage areas are moved in order of the area size
- largest areas first. This optimizes the overall elapsed time
by allowing other threads to move smaller areas while an earlier
thread is still working on a large area. If no threads qualifier
is specified then 10 threads are created by default. The minimum
is 1 thread and the maximum is the number of storage areas to be
moved. If the user specifies a value larger than the number of
storage areas, then RMU silently limits the number of threads to
the number of storage areas.
For a move operation, you can specify a threads number as low as
1. Using a threads number of 1 generates the smallest system
load in terms of working set usage and disk I/O load. Disk
I/O subsystems most likely can handle higher I/O loads. Using
a slightly larger value than 1 typically results in faster
execution time.
4.17 – Users Max
Users_Max=n
Specifies a new value for the database maximum user count
parameter.
The default is to leave the value unchanged.
Use the Users_Max qualifier only if you move the database root
file.
4.18 – Blocks Per Page
Blocks_Per_Page=n
Specifies a new page size for the storage area to which it is
applied. You cannot decrease the page size of a storage area.
If you attempt to change the page size during an online Move_
Area operation, you might receive a PAGESIZETOOBIG error message.
Changing the page size sometimes requires that Oracle Rdb change
the buffer size for the database also (because buffers must be
large enough to hold at least one page from each area). However,
the buffer size cannot change if other users are accessing the
database.
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.
The Blocks_Per_Page qualifier is a positional qualifier.
4.19 – Extension
Extension=Disable
Extension=Enable
Allows you to change the automatic file extension attribute when
you move a storage area.
Use the Extension=Disable qualifier to disable automatic file
extensions for one or more storage areas.
Use the Extension=Enable qualifier to enable automatic file
extensions for one or more storage areas.
If you do not specify the Extension=Disable or the
Extension=Enable qualifier, the storage areas is moved with the
automatic file extension attributes that are currently in effect.
The Extension qualifier is a positional qualifier.
4.20 – File
File=file-spec
Requests that the storage area to which this qualifier is applied
be moved to the specified location.
The File qualifier is a positional qualifier. This qualifier is
not valid for single-file databases.
See the Usage Notes for information on how this qualifier
interacts with the Root, Snapshot, and Directory qualifiers.
4.21 – 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 moved with the read/write attributes that
are currently in effect for the database.
This is a positional qualifier.
4.22 – 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 moved with the read/write attributes that
are currently in effect for the database.
This is a positional qualifier.
4.23 – Snapshots
Snapshots=(Allocation=n,File=file-spec)
Allows you to specify a new snapshot file allocation size, a new
snapshot file location, or both, for the storage area to which
the qualifier is applied.
Use the Allocation=n option to specify the snapshot file
allocation size in n pages; use the File=file-spec option to
specify a new file location for the snapshot file associated with
the area being moved.
Note that when you specify a new file location for the snapshot
file, the snapshot file is not actually moved; instead, Oracle
RMU creates and initializes a new snapshot file in the specified
directory. However, if a snapshot file is accidentally deleted or
becomes corrupt, using this qualifier is not the recommended or
supported method for re-creating the snapshot file. Use the RMU
Repair command instead. See the Repair help entry for information
on using the RMU Repair command to re-create and initialize a
deleted or corrupted snapshot file.
If the keyword Allocation is omitted, the original allocation is
used, not the storage area's current allocation size.
You cannot specify a snapshot file name for a single-file
database. When you create a snapshot file, Oracle Rdb does not
store the file specification of the snapshot file. Instead, it
uses the file specification of the root file (.rdb) to determine
the file specification of the snapshot file.
See the Usage Notes for information on placing a snapshot file on
a different device or directory when your database is a single-
file database and for information on how this qualifier interacts
with the Root, File, and Directory qualifiers.
The Snapshot qualifier is a positional qualifier.
4.24 – Spams
Spams
Nospams
Specifies whether to enable the creation of space area management
(SPAM) pages or to disable the creation of SPAM pages (Nospams)
for specified storage areas when converting read/write storage
areas to write-once storage areas or vice versa. This qualifier
is not permitted with a storage area that has a uniform page
format.
When SPAM pages are disabled in a read/write storage area, the
SPAM pages are initialized, but they are not updated.
The Spams qualifier is a positional qualifier.
4.25 – Thresholds
Thresholds=(n,n,n)
Specifies new SPAM thresholds for the storage area to which it is
applied (for a mixed page format storage area). The thresholds of
a storage area with a uniform page format cannot be changed.
See the Oracle Rdb7 Guide to Database Performance and Tuning for
information on setting SPAM thresholds.
The Thresholds qualifier is a positional qualifier.
5 – Usage Notes
o To use the RMU Move_Area command for a database, you must have
the RMU$MOVE privilege in the root file access control list
(ACL) for the database or have the OpenVMS SYSPRV or BYPASS
privilege.
o You cannot disable extensions of snapshot (.snp) files.
o The parameter (file and area) qualifiers for the RMU Move_Area
command have positional semantics. See the Command_Qualifiers
help entry for more information on parameter qualifiers.
o The RMU Move_Area command provides four qualifiers, Directory,
Root, File, and Snapshots, that allow you to specify the
target for the moved files. The target can be just a
directory, just a file name, or a directory and file name.
If you use all or some of these four qualifiers, apply them as
follows:
- If you want to move the database root, use the Root
qualifier to indicate the target for the moved database
root file.
- Use local application of the File qualifier to specify the
target for the moved storage area or areas.
- Use local application of the Snapshots qualifier to specify
the target for the moved snapshot file or files.
- Use the Directory qualifier to specify a default target
directory. The default target directory is the directory to
which all storage area and snapshot files not qualified
with the File or Snapshot qualifier are moved. It is
also the default directory for files qualified with the
Root, File, or Snapshot qualifier if the target for these
qualifiers does not include a directory specification.
Note the following when using these qualifiers:
- Global application of the File qualifier when the target
specification includes a file name causes Oracle RMU
to move all of the specified storage areas to different
versions of the same file name. This creates a database
that is difficult to manage.
- Global application of the Snapshot qualifier when the
target specification includes a file name causes Oracle RMU
to move all of the specified snapshot files to different
versions of the same file name. This creates a database
that is difficult to manage.
- Specifying a file name or extension with the Directory
qualifier is permitted, but causes Oracle RMU to move all
of the specified files (except those specified with the
File or Root qualifier) to different versions of the same
file name. Again, this creates a database that is difficult
to manage.
See Example 6.
o You must specify the Root qualifier when you use the RMU Move_
Area command on a single-file database. If you omit the Root
qualifier, you receive an error message. If you want to place
the snapshot file for a single-file database on a different
device or directory from the root file, Oracle Corporation
recommends that you create a multifile database. However,
you can work around this 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 single-file database with a snapshot file on a
different device or directory from the root file, 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 snapshot 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 file to the second disk.
$ COPY USER$DISK1:[DATABASE]TEST.SNP USER$DISK2:[SNAPSHOT]TEST.SNP
$ !
$ ! Delete the snapshot file from the original disk.
$ DELETE USER$DISK1:[DATABASE]TEST.SNP;
o There are no restrictions on the use of the Nospams qualifier
option with mixed page format storage areas, but the use of
the Nospams qualifier typically causes severe performance
degradation. The Nospams qualifier is useful only where
updates are rare and batched, and access is primarily by
database key (dbkey).
6 – Examples
Example 1
If a storage area is on a disk that is logging error messages,
you can move the storage area to another disk by using the RMU
Move_Area command. The following command moves the DEPARTMENTS
storage area (departments.rda) and the DEPARTMENTS snapshot
file (departments.snp) of the mf_personnel database to the
DDV21:[RICK.SQL] directory:
$ RMU/MOVE_AREA MF_PERSONNEL DEPARTMENTS /DIRECTORY=DDV21:[RICK.SQL]
Example 2
The following command moves the EMPIDS_LOW, EMPIDS_MID, and
EMPIDS_OVER storage areas for the mf_personnel database to the
DISK2:[USER2] directory. The Extension=Disable qualifier disables
automatic file extensions for the EMPIDS_LOW, EMPIDS_MID, and
EMPIDS_OVER storage area (.rda) files when they are moved to the
DISK2:[USER2] directory:
$ RMU/MOVE_AREA/EXTENSION=DISABLE/DIRECTORY=DISK2:[USER2] -
_$ mf_personnel EMPIDS_LOW,EMPIDS_MID,EMPIDS_OVER
Example 3
The following RMU Move_Area command uses an options file to
specify that the storage area files and snapshot files be moved
to different disks. Note that storage area snapshot (.snp)
files are located on different disks from one another and from
their associated storage area (.rda) files; this is recommended
for optimal performance. (This example assumes that the disks
specified for each storage area file in options_file.opt are
different from those where the storage area files currently
reside.)
$ RMU/MOVE_AREA/OPTIONS=OPTIONS_FILE.OPT MF_PERSONNEL
The following command displays the contents of the options file:
$ TYPE options_file.opt
EMPIDS_LOW /FILE=DISK1:[CORPORATE.PERSONNEL]EMPIDS_LOW.RDA -
/SNAPSHOT=(FILE=DISK2:[CORPORATE.PERSONNEL]EMPIDS_LOW.SNP)
EMPIDS_MID /FILE=DISK3:[CORPORATE.PERSONNEL]EMPIDS_MID.RDA -
/SNAPSHOT=(FILE=DISK4:[CORPORATE.PERSONNEL]EMPIDS_MID.SNP)
EMPIDS_OVER /FILE=DISK5:[CORPORATE.PERSONNEL]EMPIDS_OVER.RDA -
/SNAPSHOT=(FILE=DISK6:[CORPORATE.PERSONNEL]EMPIDS_OVER.SNP)
DEPARTMENTS /FILE=DISK7:[CORPORATE.PERSONNEL]DEPARTMENTS.RDA -
/SNAPSHOT=(FILE=DISK8:[CORPORATE.PERSONNEL]DEPARTMENTS.SNP)
SALARY_HISTORY /FILE=DISK9:[CORPORATE.PERSONNEL]SALARY_HISTORY.RDA -
/SNAPSHOT=(FILE=DISK10:[CORPORATE.PERSONNEL]SALARY_HISTORY.SNP)
JOBS /FILE=DISK7:[CORPORATE.PERSONNEL]JOBS.RDA -
/SNAPSHOT=(FILE=DISK8:[CORPORATE.PERSONNEL]JOBS.SNP)
EMP_INFO /FILE=DISK9:[CORPORATE.PERSONNEL]EMP_INFO.RDA -
/SNAPSHOT=(FILE=DISK10:[CORPORATE.PERSONNEL]EMP_INFO.SNP)
RESUME_LISTS /FILE=DISK11:[CORPORATE.PERSONNEL]RESUME_LISTS.RDA -
/SNAPSHOT=(FILE=DISK12:[CORPORATE.PERSONNEL]RESUME_LISTS.SNP)
RESUMES /FILE=DISK9:[CORPORATE.PERSONNEL]RESUMES.RDA -
/SNAPSHOT=(FILE=DISK10:[CORPORATE.PERSONNEL]RESUMES.SNP)
Example 4
The following RMU Move_Area command moves the database root for
the mf_personnel database and defines a new after-image journal
configuration, using the Aij_Options qualifier:
$ RMU/MOVE_AREA/ROOT=DISK1:[DATABASE.PERSONNEL]MF_PERSONNEL -
_$ /AIJ_OPTIONS=aij_config.opt MF_PERSONNEL/NOONLINE
The aij_config.opt file contains the following clauses:
JOURNAL IS ENABLED -
RESERVE 2 -
ALLOCATION IS 512 -
EXTENT IS 512 -
OVERWRITE IS DISABLED -
SHUTDOWN_TIMEOUT IS 120 -
NOTIFY IS DISABLED -
BACKUPS ARE MANUAL -
CACHE IS DISABLED
ADD AIJ1 -
FILE DISK2:[MFPERS_AIJ1]AIJ_ONE
ADD AIJ2 -
FILE DISK3:[MFPERS_AIJ2]AIJ_TWO
Example 5
The following example moves all the mf_personnel database storage
areas to the DISK3:[db] directory:
$ RMU/MOVE_AREA MF_PERSONNEL.RDB /ALL_AREAS/DIR=DISK3:[DB]
Example 6
The following example demonstrates the use of the Directory,
File, and Root qualifiers. In this example:
o The default directory is specified as DISK2:[DIR].
o The target directory and file name for the database root file
is specified with the Root qualifier. The target directory
specified with the Root qualifier overrides the default
directory specified with the Directory qualifier. Thus, Oracle
RMU moves the database root to DISK3:[ROOT] and names it
MOVEDRDB.RDB.
o The target directory for the EMPIDS_MID storage area is
DISK4:[FILE]. Oracle RMU moves EMPIDS_MID to DISK4:[FILE].
o The target file name for the EMPIDS_LOW storage area is
EMPIDS. Thus, Oracle RMU moves the EMPIDS_LOW storage area
to the DISK2 default directory (specified with the Directory
qualifier), and names the file EMPIDS.RDA.
o The target for the EMPIDS_LOW snapshot file is
DISK5:[SNAP]EMPIDS.SNP Thus, Oracle RMU moves the EMPIDS_LOW
snapshot file to DISK5:[SNAP]EMPIDS.SNP.
o All the other storage area files and snapshot files in the
mf_personnel database are moved to DISK2:[DIR]; the file names
for these storage areas remain unchanged.
$ RMU/MOVE_AREA DISK1:[DB]MF_PERSONNEL.RDB /ALL-
_$ /DIRECTORY=DISK2:[DIR] -
_$ /ROOT=DISK3:[ROOT]MOVEDRDB.RDB -
_$ EMPIDS_MID/FILE=DISK4:[FILE], -
_$ EMPIDS_LOW/FILE=EMPIDS -
_$ /SNAPSHOT=(FILE=DISK5:[SNAP]EMPIDS.SNP)