ORA-006004193 Solution

Recently, an error occurred in the Oracle database data file of a customer, resulting in a failure to start. After recovery, the data file status is normal and the database seems to be open. (Note that the status is normal.

Recently, an error occurred in the Oracle database data file of a customer, resulting in a failure to start. After recovery, the data file status is normal and the database seems to be open. (Note that the status is normal.

Recently, an error occurred in the Oracle database data file of a customer, resulting in a failure to start.
After recovery, the data file status is normal and the database seems to be open.
(Note that the database status is normal. This does not mean that the database is completely normal, because data files, tables, and indexes may be damaged during the restoration process .)

After the database is started, an error of ORA-00600 4193 is reported, causing the database to not open.
By the way, I have expressed great contempt for the database version or 9i system unit. This organization is also an important national machine. It is reasonable to say that there should be a healthy solution to hand over the database O & M of a system to others. As a result, there is no backup, no backup, and 9i small junk version. QNMD: It's not surprising that you are not dead. In addition, 9i is used by all its predecessors. I used to work as 9i in a large financial enterprise in a developed country, which is costly to maintain, so a chinese population has also upgraded to 10 Gb, And that rigid nation can do it. Why don't we do it? However, this has also created an early group of DBA experts (in terms of database maintenance and troubleshooting ). 9i bug is like a flood of rivers and rivers. Especially for memory and data block-level errors, it's just a fuck. Nima fragment processing has something to do, and DB Conscience gets away.

Tucao N for a long time, to get back to the original, ora-00600 4193 is a common error, reprinted on the Internet countless. Summarize the following three methods:
1. When the database is enabled, the undotbs is re-assigned to the new undotbs.
2. If it is not enabled, modify the undo_management parameter to manual or (also mentioned) to provide a new rollback segment.

Continue to vomit, and there is only one sentence: Repost, please be responsible, you will never know if you do not experiment, right.

For me, the above method is used. The database is still not opened, and the 4193 is continued.
Finally, a variety of methods were used to connect the undo_management parameter to auto, and more than 10 rollback segments were added (the name of the rollback segment should be changed once the error occurs, what can be the Continuous Error Effect of data blocks found in the test ?), The database finally got up. But very fuck is, no matter what the operation (including countless people say the reconstruction of undotbs, for your sister AH), tell you ora-00600 4193. In other words, the database is useless, but it is not the same as it is.

I continue to talk about it. The technical articles in China are quite good, but when I encounter some biased problems, I am really spam. I don't know how to install it, and I don't want to say much about it. Search for Google and Yahoo Japan, and get attacked again ~ Tianchao technicians are really hard-pressed.
I read several non-mainstream technical articles and said it is good. That is to say, there is a data block error on the undo. Although no solution is provided, it may be an error on the undotbs, so I used the last trick, modified the undo_management parameter to manual, and deleted all rollback segments on the undo.
Drop rollback segmet "_ SYSSMU1 $"
Note that you must add "". Note that it must be the offline status of the rollback segment. Otherwise, the consequences may be unimaginable. Of course, it may not be deleted, haha.

At this time, the database will prompt you: Roll, delete Nima, do not let Delete. Hum, that's because the security level is not enough. Modify the spfile parameter and change that level to 4. (I forgot the specific parameter, which is easy to query)

Final result, database: restart db, ora-600 4193 error disappears. Me: I was killed.
After-care: for the sake of insurance, re-designate the undotbs; exp/imp database.