Peter Blood - Oracle Tips

ORA-00600: internal error code, arguments: [17113], [0x000000000], [], [], [], [], [], []

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

Metalink says:

DESCRIPTION:

An error occurred when getting a new extent while adding to a heap.

The heap descriptor is uninitialized.

ARGUMENTS:
Arg [a] Always 0

FUNCTIONALITY:
HEAP MANAGER

IMPACT:
PROCESS FAILURE
MEMORY CORRUPTION
NON DATA CORRUPTIVE - No underlying data corruption.

SUGGESTIONS:

These errors can occur after the actual Oracle in-memory corruption
has taken place.

Hence the processes that report the error may not be the ones that
caused it.

Check for third party software being used to access the database.
This error can be reported when there are compatibility issues
between third party software and the database.

Check for other messages preceeding this message.

Check if the problem is reproducable.

Run memory diagnostics on all system hardware.

If the Known Issues section below does not help in terms of identifying
a solution, please submit the trace files and alert.log to Oracle
Support Services for further analysis.

Additional references to bug 3066549.

Looking at the trace file:

ORA-00600: internal error code, arguments: [17113], [0x000000000], [], [], [], [], [], []Current SQL statement for this session:BEGIN DBMS_OUTPUT.ENABLE(1000000); END;

.......

O/S info: user: xxxxxxxx, term: XXXXXXX, ospid: 2880:2460, machine: XXXXXXX\XXXXXXX program: C:\Documents and Settings\All Users\Start Menu\P application name: C:\Documents and Settings\All Users\Start Menu\P, hash value=0 last wait for 'SQL*Net message from client' blocking sess=0x0 seq=23 wait_time=2161 driver id=54435000, #bytes=1, =0 temporary object counter: 0

.......

Open Cursors:
BEGIN DBMS_OUTPUT.ENABLE(1000000); END;

SELECT SYS_CONTEXT(:B2,:B1) FROM SYS.DUAL

SELECT UPPER(NVL(V.OSUSER,'ALL')), UPPER(NVL(V.USERNAME,V.SCHEMANAME)), UPPER(NVL(SUBSTR(V.PROGRAM,1,48),'ALL')) FROM V$SESSIONV WHERE V.AUDSID = :B1 AND ROWNUM < 2

SELECT COUNT(*), MAX(SQL_TRACE) FROM USER_BIN B WHERE (B.OSUSER = :B3 OR B.OSUSER = 'ALL') AND (B.USERNAME = :B2 OR B.USERNAME = 'ALL') AND (:B1 LIKE ('%' B.PROGRAM '%') OR B.PROGRAM = 'ALL') AND ROWNUM < 2

INSERT INTO USER_LOG SELECT V.OSUSER, V.USERNAME, V.MACHINE, SYS_CONTEXT('USERENV','SESSIONID'), V.PROGRAM, SYSDATE, :B2 FROM V$SESSION V WHERE V.AUDSID = :B1

I'll keep looking into this. Judging by the code on trace file it seems to be some kind of error on event based trigger we have on this database to save object structure before change or deletion. Anyway, Oracle's explanation over errors when selecting from a view doesn't seem to apply. More on this later.

posted by Pedro Oliveira @ 1:48 AM