HELP - ORA-00600 internal error

From: John Blackburn <jb2_at_qdot.qld.gov.au>
Date: 24 Nov 1994 00:49:36 GMT
Message-ID: <3b0nv0$p6_at_camelot.qdot.qld.gov.au>


System: SPARC 10 running SunOS 4.1.3
Software:

        ORACLE RDBMS V6.0.36.7.1
        PL/SQL       V1.0.36.2.2
        SQL*Plus     V3.0.12.4.1

I have a SQL*Plus report that produces a summary of database integrity violations by means of unions. i.e. each select statement in the union does a count of the number of the particular integrity violation. Now when the report runs, the number of rows returned is equivelant to the value of arraysize after which the following error message is produced:

ERROR at lie 138:
ORA-00600: internal error code, arguments: [701], [2759616], [2759616], [1679840101], [8192], [1668573551]

With tracing turned on, the following messages appear in the trace file 22 times:

Tue Nov 22 10:29:12 1994
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [701], [2759616], [2759616], [1679840101], [8192], [1668573551] ----- Call Stack Trace -----

calling       entry         argument list...
location      point         arg values      
--------      -----         ----------      

_ksedmp+60 0xefffe370 0x5 0x35 0x21 0xefffe188 0x0
_kserip+200 _ksedmp 0x3 0x0 0x35 0x1 0x1 0x30
_ksesip+12 _kserip 0x2bd 0x5 0xefffe5e4 0xa 0x0 0x5
_ksesic+28 _ksesip 0x2bd 0x5 0xefffe5e4 0x40400080 0xf04a5fb4 0xf04a6000
_ksmcma+320 _ksesic 0x2bd 0x5 0x0 0x2a1bc0 0x0 0x2a1bc0
_opiomc+144 _ksmcma 0x270cd8 0x2a1bc0 0x0 0x6374696f 0x272240 0x29fbb8
_opivpa+744 _opiomc 0x1 0x1 0xff 0x1 0x270cd8 0x0
_opiodr+2788 _opivpa 0xeffff4d4 0x270cd8 0xeffff4d4 0x1 0x2 0x104a8
_ttcpip+3360 _opiodr 0x24f1a8 0x24f1a8 0x24f1a8 0x24f1a8 0x14 0x14
_opitsk+628 _ttcpip 0x24f1a4 0xefffeac0 0xeffff560 0x0 0x1 0xeffff4d4
_opiino+272 _opitsk 0x24f1a8 0x0 0x0 0xa 0x24f1a4 0x0
_opiodr+880 _opiino 0x3c 0x4 0xeffffae4 0x5 0x5 0x24f1a4
_opidrv+676 _opiodr 0xb4 0x78 0x11012 0x4a 0x0 0x0
_sou2o+24 _opidrv 0x0 0x4 0xeffffae4 0x0 0x1c 0x0
_main+136 _sou2o 0xeffffaf4 0x3c 0x4 0xeffffae4 0x3 0x0
start+68 _main 0x0 0xeffffc2f 0xeffffb80 0x24c000 0x0 0x0 ===================================================
PROCESS STATE

Process global information:
     process: e0008978, call: e0013814, curr sess: e0011c18, user sess: e0011c18
     user sessions: base 26e470, size 1, count 1
                    e0011c18 
----------------------------------------
SO: e0008978, type: 1, owner: 0, flag: INIT/-/-/0x00 (process) Oracle pid=6, calls cur/top: e0013814/e0013814, flag: -

          int error: 0, call error: 0, sess error 0   (latch info) wait_event=0 last_status=10 bits=0   Client O/S info: user: slc, term: ? , ospid: 880

            program: sqlplus_at_beta (Pipe Two-Task) orapid:881   Server O/S info: user: ?, term: ? , ospid: ?

            program: (Pipe Two-Task) orapid:881   OSD pid info: pid: 371, image:



  SO: e0011c18, type: 3, owner: e0008978, flag: INIT/-/-/0x00   (session) num: 1, trans: 0, flag: USR/-

            audit sess/ent: 1504/0, oct: 3, prv: 5, user: 52/SLC



    SO: e003f8c8, type: 8, owner: e0011c18, flag: INIT/-/-/0x00     DDL lock: obj = 700, mod = 4, flg = 01, cnt = 2

    SO: e003f894, type: 8, owner: e0011c18, flag: INIT/-/-/0x00     DDL lock: obj = 2088, mod = 4, flg = 01, cnt = 2

    SO: e003f998, type: 8, owner: e0011c18, flag: INIT/-/-/0x00     DDL lock: obj = 638, mod = 4, flg = 01, cnt = 1

    SO: e003f860, type: 8, owner: e0011c18, flag: INIT/-/-/0x00     DDL lock: obj = 636, mod = 4, flg = 01, cnt = 4

    SO: e003f7f8, type: 8, owner: e0011c18, flag: INIT/-/-/0x00     DDL lock: obj = 2093, mod = 4, flg = 01, cnt = 6

    SO: e003f790, type: 8, owner: e0011c18, flag: INIT/-/-/0x00     DDL lock: obj = 742, mod = 4, flg = 01, cnt = 4

    SO: e003fb04, type: 8, owner: e0011c18, flag: INIT/-/-/0x00     DDL lock: obj = 627, mod = 4, flg = 01, cnt = 4

    SO: e003f82c, type: 8, owner: e0011c18, flag: INIT/-/-/0x00     DDL lock: obj = 706, mod = 4, flg = 01, cnt = 6

  SO: e0013814, type: 2, owner: e0008978, flag: INIT/-/-/0x00   (call) sess: cur e0011c18, rec 0, usr e0011c18; depth: 0 dbgcbk: no case for 3

Oracle support has not had any answers for this problem. It is one we struck early last year and it went away when we added a new integrity check to the report. So when it occured again on Tuesday, we got around the problem by adding a dummy union.

Has anyone else out there come across this problem? And is there a patch that fixes it?

Changing a statement to get around an internal error is a rather crude aproach, so I was hoping that there might be a better way.

--
 
John Blackburn                                          Phone: +61 7 2534634
jb2_at_qdot.qld.gov.au                                     Fax:   +61 7 8541194
Received on Thu Nov 24 1994 - 01:49:36 CET

Original text of this message