1. After the database is recovered abnormally, the database will prompt an error

Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_5239.trc  (incident=121363):
ORA-00600: internal error code, arguments: [ktecgsc:kcbz_objdchk], [0], [0], [1], [], [], [], [], [], [], [], []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

2. Find problems by checking trace files

The following log files are used to judge whether it is data_ OBJECT_ There is a problem with this object with id = 104126

*** SESSION ID:(32.9) 2021-09-25 09:15:01.750
OBJD MISMATCH typ=16, seg.obj=-2, diskobj=104128, dsflg=0, dsobj=104126, tid=104126, cls=4
Incident 120379 created, dump file: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_120379/orcl_ora_3092_i120379.trc
ORA-00600: internal error code, arguments: [ktecgsc:kcbz_objdchk], [0], [0], [1], [], [], [], [], [], [], [], []

3. Check data_ OBJECT_ Id = 104126 this object

It is found that the object no longer exists in the database, but it can be queried. It is found that this table was created by yourself, not a system table. After deletion, it returns to normal

SQL> select object_name,object_type,owner from dba_objects where DATA_OBJECT_ID=104126;
OBJECT_NAME          OBJECT_TYPE         OWNER
-------------------- ------------------- ------------------------------
XINJU_HEADROOM_SCN   TABLE               SYS

SQL> select * from XINJU_HEADROOM_SCN;
select * from XINJU_HEADROOM_SCN
              *
ERROR at line 1:
ORA-08103: object no longer exists