Error ORA-04030: out of process memory
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 7 of 7

Thread: Error ORA-04030: out of process memory

  1. #1
    Join Date
    Nov 2000
    Posts
    35

    Error ORA-04030: out of process memory

    When i am running a sql file againt one database I am getting the following error .

    ORA-20001: Update statement.:ORA-04030: out of process memory when trying to
    allocate 475276 bytes (callheap,DARWIN)


    Could anybody help me How to fix this error.

    Thanks in advance

  2. #2
    Join Date
    Oct 2000
    Location
    Germany
    Posts
    1,185
    Is your shared pool large enough?

    You could be a hitting a bug that was fixed in 8.1.7.3.
    David Knight
    OCP DBA 8i, 9i, 10g

  3. #3
    Join Date
    Jan 2002
    Location
    Canada
    Posts
    195
    Is this happening in 8i or 9i?

  4. #4
    Join Date
    Nov 2000
    Posts
    35
    RDBMS version is 8i

    and

    shared_pool_reserved_size 30000000
    shared_pool_size 700000000

  5. #5
    Join Date
    Nov 2002
    Location
    New Delhi, INDIA
    Posts
    1,796
    Or you can try

    if this is a unix machine and you are using a telnet session do

    $ ulimit -d unlimited
    $ ulimit -s unlimited
    $ ulimit -m unlimited
    $ ulimit -n unlimited
    $ ulimit -c unlimited

    and then try....

    HTH
    Amar
    Amar
    "There is a difference between knowing the path and walking the path."

    Amar's Blog  Get Firefox!

  6. #6
    Join Date
    Nov 2000
    Posts
    35
    Found that the following event has been set.

    event = "10235 trace name context forever, level 1"


    Is this causing the problem ?

  7. #7
    Join Date
    Nov 2002
    Location
    New Delhi, INDIA
    Posts
    1,796
    Originally posted by ganjisb
    Found that the following event has been set.

    event = "10235 trace name context forever, level 1"


    Is this causing the problem ?
    This event will check the memory manager internal structures. and generates trace in the UDUMP.

    This can be a possible cause as this degrades the performance.

    According to metalink

    -------------------------------------------------------
    This event may be used to try to catch HEAP corruption problems closer to when they occur. Typically level 12 is required to get close to the corruption but this can impact performance too much to be useful.
    -------------------------------------------------------

    Try removing this parameter and then startup the database and run the querry again.

    Regards
    Amar
    Amar
    "There is a difference between knowing the path and walking the path."

    Amar's Blog  Get Firefox!

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