ORACLE data block corrupted; RMAN won't initalize

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Article Type: General
Product: Aleph
Product Version: 18.01

Description:
We have an issue with a corrupt data block in our Aleph 18 database:

ORA-00604: error occurred at recursive SQL level 2
ORA-01578: ORACLE data block corrupted (file # 1, block # 2061)
ORA-01110: data file 1: '/exlibris/oradata/aleph1/aleph1_system01.dbf'
ORA-00604: error occurred at recursive SQL level 2
ORA-01578: ORACLE data block corrupted (file # 1, block # 2061)
ORA-01110: data file 1: '/exlibris/oradata/aleph1/aleph1_system01.dbf'

Along with this, I am unable to connect to RMAN to perform a database restore:

ORACLE10>> rman target = aleph1
Recovery Manager: Release 10.2.0.3.0 - Production on Mon Nov 30 11:05:43 2009

target database Password:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-00604: error occurred at recursive SQL level %s

This occurred as a result of our server room overheating.

Resolution:
You should follow this procedure:

1. Take the server down

2. Take any attached storage devices down.

3. Bring up and run filesystem checks on attached and local storage devices.

4. Bring the server up.

The result of this will be that the system is less likely to corrupt any further application data due to filesystem corruption, possibly circumventing further problems recovering the system to an operational state.

If you perform only steps 1 and 4, then it could *seem* that the corruption has been corrected, but an underlying problem with the storage device could still be present.

Article last edited: 10/8/2013