This content has been marked as final.
Show 16 replies
-
1. Re: RMAn Active Database Cloning
Fran Dec 21, 2012 9:22 AM (in response to 941744)
check if this file really exists and have enough privileges to be accesed. Probably this file is not backed up by Rman at source database and not needed for recovery in target database. It's only used for speed up the backup (incremental backup?).ORA-19750: change tracking file: '/sourcedb/db/11.2.0/dbs/rman_block_tracking.f'
a workaround will be :
sql > alter database disable block change tracking ;
rman > run { ....
...
...
} -
2. Re: RMAn Active Database Cloning
941744 Dec 21, 2012 10:23 AM (in response to Fran)I agree that BCT file is used to speed up the process, But i m not restoring from Backup, I m doing Active Databse restoration to another node; why its using Block Change tracking file!!!! as its ot needed in this case.. -
3. Re: RMAn Active Database Cloning
Richard Harrison . Dec 21, 2012 10:23 AM (in response to 941744)Hi,
No idea why this would be needed as to active duplicate it has to read the whole database and not just 'changed' blocks. Is the error that it is trying to create this file on the copy rather than read it on the souce? Does th path exist on the copy?
Regards,
Harry -
4. Re: RMAn Active Database Cloning
941744 Dec 21, 2012 10:24 AM (in response to Fran)and yes the file exists on source.. -
5. Re: RMAn Active Database Cloning
941744 Dec 21, 2012 10:25 AM (in response to Richard Harrison .)Yes this patch exists and permission are also on place.. -
6. Re: RMAn Active Database Cloning
Richard Harrison . Dec 21, 2012 10:39 AM (in response to 941744)Hmm - possiblt a bug i think.
Are you able to disable bct on the source as Fran suggested and try again?
Cheers,
Harry -
7. Re: RMAn Active Database Cloning
Osama_Mustafa Dec 21, 2012 11:19 AM (in response to 941744)error number. It may contain additional support notes as
described in Note:22080.1 }
Error: ORA-19750 (ORA-19750)
Text: change tracking file: '%s'
---------------------------------------------------------------------------
Cause:This message reports the name of a file involved in other messages.
Action:See associated error messages for a description of the problem.
Refer to
Rman Duplicate fail ORA-19755, Tries Open The Block Change Tracking File of Source DB [ID 1098638.1] -
8. Re: RMAn Active Database Cloning
Fran Dec 21, 2012 11:36 AM (in response to 941744)
RMAN uses the change tracking file to identify changed blocks for incremental backup, clone, duplicate,.... databasewhy its using Block Change tracking file!!!!
-
9. Re: RMAn Active Database Cloning
941744 Dec 21, 2012 5:58 PM (in response to Fran)Fran
BCT is used in case i have used rman backups to restore but i m restoring using Active Database, then why its using BCT?? -
10. Re: RMAn Active Database Cloning
941744 Dec 21, 2012 6:02 PM (in response to Osama_Mustafa)Hi Mustafa
I went through 1098638.1 already, but it explain for RMAN Restore from BAckup's not suing Active Database...
M confused why BCT used for Active Database cloning as its has no deal with it.. -
11. Re: RMAn Active Database Cloning
941744 Dec 23, 2012 11:28 AM (in response to 941744)Any updates?? -
12. Re: RMAn Active Database Cloning
Pinela Dec 24, 2012 8:52 AM (in response to 941744)well,
(and this is just an idea)
since you have BCT on, maybe it will use to keep track of the changed blocks during the network transfer process, to prevent the network transfer of ALL the generated archivelogs during the network transfer.
This way, the duplicate takes less time, because the recover process takes less time.
Just a possibility.
br and merry christmas,
jpinela. -
13. Re: RMAn Active Database Cloning
941744 Dec 24, 2012 7:13 PM (in response to 941744)Aman/Mustafa, Please suggest!!!! -
14. Re: RMAn Active Database Cloning
Osama_Mustafa Dec 25, 2012 2:24 AM (in response to 941744)I am sorry for the delay in response .
Please note that the error appears because This file is not backed up by RMAN and not needed for recovery so as workaround you have to do the following disable block_change_tracking and restart the recovery .
thensql > alter database disable block change tracking ;
Refer torun { SET UNTIL TIME “TO_DATE (’<Your-Time>′, ‘DD-MM-YY HH24:MI:SS’)”; allocate channel ch1 type <Channel>; recover database; release channel ch1 ; }
RMAN Recovery Error