Because the numbers are added up. Those specific statistics are not designed to be aggregated. On 5/31/05, Amihay Gonen <AmihayG@xxxxxxxxx> wrote: > Hi. > I have some specific situation that I can't find any acceptable explanati= on > to it. > We have some DB server (oracle 9i) with 24GB ram and 1.7 > PGA_aggregate_target defined. > There is some cut from statspack below. >=20 > The question how session pga memory max can grow to 140Gb and session pga > memory to 6Gb? > If it isnt bug how its possible and what does it mean? >=20 >=20 >=20 > Statistic Total per Second per Trans > --------------------------------- ------------------ -------------- > ------------ > session pga memory 5,833,839,984 270,523.5 21,892.6 > session pga memory max 140,591,794,472 6,519,443.3 527,598.4 > session uga memory 452,728,840 20,993.7 1,699.0 > session uga memory max 25,300,354,184 1,173,213.7 94,944.6 >=20 >=20 >=20 > Amihay Gonen > DBA, > 972-3-9268280 >=20 > Be there ... -> http://golan/Forum%20DBA/default.aspx >=20 >=20 >=20 > -- > //www.freelists.org/webpage/oracle-l >=20 --=20 Christo Kutrovsky Database/System Administrator The Pythian Group -- //www.freelists.org/webpage/oracle-l