Bug 29552402 - ORA-600: [kdblkcheckerror] error code [14508] if temp_undo_enabled = true on Transactions that Generates Large Amount of Undo (Doc ID 29552402.8)

Bug 29552402  ORA-600: [kdblkcheckerror] error code [14508] if temp_undo_enabled = true on Transactions that Generates Large Amount of Undo

Affects:

Product (Component)	Oracle Server (Rdbms)
Range of versions believed to be affected	(Not specified)
Versions confirmed as being affected	12.2.0.1 (Base Release) 12.1.0.2 (Server Patch Set) 12.1.0.1 (Base Release)
Platforms affected	Generic (all / most platforms affected)

Fixed:

The fix for 29552402 is first included in

20.1.0 19.9.0.0.DBRU:201020 (OCT 2020) DB Release Update Revision(DB RU)

Interim patches may be available for earlier versions - click here to check.

Description

When temp_undo_enabled mode is on, a long transaction hits ORA-00600:  [kdblkcheckerror] error code [14508] with an temp undo segment header
 corruption.
 
Trace file :
Block Checking: DBA = 189824, Block Type = Unlimited undo segment header
 
*** 2019-02-21T14:04:54.099089-05:00
ERROR: Undo Segment Header Corrupted.  Error Code = 14508
ktu4shck: starting extent(0xffff816e) of txn slot #0x11 is  invalid.
 valid value (0 - 0x816e)
 
The fix introduces the following error instead of the internal error code : 
 
    ORA-55522: failed to extend temporary undo segment number N
    ORA-01628: max # extents (32765) reached for rollback segment $TEMPUNDOSEG
 
The ORA-1628 error is reported in the alert log file, unless _log_space_errors parameter is false.
 
    ORA-1628: max # extents (32765) reached for rollback segment $TEMPUNDOSEG
 
Workaround
 
Disable temp_undo_enabled
 
- or -
 
Reduce the amount of UNDO records generated by the transaction.
 

References

Bug:29552402 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article