Re: How to identify whether or not client session get ORA-1652 of TEMP in RAC.

Thanks Jonathan. It works. Amazing. I even don't need "after suspend" trigger.

Without resumable, 1652 will been generated in alert.log whenever reassignment happens. When I enable resumable with a timeout of 1, only 'real' 1652 apears in alert.log, the reassignment ones disappear. So all I need is an "LOGON ON" trigger to enable resumable.

Well, I'm not sure about the side-effects. I will put it into test env see how it goes.

Regards,
Bin

"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message news:<bonilh$ipa$1$8300dec7_at_news.demon.co.uk>...
> Have a look at resumable sessions and the 'after suspend'
> trigger. A 'real' 1652 will then put the session that has a
> problem into suspension and fire the after suspend trigger.
> Give it a timeout of (say) 10 seconds so that it really
> crashes the end-user afterwards, but make sure it logs
> the problem. It is possible that a 'spurious' 1652 that
> can be resolved by extent reallocation will not cause a
> suspension.
>
> Test carefully. I haven't tried setting sessions resumable
> en masse, so there may be odd side-effects - especially
> on a RAC system.
>
> --
> Regards
>
> Jonathan Lewis
> http://www.jlcomp.demon.co.uk
>
Received on Tue Nov 11 2003 - 01:42:03 CST