ORA-00600[4097]错误的一些案例如下：
该ORA-00600[4097]错误从Oracle 7.3版本中被引入，遇到该错误一般说明Oracle在访问一个回滚段头rollback segment header时检查其事务是否已经被提交，但发现其相关的XID存在问题。这一般是因为回滚段存在损坏/讹误导致的。该错误属于内核Rollback回滚层。 其可能导致数据库无法打开或持续的报错，甚至于数据丢失。
ORA-00600[4097]错误的相关BUG如下：
13340388 11.2.0.3.3, 11.2.0.3.BP07, 12.1.0.0 ORA-600 [kzaxpopr14 -Error in decoding xml text] when querying V$XML_AUDIT_TRAIL 10249791 11.2.0.2.BP02,on DMLS referencing SECUREFILE plugged 11.2.0.2.7, 11.2.0.3, 12.1.0.0 11.1.0.7.4, 11.2.0.1.2, 11.2.0.2, 12.1.0.0 11.1.0.7.2, 11.2.0.1.1, 11.2.0.2, 12.1.0.0 7687856 11.2.0.1 5653641 11.2.0.1 ORA-600 [4097] / ORA-600 [4000] reported using transportable tablespaces * 9145541 OERI[25027]/OERI[4097]/OERI[4000]/ORA- 1555 in plugged datafile after CREATE CONTROLFILE in 11g OERI[4097] after using distributed 8565708 11.2.0.1.BP04,transactions in RAC 3613078 2628232 9.2.0.6, ORA-600 [4000] from DML on transported ASSM tablespace Corrupt dictionary from DROP TABLESPACE containing _offline_rollback_segments OERI[4097] from DML on TRANSPORTED tables with ASSM Block corruption possible on temp files ORA-600's from CR served block from a plugged in tablespace OERI:4097 possible on objects in read only transported tablespace Tru64: OERI:4097 possible on RAC / OPS Drop of Rollback segments can cause OERI:4097 / missing data 10.1.0.3 3249755 9.2.0.5, 10.1.0.2 9.2.0.4, 10.1.0.2 8.1.7.4, 2165601 9.0.1.3, 9.2.0.1 P 1885251 * 427389 '*' against a bug indicates that an alert exists for that issue. '+' indicates a particularly notable bug. 'P' indicates a port specific bug. '@' indicates UNPUBLISHED information Fixed versions use "BPnn" to indicate Exadata bundle nn. "OERI:xxxx" may be used as shorthand for ORA-600 [xxxx]. 9015PSE, 9.2.0.1 7.3.3.3, 7.3.4.0, 8.0.3.0
该问题可以通过patch或者重建rollback segment来起到修复的作用，如果该问题导致你的数据库无法打开了，可以联系诗檀软件Oracle Support帮忙解决。
Comment