|
|
|
An exerpt from the trace file:
ORA-00600: internal error code, arguments: [4000], [9], [], [], [], [], [], [] Current SQL statement for this session: select ctime, mtime, stime from obj$ where obj# = :1 ... Block header dump: 0x0080003e Object id on Block? Y seg/obj: 0x12 csc: 0x570.b8368d16 itc: 1 flg: - typ: 1 - DATA fsl: 0 fnx: 0x0 ver: 0x01 ... Itl Xid Uba Flag Lck Scn/Fsc 0x01 xid: 0x0009.019.000dc23f uba: 0x58c13ddb.0523.46 --U- 1 fsc 0x0000.b8368d17 Looks like a problem regarding obj$ and its undo...If undo requirement is bypassed, there will be no requirement for undo. In order to do that, bumping SNC further needed. csc shows the the SCN of last block cleanout. We guessed it may be used a target bumping SCN as below:
Bump SCN as below and restart:
ORA-600 [4000] disappeared. But now, the following error appeared:
Oracle Note:47456.1: DESCRIPTION: While backing out an undo record (i.e. at the time of rollback) we found a transaction id mis-match indicating either a corruption in the rollback segment or corruption in an object which the rollback segment is trying to apply undo records on. This would indicate a corrupted rollback segment. FUNCTIONALITY: Kernel Transaction Undo Recovery IMPACT: POSSIBLE PHYSICAL CORRUPTION in Rollback segments Restart the database:
The database is opened. Since it's opened in inconsistent state, a full export and then import into a new database is required to get rid of the inconsistency in Oracle dictionary. But, the customer data will not be consistent after the import. It should be reviewed by the customer. The database was opened inconsistently. It'll be recreated with full export/import.
|
<--cancel
But, it failed with the following error:
Oracle Note:47456.1: