RMAN Duplicate issues
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: RMAN Duplicate issues

  1. #1
    Join Date
    Feb 2001

    RMAN Duplicate issues

    We're testing RMAN (9i) on our environment, and the actual tests are on RMAN duplicate feature. I chose the following scenario for the test:

    - One database running on machine A; that is a development DB;
    - One database running OEM repository + RMAN catalog on machine B;

    I need to create on machine B a copy of the dev DB. I have backups of that database (taken with RMAN and registered on the recovery catalog). According to documentation and some Metalink notes, I followed the steps:

    1. Created a password file and a W2K service;
    2. Created a PFILE. Parameters like CONTROL_FILES and DB_FILE_NAME_CONVERT were set there to reflect differences on directory structure;
    3. Configured Oracle Net on both machines to access the auxiliary database;
    4. STARTUP NOMOUNT on auxiliary database;
    5. Connected on RMAN (target + catalog + auxiliary). So, I ran the following:

    run {
    allocate auxiliary channel aux1 device type disk;
    duplicate target database to AUXDB;

    As far as I noticed, directory conversions went fine. However, the following error was shown during the restore of datafiles:

    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 12/23/2003 14:06:17
    RMAN-03015: error occurred in stored script Memory Script
    ORA-19505: failed to identify file "F:\ORADATA\DEVDB\BAK\B_13F9LT48_1_1"
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.

    Drive F is on machine A, it doesn't exist on machine B. However, I mapped the network drive through NET USE, so machine B can read the directory as if it was a local drive (I tested it).

    Is there any misunderstanding of mine? Any clarifications?
    An ounce of action is worth a ton of theory.
    —Friedrich Engels

  2. #2
    Join Date
    Nov 2000
    Sounds like the user on b can't see a's mounted filesystem.
    Jeff Hunter
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  3. #3
    Join Date
    Feb 2001

    RMAN> exit

    Recovery Manager complete.

    H:\>dir F:\ORADATA\DEVDB\BAK\B_13F9LT48_1_1
    Volume in drive F is Data
    Volume Serial Number is C601-5D2D

    Directory of F:\ORADATA\DEVDB\BAK

    12/23/2003 12:04a 1,040,162,816 B_13F9LT48_1_1
    1 File(s) 1,040,162,816 bytes
    0 Dir(s) 152,932,433,920 bytes free

    H:\>net use
    New connections will be remembered.

    Status Local Remote Network

    OK F: \\machineA\f$ Microsoft Windows Network
    OK H: \\machineD\USERS\Backup Microsoft Windows Network
    The command completed successfully.

    Anything wrong with that?
    An ounce of action is worth a ton of theory.
    —Friedrich Engels

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Click Here to Expand Forum to Full Width