pga_aggregate_target to workaround pga memory leak?
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: pga_aggregate_target to workaround pga memory leak?

  1. #1
    Join Date
    Jun 2000
    Posts
    417

    pga_aggregate_target to workaround pga memory leak?

    We are experiencing a pga memory leak. So far I have not matched it up to a specific bug, and because of our environment we can't really work with support to narrow it down. I'll work on isolating the problem myself but....

    I'm looking for a workaround. Typically we see the allocated PGA increase much faster than what is actually being used. I'm looking into seeing if we can workaround this with pga_aggregate_target & workarea_size_policy.

    Is pga_aggregate_target a hard limit? IE, if I have a leaking PGA will it stop there? I'm sure it would depend on the leak, I'm just talking through it to see if the concept has merit.

    As an aside, is there any way to free a processes unused, allocated PGA?

    Thanks

  2. #2
    Join Date
    May 2000
    Location
    ATLANTA, GA, USA
    Posts
    3,135
    Try this in your code:
    dbms_session.free_unused_user_memory ;

    This will free up PGA and UGA.

    Tamil

  3. #3
    Join Date
    Jun 2000
    Posts
    417
    Thanks Tamil,

    Do you know if there is a way to execute this for another session? I didn't see anything in dbms_system or oradebug which would help.

    Pat

  4. #4
    Join Date
    May 2000
    Location
    ATLANTA, GA, USA
    Posts
    3,135
    You will not see it in dbms_system pkg.

    Tamil

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