Results 1 to 3 of 3
  1. #1
    Join Date
    Sep 2003
    Posts
    1

    Unhappy Unanswered: unable to allocate...

    I'm getting the following error logged in the event log while using the ORACLE db

    DESC: ORA-04031: unable to allocate 64 bytes of shared memory ("large pool","unknown object","session heap","trigger condition node") Number: -2147467259

  2. #2
    Join Date
    Sep 2003
    Location
    The Netherlands
    Posts
    311
    hi,

    this means that a connection cannot be established, since there's not enough free memory to be allocated for the connection.
    Increase your SGA (especially the large pool), restart the database and try again.
    Or check for any dead connections that can be removed.

    Hope this helps
    Edwin van Hattem
    OCP DBA / System analyst

  3. #3
    Join Date
    Feb 2003
    Posts
    3
    Originally posted by evanhattem
    hi,

    this means that a connection cannot be established, since there's not enough free memory to be allocated for the connection.
    Increase your SGA (especially the large pool), restart the database and try again.
    Or check for any dead connections that can be removed.

    Hope this helps
    what is your Oracle version . if it is V 8.1.7 know that there is a bug regarding the "shared pool" management indeed the bug n1727717 has been detected by oracle and is corrected with the patch 2 of this version.
    you can solve temporarily this problem by increasing the size of the "shared pool" then stop/start the instance to take it into account (see the initXXX file to change it) but the problem will occur again in a longer term but will appear anyway. patch id : 17.
    good luck
    Stephane.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •