RMAN Active Duplication Fais When Specifying LOGFILE Instance Clause RMAN-06136
(Doc ID 2418809.1)
Last updated on MARCH 06, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
Symptoms
RMAN active duplication failing when specifying LOGFILE INSTANCE clause in RAC
RMAN-06136: ORACLE error from auxiliary database: ORA-01967: invalid option for CREATE CONTROLFILE
run {
allocate auxiliary channel 'dev_0' device type disk;
set newname for database to '+FRA';
duplicate target database to '<New_Db>'
UNTIL TIME "TO_DATE('06-06-2014 15:20:00', 'DD-MM-YYYY HH24:mi:ss')"
DB_FILE_NAME_CONVERT ('+DATA','+DATA')
LOGFILE INSTANCE '<Instance_Name>' GROUP 1 ('+DATA','+FRA') SIZE 10M,
INSTANCE '<Instance_Name>' GROUP 2 ('+DATA','+FRA') SIZE 10M,
INSTANCE '<Instance_Name>' GROUP 3 ('+DATA','+FRA') SIZE 10M,
INSTANCE '<Instance_Name> GROUP 4 ('+DATA','+FRA') SIZE 10M ;
release channel 'dev_0';
}
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |