oracle database file corrupted! [message #63662] |
Tue, 26 October 2004 02:17 |
Soham
Messages: 29 Registered: June 2004 Location: Mumbai
|
Junior Member |
|
|
while starting oracle database i am getting following error.
<database_file_name.ora> is corrupted. this file cannot be varified.
What is corruption of database files? what might be the possible reasons? how to recover from the corruptted database files?(can it be recover from the cold back-up )
please help,
thanx in advance,
Regards,
soham
|
|
|
Re: oracle database file corrupted! [message #63664 is a reply to message #63662] |
Tue, 26 October 2004 06:27 |
dilip kumar
Messages: 111 Registered: December 2003
|
Senior Member |
|
|
Hi
you have not properly posted your error messages it seems send it once again and tell me whether your database is running in archive log mode or noarchivelog mode because that plays a major role in recover process
Regards
D.Dilip
|
|
|
|
Re: oracle database file corrupted! [message #63677 is a reply to message #63668] |
Wed, 27 October 2004 05:57 |
croK
Messages: 170 Registered: April 2002
|
Senior Member |
|
|
Try to find out what file is #32, because if it is datafile that contains rollback segments, you can drop that and recreate it.
If it is datafile that contains indexes, you can also drop it and rebuild indexes.
If it is system tablespace, you should restore good cold backup from tape. But your database will be as it was on 20/10/2004, all transactions since that day up to date will be lost because you are not running on archivelog mode.
If datafile #32 is some data tablespace, you can also check what table is corrupted, and try to export that table, drop it, and recreate it into another tablespace.
If it is a user table, you can use dbms_repair as follows:
DBMS_REPAIR.SKIP_CORRUPT_BLOCKS('<schema>','
');
then you can export table with no problem. Of course, be sure you can recreate table exactly as it was before dropping it (indexes, constraints, etc..)
Best luck.
|
|
|
Re: oracle database file corrupted! [message #63730 is a reply to message #63677] |
Tue, 02 November 2004 09:57 |
Soham
Messages: 29 Registered: June 2004 Location: Mumbai
|
Junior Member |
|
|
Thanks Crok!
We found out tht it is a data tablespace and also which table is corrupted.
We tried to recreate it into another tablespace but it is introducing the bad blocks in tht tablespace also
[[bad blocks are spreading on the insert statement]]
so I think it might be the problem of the disk controller.
we r trying to recover the database from cold bkup on some other machine.
thanks for your help,
regards,
soham
|
|
|