Rman rac to single instance duplicate automatic allocation channel trigger ORA-19505 Error

Using RMAN duplicate to set up data guard from RAC to a single instance, results in duplicate, triggering ORA-19505 error, as shown below:

ORA-19505: failed to identify file "/u01/APP/Oracle/11.2.0/db_1/dbs/orapwdave1"

 

I checked the log, modified the number of channels, and duplicate again.

 

I. Error Reporting

RMAN> show all;

 

RMAN configuration parameters for databasewith db_unique_name Dave are:

Configure retention policy to redundancy 1; # default

Configure backup optimization off; # default

Configure Default device type to disk; # default

Configure controlfile autobackup off; # default

Configure controlfile autobackup format fordevice type disk to '% F'; # default

Configure device typedisk parallelism 4 backup type to backupset;

Configure datafile backup copies for devicetype disk to 1; # default

Configure archivelog backup copies fordevice type disk to 1; # default

Configure maxsetsize to unlimited; # default

Configure encryption for database off; # default

Configure encryption algorithm 'aes128 '; # default

Configure compression algorithm 'basic 'asof release 'default' optimize for load true; # default

Configure archivelog deletion policy tonone; # default

Configure snapshot controlfile name to '/u01/APP/Oracle/11.2.0/db_1/dbs/snapcf_dave1.f'; # default

 

 

 

RMAN> duplicate targetdatabase for standby from active database;

 

Starting duplicate dB at 03-jul-13

Using target database control file insteadof recovery catalog

Allocated channel: ora_aux_disk_1

Channel ora_aux_disk_1: SID = 19 devicetype = Disk

Allocated channel: ora_aux_disk_2

Channel ora_aux_disk_2: SID = 20 devicetype = Disk

Allocated channel: ora_aux_disk_3

Channel ora_aux_disk_3: SID = 21 devicetype = Disk

Allocated channel: ora_aux_disk_4

Channel ora_aux_disk_4: SID = 22 devicetype = Disk

 

Contents of memory script:

{

Backup as copy Reuse

Targetfile '/u01/APP/Oracle/11.2.0/db_1/dbs/orapwdave1' auxiliary format

'/U01/APP/Oracle/product/11.2.0/dbhome_1/dbs/orapwdave ';

}

Executing memory script

 

Starting backup at 03-jul-13

Allocated channel: ora_disk_1

Channel ora_disk_1: SID = 43 instance = dave2 device type = Disk

Allocated channel: ora_disk_2

Channel ora_disk_2: SID = 63 instance = dave1 device type = Disk

Allocated channel: ora_disk_3

Channel ora_disk_3: SID = 42 instance = dave2 device type = Disk

Allocated channel: ora_disk_4

Channel ora_disk_4: SID = 55 instance = dave1 device type = Disk

RMAN-00571: ========================================================== ==============================

RMAN-00569: ==================== error messagestack follows ======================

RMAN-00571: ========================================================== ==============================

RMAN-03002: failure of duplicate dB commandat 07/03/2013 01:44:01

RMAN-05501: Aborting duplication of targetdatabase

RMAN-03015: Error occurred in stored scriptmemory script

RMAN-03009: failure of Backup command onora_disk_1 channel at 07/03/2013 01:44:01

ORA-19505: Failed toidentify file "/u01/APP/Oracle/11.2.0/db_1/dbs/orapwdave1"

ORA-27037: unable toobtain File status

Linux-x86_64 error: 2: nosuch file or directory

Additional information: 3

 

The files here have been created before and exist on each node.

 

 

2. The channel is successfully modified.

 

RMAN> configuredevice type disk parallelism 2;

 

Old rman configuration parameters:

Configure device type disk parallelism 4 backup type to backupset;

New RMAN configuration parameters:

Configure device type disk parallelism 2 Backup Type to backupset;

New RMAN configuration parameters aresuccessfully stored

Released channel: ora_disk_1

Released channel: ora_disk_2

Released channel: ora_disk_3

Released channel: ora_disk_4

Released channel: ora_aux_disk_1

Released channel: ora_aux_disk_2

Released channel: ora_aux_disk_3

Released channel: ora_aux_disk_4

 

RMAN> duplicate targetdatabase for standby from active database;

 

Starting duplicate dB at 03-jul-13

Allocated channel: ora_aux_disk_1

Channel ora_aux_disk_1: SID = 19 devicetype = Disk

Allocated channel: ora_aux_disk_2

Channel ora_aux_disk_2: SID = 20 devicetype = Disk

 

Contents of memory script:

{

Backup as copy Reuse

Targetfile '/u01/APP/Oracle/11.2.0/db_1/dbs/orapwdave1' auxiliary format

'/U01/APP/Oracle/product/11.2.0/dbhome_1/dbs/orapwdave ';

}

Executing memory script

 

Starting backup at 03-jul-13

Allocated channel: ora_disk_1

Channel ora_disk_1: SID = 63 instance = dave1 device type = Disk

Allocated channel: ora_disk_2

Channel ora_disk_2: SID = 55 instance = dave1 device type = Disk

Finished backup at 03-jul-13

 

Contents of memory script:

{

Backup as copy current controlfile for standby auxiliary format '/u01/APP/Oracle/oradata/Dave/control01.ctl ';

Restore clone controlfile to '/u01/APP/Oracle/fast_recovery_area/Dave/control02.ctl' from

'/U01/APP/Oracle/oradata/Dave/control01.ctl ';

}

Executing memory script

 

 

 

The reason is based on the red mark. Here, I solve this problem by modifying the number of channels. Another solution is to create a password file for the other node on both nodes.

 

If you are interested, you can test it yourself.

 

 

 

 

 

 

 

 

 

Bytes --------------------------------------------------------------------------------------------

All rights reserved. reprinted articles are allowed, but source addresses must be indicated by links. Otherwise, the documents will be held legally responsible!

QQ: 251097186

Skype: tianlesoftware

Email: tianlesoftware@gmail.com

Blog: http://blog.csdn.net/tianlesoftware

WEAVER: http://weibo.com/tianlesoftware

Twitter: http://twitter.com/tianlesoftware

Facebook: http://www.facebook.com/tianlesoftware

LinkedIn: http://cn.linkedin.com/in/tianlesoftware