RMAN error when running Synchronise Standby Database.
Problem Details
Problem Statement
RMAN error when running Synchronise Standby Database.
Applicable Error Code
RMAN-03002 and ORA-01403
Affected Versions
All Standby Version / Database Version 11.2.0.1
Affected Platforms
Noticed in Unix Platforms
The primary database Oracle version 11.2.0.1 is ASM, the standby is non ASM, no ASM instance running on the standby server.
When synchronizing standby database, Dbvisit fails at restoring the standby control file with:
20131217 17:26:42 main::cmn_cat-> RMAN-00571: =========================================================== 20131217 17:26:42 main::cmn_cat-> RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== 20131217 17:26:42 main::cmn_cat-> RMAN-00571: =========================================================== 20131217 17:26:42 main::cmn_cat-> RMAN-03002: failure of switch command at 12/17/2013 17:26:42 20131217 17:26:42 main::cmn_cat-> ORA-03113: end-of-file on communication channel 20131217 17:26:42 main::cmn_cat-> ORA-01403: no data found 20131217 17:26:42 main::cmn_cat-> ORA-01403: no data found
Trace file reveals the error occurred when renaming a temp file in the standby control file using RMAN:
RMAN>run {
>set newname for tempfile 1 to NEW;
>switch tempfile 1;
}
An error in the standby alert log:
ERROR: slave communication error with ASM; terminating process 661
The same error may occur when restoring datafiles, and when running Create Standby Database.
The problem is caused by an Oracle bug that was fixed in 11.2.0.2. Upgrade or apply Patch 9530594.
Anna MacNaughtan December 18, 2013 17:46
Comments