4) Check if using the Parallel Query Option - if an operation is
being performed in parallel the memory requirements are greater.
@ 5) If it is none of these we need to know the problem statement.
@ If there is any doubt about the statement set:
@
@ event="4030 trace name errorstack level 3"
@
@ for the database OR:
@
@ alter session set events '4030 trace name errorstack level 3';
@
@ for the problem session.
@
@ 6) From the ERRORSTACK check the PLSQL call stack for a recusrsive
@ loop. Eg:
@ ----- PL/SQL Call Stack -----
@ object line object
@ handle number name
@ 3355fcc 1666 package body PIMS.CORE
@ 3355fcc 544 package body PIMS.CORE
@ 3355fcc 1666 package body PIMS.CORE
@ 3355fcc 544 package body PIMS.CORE
@ 3355fcc 1666 package body PIMS.CORE
@ 3355fcc 544 package body PIMS.CORE
@ ....
@ If found this is most likely an application bug. Dump the source
@ lines
@
@ 7) Are they using any of:
@
@ Partition Views with large numbers of partitions,
@ Bitmap indexes
@ Large inlists.作者: iamnothing 時(shí)間: 2003-07-02 17:24 標(biāo)題: 請(qǐng)教！ up一下把作者: rollingpig 時(shí)間: 2003-07-02 17:58 標(biāo)題: 請(qǐng)教！ $ORACLE_HOME/dbs/init$ORACLE_SID.ora