ora-0430 and ora-0431
DBAsupport.com Forums - Powered by vBulletin
Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: ora-0430 and ora-0431

  1. #1
    Join Date
    Jan 2001
    Posts
    230
    Hi:

    Os : windows NT

    I am having two ora problem
    1) ORA-0430 out of process memory when trying to allocate num bytes str,str
    2)ora-0431 unable to allocate num bytes of shared memory num,num,num

    What do I need to do to resolve this problem...

    Thanks.

  2. #2
    Join Date
    Jan 2001
    Posts
    230

    Correction

    ora-0430 => ora-04030
    ora-0431 => ora-04031

  3. #3
    Join Date
    Sep 2001
    Location
    Fort Smith
    Posts
    184
    This may be a bug or related to memory leakage.
    I do not know ur version of Oracle and NT version and sp number applied.
    sonofsita
    http://www.ordba.net

  4. #4
    Join Date
    Jan 2001
    Posts
    230

    Windows NT 4.o SP6..

  5. #5
    Join Date
    Jan 2001
    Posts
    230

    Oracle version is 8.1.6.1.0


  6. #6
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Yes, it may be a bug, but I would look at your use of reusable SQL first. See http://metalink.oracle.com/metalink/...&p_id=146599.1 to diagnose.
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  7. #7
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    many times 4031 is caused by MTS and large pool settings

    it basically means that your shared pool is fragmentated and Oracle cannot allocate enough contiguos memory for a large object in the shared pool, if that was the case you should check

    SHARED_POOL_RESERVED_MIN_ALLOC and
    SHARED_POOL_RESERVED_SIZE

    If you are in 8i SHARED_POOL_RESERVED_MIN_ALLOC is a hidden parameter

    in the case of MTS you may see something like unable to allocate string bytes of shared memory
    ("string","string","string","large pool") this is probably your large pool is not large enough

    Quoted from Metalink:

    Large Pool is an area of SGA similar to Shared Pool. If large pool is defined
    in init.ora then MTS will use large pool (instead of shared pool) for User
    Global Area (UGA). Oracle8 explicitly allocate memory from large pool to user
    session and once alllocated it never aged out as long as the user session are
    connected to the database. If there is not enough free memory in large pool
    the new connection to the database might get ORA-4031.


    ORA-04030 is more complicated as it is related to the OS process memory allocation and sometimes it is related to application bugs, try generate a trace file

    set this in your initSID.ora

    event="4030 trace name errorstack level 10"

    sometimes it may be because your sort_area_size is too large

    If it wasnt a bug or sort_area_size you have to check your kernel parameters, sometime the error is because the process grew up too much and reached the limit for
    the operating system kernel parameter that defines the maximum process size

  8. #8
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    Sorry, forget the kernel parameters, I didnt see it was NT

    But anyway, does this happen consistently? When does it happen? During any specific process or just a simple query? If it was a simple query most probably it's a bug

  9. #9
    Join Date
    Jan 2001
    Posts
    230
    Jeff:

    Where can I find more info on ora-04030

    Thanks.

  10. #10
    Join Date
    Sep 2001
    Location
    Fort Smith
    Posts
    184
    sonofsita
    http://www.ordba.net

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