Message-Id: <10708.124341@fatcity.com> From: Vivek Date: Tue, 12 Dec 2000 11:25:43 -0500 Subject: large uga/pga and scan rates Hi: Steve Adams has given a good explanation on memory allocation and deallocation in hos book Oracle 8i internal services Chapter 6 - Process memory allocation, Process Memory deallocation. HTH Vivek ------------------------------------------------------------------- From: Henry Poras Date: Mon, 11 Dec 2000 10:38:30 -0500 Subject: RE: large uga/pga and scan rates That is exactly what I am seeing. But I also remember reading what Ron quoted from the Concepts manual "Once connected, a user can never run = out of PGA space; there is either enough or not enough memory to connect in = the first place." If true, how can the process memory (dedicated) grow with = no bounds? I'll try running some pmap(s) today and see if that gives any = clues (not that I'm too familiar with the output). I'll post that data when = I've got it. Thanks. Henry -----Original Message----- Sent: Monday, December 11, 2000 4:21 AM To: Multiple recipients of list ORACLE-L Hi, The pga memory is not fixed (I am talking if you're not using MTS).=20 The process will take what it needs until it reaches the OS limit. I had a similar case on Oracle 8.0.4/HP 10.20 with a function in a select. The select was bringing back more than 500 000 rows. Oracle was not releasing the memory after the function call.=20