Oracle ORA 221 Error
Recently I had found an ORA-0021 on one of my customers. The problem was arised when a SCSI controller failed resulting in a I/O error writing one of the control files.
The problem is serious, because the database stops and is not able to start again, but don't panic, the solution is so easy.
Controlfiles are readed during the instance start. You can see the error, as ORA 221 or ORA-00221 in the alert log leaving the database unmounted.
To solve the problem, stop the instance and then, looking the alert log and locating the entry about the 221 error, look for the controlfile corrupted. Then, rename the corrupted file (I have learned in all my years as system administrator that you should not delete never a file, rename it and delete it a few weeks before when you are sure you'll not need any more), and finally copy one of the other controlfiles to the name of the first one.
Now, if you restart the database all should be fine.
The problem is serious, because the database stops and is not able to start again, but don't panic, the solution is so easy.
Controlfiles are readed during the instance start. You can see the error, as ORA 221 or ORA-00221 in the alert log leaving the database unmounted.
To solve the problem, stop the instance and then, looking the alert log and locating the entry about the 221 error, look for the controlfile corrupted. Then, rename the corrupted file (I have learned in all my years as system administrator that you should not delete never a file, rename it and delete it a few weeks before when you are sure you'll not need any more), and finally copy one of the other controlfiles to the name of the first one.
Now, if you restart the database all should be fine.
posted by Josep Llauradó i Selvas at 12:05 AM
0 Comments:
Post a Comment
<< Home