Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
Windows Server 2012
Hi all,
I am getting the following error/trace ORA-00600 when dequeueing a scheduler event with DBMS_AQ.DEQUEUE
The dequeue works and the procedure that calls it completes without error.
Trace file D:\APP\ORACLE\diag\rdbms\xe\xe\trace\xe_q003_6212.trc
Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
Windows NT Version V6.2
CPU : 2 - type 8664, 2 Physical Cores
Process Affinity : 0x0x0000000000000000
Memory (Avail/Total): Ph:1471M/4095M, Ph+PgF:1958M/4607M
Instance name: xe
Redo thread mounted by this instance: 1
Oracle process number: 38
Windows thread id: 6212, image: ORACLE.EXE (Q003)
*** 2016-02-24 12:45:43.218
*** SESSION ID:(15.7) 2016-02-24 12:45:43.218
*** CLIENT ID:() 2016-02-24 12:45:43.218
*** SERVICE NAME:(SYS$BACKGROUND) 2016-02-24 12:45:43.218
*** MODULE NAME:(Streams) 2016-02-24 12:45:43.218
*** ACTION NAME:(QMON Slave) 2016-02-24 12:45:43.218
Symbol file D:\app\oracle\product\11.2.0\server\BIN\ORACLE.SYM does not match binary.
Symbol TimeStamp=5386049b, Module TimeStamp=53882d4a are different
Incident 2705 created, dump file: D:\APP\ORACLE\diag\rdbms\xe\xe\incident\incdir_2705\xe_q003_6212_i2705.trc
ORA-00600: internal error code, arguments: [kwqitnmphe:ltbagi], [1], [0], [], [], [], [], [], [], [], [], []
kwqitmmit during kwqitmmit:time mgr IOT proc: Error 600 in Queue Table SYS.SCHEDULER$_EVENT_QTAB
kwqicaclcur: Error 600
Cursor Session Number : 9
Cursor Session Serial : 47625
Cursor Pin Number : 28681
kwqitmmit during kwqitmmit:end proc: Error 600 in Queue Table SYS.SCHEDULER$_EVENT_QTAB
kwqitptm: error 600 encountered during serving 12455
*** 2016-02-24 12:45:43.842
ORA-00600: internal error code, arguments: [kwqitnmphe:ltbagi], [1], [0], [], [], [], [], [], [], [], [], []
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-00600: internal error code, arguments: [kwqitnmphe:ltbagi], [1], [0], [], [], [], [], [], [], [], [], []
it looks like a bug. Has anyone seen this? Any ideas?
many thanks
Garry Lawton