| Symptoms |
|---|
| Cause |
|---|
| Solution |
|---|
| References |
|---|
Applies to:
Oracle Database – Enterprise Edition – Version 11.2.0.1 and later
Information in this document applies to any platform.
* Checked for relevance on 27-NOV-2015 *
Symptoms
Running Rman Active Duplicate to Create Standby from RAC Primary.
Scan Listener is used to connect to the RAC 2 Node as Target.
RMAN Duplicate failing with:
RMAN> connect target *
2> connect auxiliary *
3> RUN {
4> ALLOCATE CHANNEL d01 TYPE DISK PARMS="BLKSIZE=1048576";
5> ALLOCATE CHANNEL d02 TYPE DISK PARMS="BLKSIZE=1048576";
6> ALLOCATE CHANNEL d03 TYPE DISK PARMS="BLKSIZE=1048576";
7> ALLOCATE CHANNEL d04 TYPE DISK PARMS="BLKSIZE=1048576";
8> ALLOCATE CHANNEL d05 TYPE DISK PARMS="BLKSIZE=1048576";
9> ALLOCATE CHANNEL d06 TYPE DISK PARMS="BLKSIZE=1048576";
10> ALLOCATE CHANNEL d07 TYPE DISK PARMS="BLKSIZE=1048576";
11> ALLOCATE CHANNEL d08 TYPE DISK PARMS="BLKSIZE=1048576";
12> ALLOCATE AUXILIARY CHANNEL cnv01 TYPE DISK PARMS="BLKSIZE=8388608";
13> ALLOCATE AUXILIARY CHANNEL cnv02 TYPE DISK PARMS="BLKSIZE=8388608";
14> ALLOCATE AUXILIARY CHANNEL cnv03 TYPE DISK PARMS="BLKSIZE=8388608";
15> ALLOCATE AUXILIARY CHANNEL cnv04 TYPE DISK PARMS="BLKSIZE=8388608";
16> ALLOCATE AUXILIARY CHANNEL cnv05 TYPE DISK PARMS="BLKSIZE=8388608";
17> ALLOCATE AUXILIARY CHANNEL cnv06 TYPE DISK PARMS="BLKSIZE=8388608";
18> ALLOCATE AUXILIARY CHANNEL cnv07 TYPE DISK PARMS="BLKSIZE=8388608";
19> ALLOCATE AUXILIARY CHANNEL cnv08 TYPE DISK PARMS="BLKSIZE=8388608";
20> DUPLICATE TARGET DATABASE
21> FOR STANDBY
22> FROM ACTIVE DATABASE
23> DORECOVER
24> SPFILE
25> SET db_unique_name='SAMER'
26> SET control_files='+SAMER_REDO01/TEST_SAMER_01.ctl','+SAMER_REDO02/TEST_SAMER_02.ctl'
27> SET log_archive_dest_1='LOCATION=+SAMER_ARCH01 VALID_FOR=(ALL_LOGFILES,ALL_ROLES)'
28> SET log_archive_dest_2='SERVICE=TEST LGWR AFFIRM ASYNC NET_TIMEOUT=30 COMPRESSION=ENABLE DB_UNIQUE_NAME=TEST VALID_FOR=(ONLINE_LOGFILE,PRIMARY_ROLE)'
29> SET fal_server='TEST'
30> SET db_file_name_convert='+TEST_DATA','+SAMER_DATA01'
31> SET log_file_name_convert='+TEST_REDO1','+SAMER_REDO01','+TEST_REDO2','+SAMER_REDO02'
32> SET standby_file_management='AUTO'
33> SET log_archive_config='dg_config=(TEST,SAMER)'
34> SET parallel_execution_message_size="65536"
35> SET db_recovery_file_dest='+SAMER_ARCH01'
36> SET db_recovery_file_dest_size="536870912000"
37> SET DB_CREATE_ONLINE_LOG_DEST_1='+SAMER_REDO01'
38> SET DB_CREATE_ONLINE_LOG_DEST_2='+SAMER_REDO02'
39> SET DB_CREATE_FILE_DEST='+SAMER_DATA01'
40> SET diagnostic_dest='/u02/app/oracle/diag'
41> NOFILENAMECHECK;
42> }
43> ..
.
.
.
contents of Memory Script:
{
backup as copy reuse
targetfile '/u01/app/oracle/product/11.2.0/db_1/dbs/orapwTEST1' auxiliary format
'/u02/app/oracle/product/11.2.0/dbs/orapwTEST1' targetfile
'+TEST_DATA/TEST/spfileTEST.ora' auxiliary format
'/u02/app/oracle/product/11.2.0/dbs/spfileTEST1.ora' ;
sql clone "alter system set spfile= ''/u02/app/oracle/product/11.2.0/dbs/spfileTEST1.ora''";
}
executing Memory Script
Starting backup at 05-MAY-13
RMAN-03009: failure of backup command on d01 channel at 05/05/2013 04:54:54
ORA-19505: failed to identify file "/u01/app/oracle/product/11.2.0/db_1/dbs/orapwTEST1"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
continuing other job steps, job failed will not be re-run
released channel: d01
released channel: d02
released channel: d03
released channel: d04
released channel: d05
released channel: d06
released channel: d07
released channel: d08
released channel: cnv01
released channel: cnv02
released channel: cnv03
released channel: cnv04
released channel: cnv05
released channel: cnv06
released channel: cnv07
released channel: cnv08
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/05/2013 04:54:54
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on d01 channel at 05/05/2013 04:54:54
ORA-19505: failed to identify file "/u01/app/oracle/product/11.2.0/db_1/dbs/orapwTEST1"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Cause
Scan Listener are used and RMAN is trying to copy the password file orapwTEST1 while connecting to node 2 which has orapwTEST2.
A SCAN listener is a dynamic listener so cannot be used for active duplicates.
Active duplicate can only use static listeners.
Dedicated Server connections are recommended for RMAN
Solution
Do not use SCAN Listener connects for RMAN
Active duplicate can only use static listeners.
Use "Dedicated" Server connections for RMAN
Prerequisites Specific to Active Database Duplication:
When you execute DUPLICATE with FROM ACTIVE DATABASE, at least one normal target channel and at least one AUXILIARY channel are required.
When you connect RMAN to the source database as TARGET, you must specify a password, even if RMAN uses operating system authentication. The source database must be mounted or open. If the source database is open, then archiving must be enabled. If the source database is not open, then it must have been shut down consistently.
When you connect RMAN to the auxiliary instance, you must provide a net service name. This requirement applies even if the auxiliary instance is on the local host.
The source database and auxiliary instances must use the same SYSDBA password, which means that both instances must have password files. You can create the password file with a single password so you can start the auxiliary instance and enable the source database to connect to it.
The DUPLICATE behavior for password files varies depending on whether your duplicate database acts as a standby database. If you create a duplicate database that is not a standby database, then RMAN does not copy the password file by default. You can specify the PASSWORD FILE option to indicate that RMAN should overwrite the existing password file on the auxiliary instance. If you create a standby database, then RMAN copies the password file to the standby host by default, overwriting the existing password file. In this case, the PASSWORD FILE clause is not necessary.
You cannot use the UNTIL clause when performing active database duplication. RMAN chooses a time based on when the online data files have been completely copied, so that the data files can be recovered to a consistent point in time.