ORA-00600 12700 Solution

Oracle 9i is really a headache, ORA-00600 has become a signboard error, although 10g also has similar errors, but it is already very different from 9i.
At the beginning of DBA, on the ORA-00600 began to understand, when learning that this is "oracle bug, kernel error" and other information, has given up to solve. At that time, fortunately, I just returned to the DB Group to work offshore and had nothing to do. By the way, I provided technical support to other colleagues in the Department, such as pure friendship support and informal work delegation. So sometimes encounter a ORA-600, directly tell them to reinstall it, haha. The first is laziness, and the second is failure to solve the problem. They thought that the turtle DBA was very NB, and at first I did solve a few problems, so they came to me for everything, but this is not the case. Brother knows, at that time, brother was just an entry level.
 
There is no way to deal with it. In the face of a variety of production machines and customers, if you don't solve it, you just need to break your own job. Stick it to your scalp.
This is the ORA-00600, the reason is very simple: generally because of the table or index data block error, usually caused by "select XX from tblXX.
Let's talk about 9i again. Is it okay if the data block is correct...
 
By collecting various information on the Internet, we have summarized the solution. I still want to tell you that the online methods are not necessarily and not necessarily correct. They are all transferred in and out. First, there may be missing steps, and second, they may not be suitable for your system, so the application is risky, be cautious when solving the problem. In the end, you have to think about the best solution by yourself.
The solution is as follows:
First of all, this is the method to cure the problem.
1. Through the error information ORA-00600 [12700] [11350] [712367812], you can get the error obj_id and block_id.
2. Find the error object through obj_id, table/index/table partition, and so on.
3. It should be okay to rebuild the index directly. If you want to rebuild the table, you can rename it to bak first. Then re-create the table and pay attention to the index name. Finally, insert into table select * from table_bak. Of course, you can also use exp/imp to recreate a table, but the wrong data block cannot be exported during exp.
Problem: one of the risks of doing so is that not only this object may have bad blocks, so there is a potential risk. In addition, the data on Bad blocks will not be inserted into the new table, data is lost, and the index name changes. So I thought whether the data block level can be repaired? No answer yet. I am very grateful to have a chance to tell you.
 
Note: To be safe, check whether all user tables are incorrect.
Table check
Select 'analyze table afis40. '| object_name | 'validate structure;' from dba_objects where wner = 'afis40' and object_type = 'table ';
Check all the table information and associate Indexes
Select 'analyze table afis40. '| object_name | 'validate structure cascade;' from dba_objects where wner = 'afis40' and object_type = 'table ';
Check data files
Dbv file = 'xxx. dbf'blocksize = 8192
However, it is unclear how to locate and fix the data file error information.