RMAN Duplicate For Standby Fails With RMAN-00600: Internal Error, Arguments [7530]
(Doc ID 2332108.1)
Last updated on APRIL 03, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
RMAN> duplicate target database for standby
2> dorecover;
.....
channel ORA_AUX_DISK_4: restore complete, elapsed time: 00:00:46
Finished restore at 24-NOV-17
contents of Memory Script:
{
switch clone datafile all;
}
executing Memory Script
Recovery catalog is down or not connected to catalog, trying to reconnect.
Reconnection with the recovery catalog is successful.
datafile 1 switched to datafile copy
....
input datafile copy RECID=55 STAMP=960891651 file name=/<PATH>/datafile/<FILE_NAME>.dbf
datafile 22 switched to datafile copy
input datafile copy RECID=56 STAMP=960891652 file name=/<PATH>/datafile/<FILE_NAME>.dbf
contents of Memory Script:
{
set until scn 2553953590209;
recover
standby
clone database
delete archivelog
;
}
executing Memory Script
executing command: SET until clause
Starting recover at 24-NOV-17
using channel ORA_AUX_DISK_1
....
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/24/2017 10:20:56
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-00600: internal error, arguments [7530] [] [] [] []
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |