VMS Help  —  RMU72  Restore  Examples (Cont.)
    Example 18

    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, the
       RMU restore process restores the database root in DISK3:[ROOT]
       and names it COPYRDB.RDB.

    o  The target directory for the EMPIDS_MID storage area is
       DISK4:[FILE]. The RMU restore process restores EMPIDS_MID
       in DISK4:[FILE].

    o  The target file name for the EMPIDS_LOW storage area is
       EMPIDS. Thus, the RMU restore process restores the EMPIDS_LOW
       storage area to the DISK2:[DIR] 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, the RMU restore process restores
       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 restored in DISK2:[DIR]; the file names
       for these storage areas and snapshot files remain unchanged.

    $ RMU/RESTORE MF_PERSONNEL.RBF -
    _$ /DIRECTORY=DISK2:[DIR] -
    _$ /ROOT=DISK3:[ROOT]MF_PERSONNEL.RDB -
    _$ EMPIDS_MID/FILE=DISK4:[FILE], -
    _$ EMPIDS_LOW/FILE=EMPIDS -
    _$ /SNAPSHOT=(FILE=DISK5:[SNAP]EMPIDS.SNP)

    Example 19

    The following example demonstrates how to restore a database
    such that the newly restored database will allow read-only
    transactions only. After the RMU restore process executes the
    command, the database is ready for you to start Hot Standby
    replication operations. See the Oracle Rdb7 and Oracle CODASYL
    DBMS: Guide to Hot Standby Databases for details on starting Hot
    Standby replication operations.

    $RMU/RESTORE/TRANSACTION_MODE=READ_ONLY MF_PERSONNEL.RBF

    Example 20

    The following example uses the Nocommit qualifier while restoring
    a backup file of a database that has a structure level of V7.1 in
    a V7.2 environment.

    $ RMU/SHOW VERSION
    Executing RMU for Oracle Rdb V7.2-00
    $ RMU/RESTORE MFP71.RBF /NOCOMMIT/NOCDD/NORECOVER
    %RMU-I-AIJRSTAVL, 0 after-image journals available for use
    %RMU-I-AIJISOFF, after-image journaling has been disabled
    %RMU-I-LOGCONVRT, database root converted to current structure level
    %RMU-S-CVTDBSUC, database USER1:[80]MF_PERSONNEL.RDB;1 successfully
    converted from version V7.1 to V7.2
    %RMU-W-USERECCOM, Use the RMU Recover command. The journals are not
    available.
    $ RMU/SHOW VERSION
    Executing RMU for Oracle Rdb V7.2-00
    $ RMU/CONVERT/ROLLBACK MF_PERSONNEL.RDB
    %RMU-I-RMUTXT_000, Executing RMU for Oracle Rdb V7.2-00
    Are you satisfied with your backup of RDBVMS_USER1:[V71]MF_PERSONNEL.RDB;1
    and your backup of any associated .aij files [N]? Y
    %RMU-I-LOGCONVRT, database root converted to current structure level
    %RMU-I-CVTROLSUC, CONVERT rolled-back for RDBVMS_USER1:[V71]MF_PERSONNEL.
    RDB;1 to version V7.1

    Example 21

    The following example uses the Close_Wait qualifier to set the
    database close mode to TIMED AUTOMATIC, specifying that the
    database will be closed automatically in 10 minutes.

    $ RMU/RESTORE/OPEN_MODE=AUTOMATIC/CLOSE_WAIT=10/DIR=DISK:[DIR] TEST_DB.RBF
    $ RMU/DUMP/HEADER=PARAMETERS TEST_DB.RDB

    Example 22

    The following example demonstrates that /SNAPSHOT=(ALLOCATION=N)
    is a positional qualifier. The behavior is different (local
    or global) depending on the placement of the qualifier on the
    command line. In the following example, it is used both globally
    and locally.

    MALIBU-> RMU/RESTORE/NOCDD -
             /DIR=SYS$DISK:[]/SNAP=ALLO=12345 [JONES.RDB]MF_PERSONNEL_V71.RDF -
             DEPARTMENTS/SNAP=ALLO=2
    MALIBU-> DIR/SIZE *.SNP

    Directory DBMS_USER3:[JONES.WORK]

    DEPARTMENTS.SNP;1          6
    EMPIDS_LOW.SNP;1       24692
    EMPIDS_MID.SNP;1       24692
    EMPIDS_OVER.SNP;1      24692
    EMP_INFO.SNP;1         24692
    JOBS.SNP;1             24692
    MF_PERS_DEFAULT.SNP;1
                           24692
    MF_PERS_SEGSTR.SNP;1
                           24692
    SALARY_HISTORY.SNP;1
                           24692

    Total of 9 files, 197542 blocks.

    Example 23

    The following example demonstrates how /SNAPSHOT=(ALLOCATION=N)
    can be used to alter the parameters of the restored database from
    those defined at the time of the database backup. /SNAPSHOT is
    ofter used with /FILE: /FILE for the storage area RDA file and
    /SNAPSHOT for the storage area snapshot file.

    $ RMU/RESTORE MFP.RBF -
      /DIRECTORY=DISK1:[DIRECTORY] -
      /ROOT=DISK2:[DIRECTORY]MF_PERSONNEL.RDB -
     EMPIDS_MID /FILE=[DISK3:[DIRECTORY]  /SNAPSHOT=(ALLOCATION=2000),  -
     EMPIDS_LOW /FILE=[DISK3:[DIRECTORY]NEWNAME  -
          /SNAPSHOT=(FILE=DISK4:[DIR]NEWNAME, ALLOCATION=3000)

    In this example, the root would go to one disk, EMPIDS_MID
    would go to another, EMPIDS_LOW to another disk and the snap
    to another disk and both snaps would be allocated the specified
    number of pages. All the other snaps and RDA files would go to
    where /DIRECTORY points (and the snaps would keep their original
    allocation).
Close Help