Is there a way to identify the offending sql in trace file?

From: Guang Mei <gmei_at_incyte.com>
Date: Thu, 10 Apr 2003 15:08:36 -0800
Message-ID: <F001.0057F51C.20030410150836@fatcity.com>

Hi:

We have oracle 8173 on Solaris 2.8. Occuasionally we get a dump file (see below). The program that caused this has many sqls and I am wondering if there is a way to "identify" which one generated the dump. The program runs daily so it is not a source code bug (otherwise we would get daily dump). I know that ORA-00600 [729] is an oracle bug and I have already set the following in init.ora file:

event = "10262 trace name context forever, level 4000"

We can not upgrade to new oracle version now. And I don't want to just increase the level in init.ora setting to mask this bug, I would prefer to make s ome change in the program to "avoid" this error, if possible.

TIA. Guang

• partial dump file in udump directory:
  • 2003-04-10 02:25:50.896 ksedmp: internal or fatal error ORA-00600: internal error code, arguments: [729], [6400], [space leak], [], [], [], [] , [] ----- Call Stack Trace ----- calling call entry argument values in hex location type point (? means dubious value) -------------------- -------- --------------------

    ---

    ksedmp()+168 CALL ksedst()+0 3B8 ? 1 ? FFBEC820 ? FFBEC2C4 ? FFBEC2A8 ? 0 ? kgeriv()+196 PTR_CALL 00000000 3 ? 0 ? 0 ? 258 ? 1 ? 2D9 ? kgesiv()+96 CALL kgeriv()+0 1A609B4 ? 1AB89BC ? 15FBB0C ? 2 ? FFBED038 ? 1A4EAC4 ? ksesic2()+64 CALL kgesiv()+0 1A609B4 ? 1AB89BC ? 2D9 ? 2 ? FFBED038 ? 1ABBB50 ? ksmuhe()+664 CALL ksesic2()+0 2D9 ? 0 ? 1900 ? 1 ? A ? 1910724 ? ksmugf()+344 CALL ksmuhe()+0 1910724 ? 1A61C00 ? 1ABBB4C ? 1 ? 1900 ? 1A6E938 ? ksuxds()+4548 CALL ksmugf()+0 A8764330 ? A87647F8 ? 1 ? 1A61C00 ? 1A60888 ? 0 ? ksudel()+24 CALL ksuxds()+0 1601000 ? 1A60800 ? 1 ? A8764330 ? FFBED2C8 ? 1 ? opilof()+1120 CALL ksudel()+0 A8764330 ? 1 ? 1A61C00 ? 1A60800 ? 2 ? 1A62000 ? opiodr()+5748 PTR_CALL 00000000 FFBED50C ? 0 ? FFBEF0D0 ? 0 ? 3 ? FFBEF1D7 ? ttcpip()+956 PTR_CALL 00000000 16AE680 ? FFBED874 ? 1A64800 ? 0 ? 16E39FE ? 54435000 ? opitsk()+664 CALL ttcpip()+0 1A635B0 ? 1A6368C ? 16E39FE ? FFBEE6EC ? FFBEE8D0 ? FFBEE6E8 ? opiino()+1792 CALL opitsk()+0 0 ? 1A62308 ? 1A64D84 ? 0 ? 1 ? 0 ? opiodr()+5748 PTR_CALL 00000000 FFBEFAD0 ? 80005000 ? 1A63400 ? 1A9B328 ? 0 ? 1A4EAC4 ? opidrv()+1308 CALL opiodr()+0 16AE9B0 ? FFBEF6D4 ? 1A64800 ? 0 ? 16E3ACA ? 1A6E938 ? sou2o()+20 CALL opidrv()+0 3C ? FFBEF7E4 ? 1A60800 ? 2F6C6F67 ? 0 ? 2F ? main()+160 CALL sou2o()+0 FFBEFAE0 ? 3C ? 4 ? FFBEFAD0 ? 17A8BE4 ? 1A6E938 ? _start()+220 CALL main()+0 0 ? FFBEFC8C ? 1A87910 ? 1A60400 ? 0 ? 0 ? ----- Argument/Register Address Dump ----- Argument/Register addr=ffbec820.

--

Please see the official ORACLE-L FAQ: http://www.orafaq.net
--

Author: Guang Mei
  INET: gmei_at_incyte.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Thu Apr 10 2003 - 18:08:36 CDT