Skip to Main Content

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Saurabh.

Asked: September 03, 2016 - 6:55 pm UTC

Last updated: June 26, 2024 - 2:36 am UTC

Version: 11.2.0.4

Viewed 10K+ times! This question is

You Asked

Hi,

I am trying to restore target database with below command :

rman auxiliary /

run {
allocate auxiliary channel ch1 type disk;
allocate auxiliary channel ch2 type disk;
allocate auxiliary channel ch3 type disk;
allocate auxiliary channel ch4 type disk;
allocate auxiliary channel ch5 type disk;
allocate auxiliary channel ch6 type disk;
allocate auxiliary channel ch7 type disk;
allocate auxiliary channel ch8 type disk;
duplicate target database to EFGH
BACKUP LOCATION '/bkup/ABCD'
UNTIL TIME "TO_DATE('2016-07-21 10:30:10', 'YYYY-MM-DD HH24:MI:SS')";
release channel ch1;
release channel ch2;
release channel ch3;
release channel ch4;
release channel ch5;
release channel ch6;
release channel ch7;
release channel ch8;
}
exit


Command is failing is with below error :

contents of Memory Script:
{
sql clone "alter system set db_name =
''EFGH'' comment=
''Reset to original value by RMAN'' scope=spfile";
sql clone "alter system reset db_unique_name scope=spfile";
shutdown clone immediate;
}
executing Memory Script

Errors in memory script
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01507: database not mounted
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 13658
ORA-06512: at line 1
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-19563: header validation failed for file
ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 3939
ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 3882
ORA-06512: at line 1
RMAN-05001: auxiliary file name +RECO_MP/ABCD/blcktrfile1.log conflicts with a file used by the target database
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 08/21/2016 00:12:12
RMAN-05501: aborting duplication of target database

This seems to be failing as BCT appears to be enabled as per log, how can I control block change tracking at target side using duplicate command as I am simply opening the database in nomount mode, rest everything else is taking care off by duplicate command.


Regards,
Saurabh

and Connor said...

This is a known issue. I've copied the MOS note below

=======================
Rman Duplicate fail ORA-19755, Tries Open The Block Change Tracking File of Source DB (Doc ID 1098638.1) To BottomTo Bottom

In this Document
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 15-Apr-2014***
SYMPTOMS

When trying to do an rman duplicate with the source database using block change tracking file receiving
errors:


RMAN-03002: failure of Duplicate Db command at 05/11/2010 18:22:47
RMAN-03015: error occurred in stored script Memory Script
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/rman/I3VPROD1/archivelog/2010_05_11/o1_mf_1_40265_5ym0xdlc_.arc'
ORA-00283: recovery session canceled due to errors
ORA-19755: could not open change tracking file
ORA-19750: change tracking file: '/rman/bct/blockchanges.log'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3



CAUSE

Unpublished Bug 7500916 RMAN DUPLICATE DOESN'T PRESERVE DATABASE LEVEL SUPPLEMENTAL LOGGING DIRECTIVES
Bug 10185641 RMAN'S DB_FILE_NAME_CONVERT OF DUPLICATE NOT APPLIED TO CHANGE TRACKING FILE
Bug 10193846 RMAN DUPLICATE FAILS WITH ORA-19755 WHEN BCT FILE OF PRIMARY IS NOT ACCESSIBLE

Unpublished Bug 11744544 Set newname for database does not apply to block change tracking file
fixed in 12.1
Description: Block change tracking recreation might fail if ot duplicating to OMF newnames
or db_file_name_convert can not be applied to it.



Bug 18371441 : RMAN DUPLICATE FAILS TO CREATE BCT FILE

SOLUTION


You are encountering one of several bugs. The best option is to apply the fix for unpublished Bug: 11744544 Set newname for database does not apply to block change tracking file

Unpublished Bug 11744544 Set newname for database does not apply to block change tracking file. fixed in 12.1
Description: Block change tracking recreation might fail if ot duplicating to OMF newnames
or db_file_name_convert can not be applied to it.

There are patches available for this bug for several platforms. With the patch, you can use new syntax:

SET NEWNAME FOR BLOCK CHANGE TRACKING FILE TO '...filename...';

to explicitly set the location of the block change tracking file

For example:

run
{
SET NEWNAME FOR BLOCK CHANGE TRACKING FILE TO '/oracle/oradata/TEST/block_change.bct';
...
duplicate database to TEST..;

}

OR

run
{
SET NEWNAME FOR BLOCK CHANGE TRACKING FILE TO '+DATA';
...
duplicate database to TEST..;

}





Unpublished Bug 7500916

This is fixed in the oracle patchset 11.2.0.2 as part of Bug 7500916.
The workaround is to disable change tracking before duplicate.

Bug 10185641

Workaround is to set DB_FILE_NAME_CONVERT in the SET-clause of duplicate, instead of using DB_FILE_NAME_CONVERT setting in an init.ora or spfile.
Example :
RMAN> duplicate database v112 to duplv112
backup location '/u01/oradata/v112/reco_area/V112/backupset/2010_10_09'
spfile parameter_value_convert ('v112', 'duplv112')
set db_file_name_convert = 'v112', 'duplv112'
noresume;
This bug is fixed in Product Version 12.1


Bug 10193846

Workaround is to create a dummy file in the location where the error ORA-19755 is signalled.
A workaround for all of the bugs would be to disable block change tracking on the target database before
duplicating.

In the case of using an UNTIL clause, disabling of BCT will not work unless the selected UNTIL time or SCN is AFTER the time of disabling block change tracking.

Bug 10193846 - RMAN duplicate fails with ORA-19755 when BCT file is not accessible (Doc ID 10193846.8)
This issue is fixed in:
12.1.0.1 (Base Release)
11.2.0.3 (Server Patch Set)
11.2.0.2.3 Database Patch Set Update
11.2.0.2 Bundle Patch 7 for Exadata Database
11.2.0.1 Bundle Patch 12 for Exadata Database
11.2.0.2 Patch 6 on Windows Platforms


(MAY-2014) Related open issue Bug 18371441 - RMAN DUPLICATE FAILS TO CREATE BCT FILE
============================

Rating

  (2 ratings)

Is this answer out of date? If it is, please let us know via a Comment

Comments

Thanks much

Saurabh Shukla, September 05, 2016 - 8:44 am UTC

Just one question, how the BCT can be disabled at target side in duplicate run block?
Connor McDonald
September 06, 2016 - 2:17 am UTC

What they say "target" in effect it is the *source* database they are referring to (in the same way we do)

connect target u/p
connect auxiliary i/p

and the duplicate from the "target" (ie the *source*) to the aux.

But that does seem a drastic option to me (because presumably it would mean your *next* target backup would have to rescan all the files to re-establish the block change tracking file)

Error When restore Database

Youheng Chhieng, June 26, 2024 - 2:27 am UTC

Errors in memory script
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: Oracle error from auxiliary database: ORA-01507: database not mounted
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 16172
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 16126
ORA-06512: at line 1
RMAN-03015: error occurred in stored script Memory Script
RMAN-10035: exception raised in RPC:
ORA-19583: conversation terminated due to error
ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 3336
ORA-19870: error while restoring backup piece /dba_backup/backup/FCPRI/Full_FCPRI_22062024_19268_1_1172284624
ORA-00600: internal error code, arguments: [krbebad_1], [0], [0], [], [], [], [], [], [], [], [], []
ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 3333
RMAN-10031: RPC Error: ORA-19583 occurred during call to DBMS_BACKUP_RESTORE.RESTOREBACKUPPIECE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/26/2024 09:11:06
RMAN-05501: aborting duplication of target database

Connor McDonald
June 26, 2024 - 2:36 am UTC

Any time you get an ORA-600, its time to call Support.

eg

Bug 35914103 ORA-19599 / ORA-600 [krbebad_1] during RMAN restore
Bug 32966688 OSBWS: Restore from cloud fails with ORA-600 [krbebad_1]
more

Connor and Chris don't just spend all day on AskTOM. You can also catch regular content via Connor's blog and Chris's blog. Or if video is more your thing, check out Connor's latest video and Chris's latest video from their Youtube channels. And of course, keep up to date with AskTOM via the official twitter account.

More to Explore

Backup/Recovery

Check out the complete guide to all of the Backup & Recovery techniques in the Oracle Database.