Found below error message in alert log while switch over in DR site.
ORA-00756: recovery detected a lost write of a data block
ORA-10567: Redo is inconsistent with data block (file# 60, block# 871712, file offset is 2846097408 bytes)
ORA-10564: tablespace APPS_UNDOTS1
ORA-01110: data file 60: '/d4/oraprod/PROD/apps_st/data/undo_ts1b.dbf'
ORA-10560: block type 'KTU UNDO BLOCK'
Lost writes are caused by factors external to Oracle RDBMS. This normally happens when the operating system does not raised any errors while trying to write a blcok on disk, but still the write didn't get into the persistent storage.
So since there is no error, for Oracle, this is a complete write because the system call didn't produce any errors.
And then later, when reading the block, Oracle may realize by comparing the block with a different block that the block is not current.
As the affected datafile is part of UNDO tablespace you should replace the datafiles on STANDBY using the steps from Note 453153.1 - Recovering the primary database's datafile using the physical standby, and vice versa
ORA-00756: recovery detected a lost write of a data block
ORA-10567: Redo is inconsistent with data block (file# 60, block# 871712, file offset is 2846097408 bytes)
ORA-10564: tablespace APPS_UNDOTS1
ORA-01110: data file 60: '/d4/oraprod/PROD/apps_st/data/undo_ts1b.dbf'
ORA-10560: block type 'KTU UNDO BLOCK'
Lost writes are caused by factors external to Oracle RDBMS. This normally happens when the operating system does not raised any errors while trying to write a blcok on disk, but still the write didn't get into the persistent storage.
So since there is no error, for Oracle, this is a complete write because the system call didn't produce any errors.
And then later, when reading the block, Oracle may realize by comparing the block with a different block that the block is not current.
As the affected datafile is part of UNDO tablespace you should replace the datafiles on STANDBY using the steps from Note 453153.1 - Recovering the primary database's datafile using the physical standby, and vice versa
Solution:
Please set below parameter on both primary and standby database . Please refer document 1265884.1 & 1302539.1 for more details and parameter impact on the database .
DB_LOST_WRITE_PROTECT =TYPICAL
DB_BLOCK_CHECKING=FULL
No comments:
Post a Comment
Note: only a member of this blog may post a comment.