Simply record a ORA-00600: internal error code, arguments: [2662]

Next, REDO error after the OPEN Database and the error ORA-00600: internal error code, arguments: [2662].

The reason is _ allow_resetlogs_uption after resetlogs open the database, we may encounter ORA-00600 2662 error due to inconsistent SCN, here is a complete example and solution process.

Symptom and solution-please refer to EYGLE for this picture.

Sun Dec 11 18:02:25 2005 Errors in file/opt/oracle/admin/conner/udump/conner_ora_13349.trc:ORA-00600: internal error code, arguments: [2662], [0], [547743994], [0], [898092653], [8388617], [], []Sun Dec 11 18:02:27 2005
At this point, we can adjust the SCN through Oracle internal events:
There are two common methods to improve SCN:
1. Use the immediate trace name method (in the database Open state)
Alter session set events 'immediate trace name ADJUST_SCN level x ';
2. Pass the 10015 event (unable to open the database, mount the status)
Alter session set events '10015 trace name adjust_scn level x ';
Note: level 1 is used to increase SCN 1 billion (1 billion) (1024*1024*1024). Generally, Level 1 is sufficient. It can also be adjusted according to the actual situation.

Reference http://www.eygle.com/archives/2005/12/oracle_diagnostics_howto_deal_2662_error.html