Databases Reference
In-Depth Information
Valid levels for this event are 1, 2, 3, 32, and 536870912 plus one of the levels between 1 and
32. Among others, the resulting trace file contains a call stack trace and the SQL statement,
which was active at the time when the error occurred.
ioc_allocate (size: 4096, heap name: *** SGA ***, flags: 110009) caught 4031
*** 2007-11-12 16:20:54.359
ksedmp: internal or fatal error
ORA-04031: unable to allocate 4096 bytes of shared memory ("java pool",
"unknown object","joxs heap","Intern")
Current SQL statement for this session:
SELECT SYNNAM, DBMS_JAVA.LONGNAME(SYNNAM), DBMS_JAVA.LONGNAME(SYNTAB),
TABOWN, TABNODE, PUBLIC$, SYNOWN, SYNOWNID, TABOWNID, SYNOBJNO
FROM SYS.EXU9SYN WHERE SYNOWNID = :1 ORDER BY SYNTIME
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
…
After collecting sufficient diagnostic data, the dump event may be disabled with the
following statement:
SQL> ALTER SYSTEM SET EVENTS '4031 trace name heapdump off';
System altered.
Immediate Dumps
Using the following syntax, it is also possible to request that a dump be taken immediately:
ALTER SESSION SET EVENTS 'IMMEDIATE TRACE NAME dump_name LEVEL lvl'
If you suspect that an instance is hanging, you might take a system state dump like this:
SQL> ALTER SESSION SET EVENTS 'immediate trace name systemstate level 10';
Session altered.
The header of a system state dump looks as follows:
SYSTEM STATE
------------
System global information:
processes: base 6ED426BC, size 50, cleanup 6ED47FF4
allocation: free sessions 6ED60D60, free calls 00000000
control alloc errors: 0 (process), 0 (session), 0 (call)
PMON latch cleanup depth: 0
seconds since PMON's last scan for dead processes: 21
system statistics:
166 logons cumulative
18 logons current
1082648 opened cursors cumulative
25 opened cursors current
