'some complaining about system memory was used up when the target is
set.'
I need to research this. I cant find anything on google. anyone have
comments? I thought pga_aggregate_target was the way to go.
Ask the dba to submit proof.
If something goes wrong, it is always caused by
- the database
- the upgrade
- the new features in the upgrade
(Cross all that apply)
--
Sybrand Bakker, Senior Oracle DBA
Hi Ryan,
O/S Platform would surely be useful ...
On HP Tru64 with "Eager" swapping mode set we had a nasty shock with P_A_T
in that the O/S was more than eager and "ate" all our 32G of swap space with
less than 3G of PGA used. This was highlighted by Oracle Support as an
expected feature !! By bouncing the box and setting the swap mode to lazy,
P_A_T has subsequently worked beautifully with an overall saving of 2G of
memory, better sort (etc.) performance and a rather idle swap disk as a
result.
You could have run into the same/similar problem.
BTW, I discussed this here and at the L-Oracle Mail list a number of times.
Cheers
Richard
we are on solaris. any word on that platform?