Oracle DBA Tips and Techniques

By Arjun Raja

Block Change Tracking file error – ORA-19750 during RECOVERY.

Posted by Arjun Raja on January 18, 2011

While restoring and recovering the a database which uses the block change tracking file we faced a documented problem with the block_change_tracking file not being avaiblable.

This was the error during RECOVERY….

released channel: ch1
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of recover command at 02/18/2009 09:33:29 ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile
‘/u02/oradata/flash_recovery_area/XXXXXXX/archivelog/2009_02_18/o1_mf_1_117043_4spoq75y_.arc’ ORA-00283: recovery session canceled due to errors
ORA-19755: could not open change tracking file
ORA-19750: change tracking file:
‘/u02/oradata/xxxxxx/xxxxxx_blk_change.dbf’
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory Additional information: 3

This Block Change Tracking file is not backed up by RMAN and not needed for recovery – it is purely used by RMAN for speeding up the incremental backups.

Therefore to workaround this problem simply disable block_change_tracking and restart the recovery .

sql > alter database disable block change tracking ;

RMAN> run {
SET UNTIL TIME “TO_DATE (’09-02-09 18:00:00′, ‘DD-MM-YY HH24:MI:SS’)”; allocate channel ch1 type ‘sbt_tape’ parms ‘ENV=
(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)’; recover database;
release channel ch1 ;
}
executing command: SET until clause

allocated channel: ch1
channel ch1: sid=310 devtype=SBT_TAPE
channel ch1: Data Protection for Oracle: version 5.4.1.0

Starting recover at 18-FEB-09

starting media recovery

archive log thread 1 sequence 117043 is already on disk as
file /u02/oradata/flash_recovery_area/XXXXXXXX/archivelog/2009_02_18/o1_mf_1_117043_4spoq75y_.arc archive log thread 1 sequence 117044 is already on disk as
file /u02/oradata/flash_recovery_area/XXXXXXXXarchivelog/2009_02_18/o1_mf_1_117044_4spoq6n3_.arc archive log
filename=/u02/oradata/flash_recovery_area/XXXXXX/archivelog/2009_02_18/o1_mf_1_117043_4spoq75y_.arc thread=1 sequence=117043
archive log
filename=/u02/oradata/flash_recovery_area/XXXXX/archivelog/2009_02_18/o1_mf_1_117044_4spoq6n3_.arc thread=1 sequence=117044
archive log
filename=/u02/oradata/flash_recovery_area/XXXXX/archivelog/2009_02_18/o1_mf_1_117045_4spoq7ks_.arc thread=1 sequence=117045
channel ch1: starting archive log restore to default destination ==

Recovery continues.

Advertisements

One Response to “Block Change Tracking file error – ORA-19750 during RECOVERY.”

  1. Ann Kobetitsch said

    Arjun – Do you know how to get around this error on block change tracking file when running DUPLICATE? Only workaround I’ve found so far is to disable change tracking on the source database before backing up the conrolfile that will be used for the dup.
    Thanks!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: