ORA-00600 in Alert Log . Please Help .....
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: ORA-00600 in Alert Log . Please Help .....

Hybrid View

  1. #1
    Join Date
    Sep 2000
    Posts
    362

    Angry

    Hi,
    In my alert.log I see some ORA-00600 errors. It is my production database and I have no clue as to what is this error for.
    I am running Oracle 8.0.5 on Windows NT 4.0.

    Please Help.......

    The Alert File
    --------------

    CKPT started with pid=6
    SMON started with pid=7
    RECO started with pid=8
    Wed Apr 18 21:51:24 2001
    alter database sid8 mount
    Wed Apr 18 21:51:24 2001
    Errors in file C:\orant\RDBMS80\trace\ORA00140.TRC:
    ORA-00600: internal error code, arguments: [SKGMBUSY], [1], [0], [0], [0], [], [], []

    The Trace File
    ---------------

    Dump file C:\orant\RDBMS80\trace\ORA00140.TRC
    Wed Apr 18 21:51:24 2001
    ORACLE V8.0.5.0.0 - Production vsnsta=0
    vsnsql=c vsnxtr=3
    Windows NT V4.0, OS V5.101, CPU type 586
    Oracle8 Enterprise Edition Release 8.0.5.0.0 - Production
    With the Objects option
    PL/SQL Release 8.0.5.0.0 - Production
    Windows NT V4.0, OS V5.101, CPU type 586
    Instance name: sid8

    Redo thread mounted by this instance: 0

    Oracle process number: 0

    pid: 8c


    *** 2001.04.18.21.51.23.953
    ksedmp: internal or fatal error
    ORA-00600: internal error code, arguments: [SKGMBUSY], [1], [0], [0], [0], [], [], []
    Current SQL information unavailable - no session.
    ----- Call Stack Trace -----
    calling call entry argument values in hex
    location type point (? means dubious value)
    -------------------- -------- -------------------- ----------------------------
    _ksedmp+9e CALLrel _ksedst+0
    E8D89C
    _ksfdmp+e CALLrel _ksedmp+0 3
    _kgerinv+8e CALLreg 00000000
    B0EF8
    3
    _kgesinv+19 CALLrel _kgerinv+0
    110E0
    0
    1015B760
    4
    4E8DA24
    _kgesinw+17 CALLrel _kgesinv+0
    B0EF8
    0
    1015B760
    4
    4E8DA24
    _skgmattach+2c7 CALLreg 00000000
    B0EF8
    1015B760
    4 0 1
    0 0 0
    0 0 0
    _ksmlsge+df CALLrel _skgmattach+0
    E8DCF0
    1B0DB0
    4E8DB68
    1B0E08
    _ksmlsg+2 CALLrel _ksmlsge+0 0
    _ksucre+45 CALLrel _ksucrp+0 1 0
    _kpolna+e5 CALLrel _ksucre+0 0
    _kpolon+102 CALLrel _kpolna+0 52
    4E8E078
    _opiodr+4a6 CALLreg 00000000 52 1A
    4E8F0F4
    _ttcpip+d9f CALLreg 00000000 52 1A
    4E8F0F4
    0
    _opitsk+453 CALL??? 00000000
    B2E00
    52
    4E8F0F4
    0
    4E8EF14
    4E8F5F8
    685410
    0
    _opiino+4fe CALLrel _opitsk+0 0
    _opiodr+4a6 CALLreg 00000000 3C 4
    *** Trace file full ***


  2. #2
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    ORA-600 messages are usually bugs with the database software. They should be reported to Oracle Support.
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  3. #3
    Join Date
    Feb 2001
    Posts
    123
    I have seen ORA-0600 with the same flags on IBM AIX, where IIRC it was problems with shared memory. It all went away after a reboot of the server.

    A search for SKGMBUSY on Metalink gave an Oracle forum thread, the response from the Oracle analyst is pasted below (hope nobody gets too upset about me cutting info from Metalink, and posting it here )

    HTH

    David.
    -------------
    From: Oracle, Helen Schoone 26-Jan-00 15:33
    Subject: Re : Ora-00600 [SKGMBUSY]


    Hi. It appears that on NT, this error can be signalled due to the OracleService not being stopped after shutdown and restarted prior to attempting to restart the database. Please confirm if this is your scenario. The fix is to stop and restart the OracleService prior to attempting to restart the database.

    In addition, this error can be signalled to a process instead of ORA-1034 when a process attempts to connect to the database when it is being started. The reporting of an ORA-600 instead of ORA-1034 in this case is considered a bug (939689) and is fixed in 8.0.6.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width