Supplemental Logging for OLTP-compressed table may corrupt UNDO block.
The Corrupt UNDO block results in the inability of tables from being read for transaction abort/recovery or consistent-read.
SMON may crash the database as it is unable to rollback the transaction associated to the corrupt UNDO segment.
This problem only occurs when Supplemental Logging is enabled for OLTP-compressed table.
Supplemental Logging is normally enabled when using Logical Standby Database, Golden Gate or Oracle Streams.
In RDBMS version 11.1 Supplemental Logging on COMPRESS tables is not supported so one of the workarounds described in the section below has to be used.
This restriction is lifted in 11.2g. However, the same problem is caused in 11.2g by bug 8331063.
Symptoms of the Problem
ORA-600  in Oracle foreground process or SMON background process in the presence of supplemental logging for COMPRESS tables.
This error is raised on undo application code paths and would show functions like ktundo on the stack.
If db_block_checking is enabled, the next errors can be produced with check code 2007 preventing the corruption going to disk:
ORA-600 [kdBlkCheckError] [file#] [block#] 
ORA-600 [kddummy_blkchk] [file#] [block#] 
and the trace file contains:
Block Checking: DBA = rdba, Block Type = Undo data block
ERROR: Undo Block Corrupted. Error Code = 2007
ktu4ubck: undo record #n with n change vectors exceeds allowed 293
Supplemental Logging can be enabled at database or table level.
Supplemental Logging at database level (any column value different than "NO" means that it is enabled):
select supplemental_log_data_min, supplemental_log_data_pk,supplemental_log_data_ui from v$database;Supplemental Logging at table level for a COMPRESS table:
select t.owner, t.table_name from dba_log_groups g, dba_tables t where g.owner = t.owner and g.table_name = t.table_name and t.compression = 'ENABLED';
Solution of the Problem
If you are using 11.2g then install patch 8331063.
However if you are in 11.1 and in 11.2g you can follow following workarounds.
1) Set _lmn_compression=FALSE to disable supplemental logging on compress tables.
2) Disable Supplemental Logging.
3) Disable COMPRESSION by using,
'alter table ... MOVE NOCOMPRESS'. Don't use 'alter table ... NOCOMPRESS' statement.
Note that this statement does not repair existent corruptions but it will prevent them from future happenings.