My Oracle Support Banner

Physical Standby Database Reported Corrupted Datafiles in Temporary Tablespace (Doc ID 1290412.1)

Last updated on FEBRUARY 13, 2019

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.


=== ODM Issue Clarification ===

While opening physical standby database in read only mode, alert.log file reports:

Tue Jan 25 15:25:08 2011
Tue Jan 25 15:25:08 2011
Hex dump of (file 501, block 1) in trace file \<oracle_home>\<db_name>\bdump\<db_name>_dbw0_4936.trc
Corrupt block relative dba: 0x00400001 (file 501, block 1)
Bad header found during data file header read
Data in bad block:
type: 11 format: 2 rdba: 0x02000001
last change scn: 0x0000.00000000 seq: 0x1 flg: 0x04
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x00000b01
check value in block header: 0x62b1
computed block checksum: 0x0
Reread of rdba: 0x00400001 (file 501, block 1) found same corrupted data
Tue Jan 25 15:25:08 2011
Errors in file \<oracle_home>\<db_name>\bdump\<db_name>_dbw0_4936.trc:
ORA-01186: file 501 failed verification tests
ORA-01122: database file 501 failed verification check
ORA-01110: data file 501: '\<oracle_home>\<db_name>\<datafile>.DBF'
ORA-01210: data file header is media corrupt




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.