Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

ORA-10567: Redo is inconsistent with data block (file# 2, block# 73)

102430Apr 5 2006 — edited Feb 28 2012

SQL> spool c:\stdb.txt
SQL> startup nomount PFILE='E:\oracle\admin\fno\pfile\init.ora';
ORACLE instance started.

Total System Global Area 730931140 bytes
Fixed Size 454596 bytes
Variable Size 285212672 bytes
Database Buffers 444596224 bytes
Redo Buffers 667648 bytes
SQL> ALTER DATABASE MOUNT STANDBY DATABASE;

Database altered.

SQL> RECOVER STANDBY DATABASE;
ORA-00279: change 7990686470 generated at 04/01/2006 15:53:57 needed for threa 1

ORA-00289: suggestion : F:\ORACLE\ORADATA\FNO\ARCH\LOG_17032.ARC
ORA-00280: change 7990686470 for thread 1 is in sequence #7032

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3020], [8388681], [1],

[7032],
[137367], [16], [], []
ORA-10567: Redo is inconsistent with data block (file# 2, block# 73)
ORA-10564: tablespace UNDOTBS1
ORA-01110: data file 2: 'G:\ORACLE\ORADATA\FNO\UNDOTBS01.DBF'
ORA-10560: block type 'KTU SMU HEADER BLOCK'

ORA-01112: media recovery not started

Please help if anybody nows solution for this.

Regds,
Ramesh
e-mail to : rameshgiri27@yahoo.com
Mobile NO: +91 080 9341018616

512897

Hi Ramesh,

I reckon you should try these out:
- identify the tablespace that file belongs to in the production db.
- put the that tablespace in backup mode on the prod db
- shutdown your standby database
- overwrite the problematic datafile with the corresponding datafile from production database
- put the tablespace above in end backup mode
- startup your standby database and issue the recover command.

Well, there you go. Your standby database should be all fine now.

Regards
Pranilesh Chand

Kenneth Ugwu

I encountered similar problem and the solution below worked for me.

Thanks a million times.

754513

it worked for me too
thanks a lot.

ELLAIA ADIL

85972

how will it work? just curious to know.

85972

BTW, it worked for us too, still not sure why/how it worked?

Saugat Chatterjee

Well actually it works like this

when you copy the problamatic datafile onto the standby server then it gets synchronised upto the point at which you enable backup for the datafile,and the activities which are done on the prod db after you enable backup for the datafile gets synchronised using the archives generated at the time of enabling and disabling the backup for the problamatic tablespace.

Saugat Chatterjee
OCP 11g

1 - 6

Locked Post

New comments cannot be posted to this locked post.

Locked on Mar 27 2012

Added on Apr 5 2006

#database-key-features, #replication

6 comments

20,621 views

Database Software

ORA-10567: Redo is inconsistent with data block (file# 2, block# 73)

Comments

Post Details