ERROR:
  Format: ORA-600 [4137]
 
VERSIONS:
  versions 7.0 to 10.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

SUGGESTIONS:

  Signalled during rollback (also rollback for consistent read).

  The consistency check that compares the transaction id of the
  transaction being rolled back against the transaction id in 
  undo block being applied is failing.

  A possible cause is a lost write to the undo segment.

  The main approach is to identify the file containing the bad undo
  segment block and treat it as if the file is corrupt. Consult
  the trace file for this information. 

  If in archivelog mode, restore the file & roll forward.

  If in Noarchivelog mode, restore from a cold backup taken before 
  the error was reported.
 
  Alternatively, you can look at dba_rollback_segs data dictionary view.
  If the status column that describes what state the rollback segment is 
  currently in is "needs recovery" then lookup the following article 
  for posible solution.

    Note:28812.1  Rollback Segment Needs Recovery

  If the Known Issues section below does not help in terms of identifying
  a solution, please submit the trace files and alert.log to Oracle
  Support Services for further analysis.