| data file block corrupted!!! [message #54293] |
Fri, 08 November 2002 13:59  |
fengq
Messages: 38
Registered: October 2002
|
Member |
|
|
hi, I got the error in the alertlog file as following:
Please help!!!!!!!!!!!!!!
Fri Nov 08 13:59:18 2002
ARC0: Beginning to archive log# 2 seq# 5474
ARC0: Completed archiving log# 2 seq# 5474
***
Corrupt block relative dba: 0x03003f53 (file 12, block 16211)
Fractured block found during buffer read
Data in bad block -
type: 6 format: 2 rdba: 0x03003f53
last change scn: 0x0001.26426c31 seq: 0x1 flg: 0x00
consistency value in tail: 0x685c0601
check value in block header: 0x0, block checksum disabled
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Reread of rdba: 0x03003f53 (file 12, block 16211) found same corrupted data
Fri Nov 08 14:00:24 2002
Errors in file E:oracleadminRDWPRDbdumprdwprdSNPW.TRC:
ORA-12012: error on auto execute of job 1
ORA-01578: ORACLE data block corrupted (file # 12, block # 16211)
ORA-01110: data file 12: 'E:ORACLEORADATARDWPRDLANDSCAPE.ORA'
ORA-06512: at "SYS.DBMS_DDL", line 179
ORA-06512: at "SYS.DBMS_UTILITY", line 331
ORA-06512: at "BAZZ.RUN_COMPUTE_STATS", line 12
ORA-06512: at line 1
|
|
|
|
|
|
| Re: data file block corrupted!!! [message #54317 is a reply to message #54293] |
Mon, 11 November 2002 06:58  |
XXXXXXXXXXXXXX
Messages: 1
Registered: November 2002
|
Junior Member |
|
|
The procedure to recover from the loss of general datafiles depends on the type
of tablespace from which the datafile is lost; for example, rollback tablespace,
user tablespace, index tablespace, or read-only tablespace. You might get the
following errors:
You're trying to start up the database and get error message ORA-1157, ORA-1110,
and possibly an operating system error.
You're trying to shut down the database in normal or immediate mode and get
error message ORA-1116, ORA-1110, and possibly an operating system error.
The following steps can be used to recover:
Shut down the database.
Restore the lost datafile from the hot backup.
Startup mount the database.
Execute the following query to determine all your online redo log files and
their respective sequence and first change numbers:
SELECT X.GROUP#, MEMBER, SEQUENCE#, FIRST_CHANGE#
FROM V$LOG X, V$LOGFILE Y
WHERE X.GROUP# = Y.GROUP#;
If the CHANGE# obtained is less than the minimum FIRST_CHANGE# of your online
redo logs, the file can't be completely recovered and you have two choices:
If you can afford to lose the database changes since the most recent cold
backup, restore the backup and continue with the recovery.
If you can't afford to lose the database changes, you'll have to re-create the
tablespace. Recover the datafile by using the archived and the online redo logs.
Open the database.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
