Wednesday, September 29, 2004

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

Oracle Version: 9.2.0.5.0
O.S. : HP/UX 11i
Machine: HP9000

Checking Metalink

There are several notes on this one: 39616.1, 151992.1, 266513.1, 268423.1, 283246.1, 268413.1, 271733.1, 241824.1 and 214242.1. Most of this notes are about upgrade issues, which is not the case. Checking the trace file, the error was in some function execution:

ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [17069], [0xC000000161802748], [], [], [], [], [], []
Current SQL statement for this session:
BEGIN :ret := P105_GETINVOICE_CALL; END;

Going down a little bit further on the trace file we find:

last wait for 'library cache pin' blocking sess=0x0 seq=5058 wait_time=3007838

Back to Metalink, the first 2 notes may have some information. Note 39616.1 states that error description is: Failed to pin a library cache object after 50 attempts.

This may also be some problem connected with the shared pool. Are there any ORA-04031 failures?

Let's try this little script:

column kghlurcr heading "RECURRENTCHUNKS"
column kghlutrn heading "TRANSIENTCHUNKS"
column kghlufsh heading "FLUSHEDCHUNKS"
column kghluops heading "PINS ANDRELEASES"
column kghlunfu heading "ORA-4031ERRORS"
column kghlunfs heading "LAST ERRORSIZE"
select kghlurcr, kghlutrn, kghlufsh, kghluops, kghlunfu, kghlunfs
from sys.x$kghlu
where inst_id = userenv('Instance')
/

RECURRENT TRANSIENT FLUSHED PINS AND ORA-4031 LAST ERROR
CHUNKS CHUNKS CHUNKS RELEASES ERRORS SIZE
---------- ---------- ---------- ---------- ---------- ----------
12887 22473 902500 485956809 6 912

That's it. Maybe it is time to bounce the database, or flush the shared pool.

[Update]

I've checked with the users and actually this happens because a previous run of the same job is still running. I was told that the function actually has a semaphore but it seems that it isn't working well. A deeper look at the actual coding may be necessary. More on this later.

0 Comments:

Post a Comment

<< Home