ORA-00600: internal error code, arguments: [17069],
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: ORA-00600: internal error code, arguments: [17069],

  1. #1
    Join Date
    Jan 2001
    Posts
    2

    Question

    Hello all,

    Could someone tell me about his experiences with problems regarding ORA-00600: internal error code, arguments: [17069]??

    Since a few days, I get the error message:
    ORA-00600: internal error code, arguments: [17069],
    [835236320], [], [], [], [], [], []

    The trace file information for the problem looks like:

    Redo thread mounted by this instance: 1
    Oracle process number: 12
    Unix process pid: 7671, image: ora_snp0_PINF

    *** SESSION ID:(16.513) 2001.01.03.15.51.32.454
    *** 2001.01.03.15.51.32.446
    ksedmp: internal or fatal error
    ORA-00600: internal error code, arguments: [17069], [835236320], [], [], [], [], [], []
    Current SQL statement for this session:
    DECLARE job BINARY_INTEGER := :job; next_date DATE := :mydate; broken BOOLEAN := FALSE; BEGIN m
    m.mm_p_cycle_time_collect; :mydate := next_date; IF broken THEN :b := 1; ELSE :b := 0; END IF; E
    ND;


    yours sincerely
    Yves

  2. #2
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,095
    ORA-600 error messages should be reported directly to Oracle Support. They usually indicate a problem with the Oracle software and Oracle Support can provide you with a work-around or patchset.
    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
    Aug 2000
    Location
    Belgium
    Posts
    342
    found on metalink
    --------------------------------------------------------
    The problem happens every time code in package A, running as part of a scheduled job, calls dbms_job.submit() with a one-time (next=null) job, also located in package A.

    I found in some article or post on MetaLink that by converting the second parameter from the ORA-600 to hex and searching for it in the trace file near "INVL", you can find the text name of the object that is reported invalid and causing the pinning miss.

    This turned out to be package A - so in Oracle 8, the job queue fails when attempting to execute a job that runs a procedure in a package already running in another job process, as far as I can tell.
    ----------------------------------------------------------

    ORA-600:[17069] is an error signalled due to a failure to pin a library cache object--possibly the q$space.segwatch procedure. Perhaps this procedure is/was invalid at the time or was being recompiled during the execution of this job.

    ----------------------------------------------------------

    The ORA-600 17069 indicates there was a failure to pin a library cache object after 50 attempts. You can take the FFD8038 (hex conversion of [268271672]) to find which library object has problems. Look for FFD8038 in the trace file. If the Library object identified has a status = INVL, it is likely that the object (or dependent objects) have been dropped or recompiled during the execution of this process. This error will normally ocurr within long-running processes.

    Hope this helps
    Gert

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