Oracle ORA-600 [4097] ORA-00600 [4097] “Corruption”

Some historic info….

Upgrade/install a patchset to bring the database to one of the following levels : 7.3.3.3, 7.3.4.0, 8.0.3.0
To avoid encountering this bug, rollback segments should only be dropped and recreatedaftertheinstancehasbeenshutdownnormalandrestarted. Ifyou have already encountered the bug, use the following workaround:
Possible workaround:
– Drop all rollback segments, except for SYSTEM
– Create the same number of rollback segments, small ones, with different names – recreate the original rollback segments
– drop the small dummy rollback segments
Every time you need to add a rollback segment, first create all of the dummy segments again, to make sure they use up the old segment numbers. Then create the new segment, then drop all dummy segments.
If you are getting this error not because of the above bug — see Description to see how you could run into the bug — then you might have a rollback segmentcorruptionissue. Typicalcausesaremediacorruptiontothe rollbacksegmentblocks,checkyourhardware. Toworkaroundarollback segment corruption problem (not because of known bug above) log the
issue with Oracle support.

ORA-600 [4097]
Versions:7.1.3 -7.3.2

Source:ktu.c

===========================================================================

Meaning:

We are accessing a rollback segment header to see if a transaction has beencommitted. However,thexidgivenisinthefutureofthe transaction table. Ie: the WRAP of the XID is higher than
the current WRAP number on the RBS header.

————————————————————————— Argument Description:

No arguments.

————————————————————————— Diagnosis:

This should be considered as a corruption.

1. Try to identify which object has this TX in its ITL list. (see the trace file)