Oracle Database Error: ORA-00600: internal error code, arguments: [qosdExpStatRead: expcnt mismatch], [65562], [26], [1144616], [1], [], [], [], [], [], [], []

SQL> exec DBMS_STATS.FLUSH_DATABASE_MONITORING_INFO;
BEGIN DBMS_STATS.FLUSH_DATABASE_MONITORING_INFO; END;

*
ERROR at line 1:
ORA-00600: internal error code, arguments: [qosdExpStatRead: expcnt mismatch],
[65562], [26], [1144616], [1], [], [], [], [], [], [], []
ORA-06512: at “SYS.DBMS_STATS”, line 2141
ORA-06512: at “SYS.DBMS_STATS”, line 43486
ORA-06512: at line 1

DDE: Problem Key ‘ORA 600 [qosdExpStatRead: expcnt mismatch]’ was flood controlled (0x4) (incident: 2017148)
ORA-00600: internal error code, arguments: [qosdExpStatRead: expcnt mismatch], [65562], [26], [1144616], [1], [], [], [], [], [], [], []
2025-07-29T11:33:58.617971+03:00
Incident 2017643 created, dump file: /oraclex/oradbp25/diag/rdbms/oradbp25/oradbp25/incident/incdir_2017643/oradbp25_dw00_3988067_i2017643.trc
ORA-00600: internal error code, arguments: [qosdExpStatRead: expcnt mismatch], [65562], [26], [1144616], [1], [], [], [], [], [], [], []
ORA-06512: at “SYS.DBMS_STATS”, line 2141
ORA-06512: at “SYS.DBMS_STATS”, line 57633
ORA-06512: at “SYS.DBMS_STATS”, line 57866
ORA-06512: at “SYS.KUPW$WORKER”, line 30029
ORA-06512: at “SYS.KUPW$WORKER”, line 3503
ORA-06512: at “SYS.KUPW$WORKER”, line 13746
ORA-06512: at “SYS.KUPW$WORKER”, line 2439
ORA-06512: at line 2

SOLUTION/FIX:

SQL> alter system set “_fix_control”=’31143146:on’,’32005394:on’ scope=both;

of course, its highly recommended to open a case with ORACLE.

ORA-00600: internal error code, arguments: [qerixAddNotNullStopKeyPredicate:1] in the alert log !

one of the databases i am supporting ( on version 12cR1 12.1.0.2) was throwing ORA-600 in the alert log:

Archived Log entry 94742 added for thread 1 sequence 48014 ID 0x6a20c315 dest 2:
Errors in file /oracle/orcl12/diag/rdbms/orcl12/orcl12/trace/orcl12_j003_115141.trc (incident=582200):
ORA-00600: internal error code, arguments: [qerixAddNotNullStopKeyPredicate:1], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /oraclex/orcl12/diag/rdbms/orcl12/orcl12/incident/incdir_582200/orcl12_j003_115141_i582200.trc
Non critical error ORA-48913 caught while writing to trace file “/oraclex/orcl12/diag/rdbms/orcl12/orcl12/incident/incdir_582200/orcl12_j003_115141_i582200.trc”
Error message: ORA-48913: Writing into trace file failed, file size limit [5242880] reached

Solution:

if this error is infrequent then you can ignore, otherwise as a workaround is to disable the Automatic SQL Tuning Tasks by executing the following:

BEGIN
DBMS_AUTO_TASK_ADMIN.DISABLE(
client_name => ‘sql tuning advisor’,
operation => NULL,
window_name => NULL );
END;
/

As a consequence, this will disable all automatic SQL tuning tasks but you can still perform “on-demand” SQL tuning to get advice on tuning specific SQL statements.