Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Problems with PGA_AGGREGATE_TARGET on Tru64
Hi all,
Compaq HP Tru64 Unix running 9i Rel2
Site where I'm working decided to switch on PGA_AGGREGATE_TARGET to hopefully reduce our PGA memory usage. Initially all looked great, we were using heaps less real memory with our usual (900+) number of connections and it was smiles all round. Then sirens started yelling and red lights flashing as we saw our swap space grow and grow and grow... Shit, it was worse than the funny chap with the beanstalk. Before we knew it, approx 5G of used real memory (with heaps and heaps to spare) had fully consumed our 32G swap space and that was it folks. No more connections and the fan was covered in brown stuff.
Now after a bit of a chat with Oracle Support, we were told that our "eager" swap mode could be the problem and that using lazy swapping should do the trick. With the PGA_AGGREGATE_TARGET, we've had so such issues with eager. Initial tests seem to confirm that lazy should be hunky dory with PGA_A_T
Thought I might just ask all you good folks out there if anyone else has had similar problems with this on Tru64 and if anyone else has got this parameter working OK with/without eager/lazy swapping.
Thanks for any info/feedback.
Cheers
Richard Received on Wed Feb 19 2003 - 08:26:21 CST
![]() |
![]() |