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:
Code:
Quote:
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?
