Have you enabled the Scan "Processes On Enable" setting, in the OAS configuration?
This feature scans memory. It is invoked after DAT update.
That forces Windows to do some memory management magic, which will include pagination of processes.
Setting was enabled so turned it off, one of the servers was fine this morning other still had the issue and had it's DB failed over.
I have updated both servers to Patch 6 and will reboot them tonight, check again in the morning.
Thanks for the help.
*** update ***
It seems the server that worked did not run its update at 4am for some reason.
When I kicked off the DAT update the event ID 906 occurred, so it seems that disabling the option made no difference.
That particular setting requires a reboot to be cleared from memory, unfortunately. Once it is on, it cannot simply be turned off. Though disabling it in policy is necessary of course, but it takes a reboot to make the change stick.
We're getting exactly the same DB performance degradation errors. The OAS 'Processes on enable" setting has been enabled since day 1.
Anyone got any further with this?