Results 1 to 3 of 3
  1. #1
    Join Date
    Dec 2007
    Posts
    4

    Unanswered: ORA-04030: out of process memory

    Hi all,

    We have oracle10g db running on AIX 5.3. While executing one function which includes an insert statement containing multiple group by clause getting following error.

    ORA-04030: out of process memory when trying to allocate 258072 bytes (QERGH hash-agg,kllcqas:kllsltba)

    but same function we are able to execute on our development setup. We have compared each and every parameter such as sga_max_size, pga_aggregate_target, shared_pool_size with our development setup but still we are clueless.

    your immediate response will be appreciated.

    Thanks & regards,
    B D Yadav

  2. #2
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    Code:
    04030, 00000, "out of process memory when trying to allocate %s bytes (%s,%s)"
    // *Cause:  Operating system process private memory has been exhausted
    It might be the case the ulimit values do not meet Oracle recommendations.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  3. #3
    Join Date
    Jul 2002
    Location
    Vista, CA
    Posts
    3
    Quote Originally Posted by bdyadav
    Hi all,

    We have oracle10g db running on AIX 5.3. While executing one function which includes an insert statement containing multiple group by clause getting following error.

    ORA-04030: out of process memory when trying to allocate 258072 bytes (QERGH hash-agg,kllcqas:kllsltba)

    but same function we are able to execute on our development setup. We have compared each and every parameter such as sga_max_size, pga_aggregate_target, shared_pool_size with our development setup but still we are clueless.

    your immediate response will be appreciated.

    Thanks & regards,
    B D Yadav
    But have you compared memory usage between your production and development? It could be simply that your usage is greater, running out of some system resource.

    See metalink Note: 233869.1 and 199746.1 for the usual things to do.

    If you want a magic bullet guess, cut your pga_aggregate_target in half.

    It could also be a sort issue, if you set sort parameters for the session smaller, you may force it to tempfiles quicker, avoiding the lack of resources.

    I've run into this sort of thing by not having enough swap configured and adding another instance (like for an RMAN repository - not on aix, but could be unix-non-specific).

Posting Permissions

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