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

Home -> Community -> Usenet -> c.d.o.server -> Re: How to identify whether or not client session get ORA-1652 of TEMP in RAC.

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Tue, 11 Nov 2003 20:52:40 -0000
Message-ID: <boriaa$eqc$2$8302bc10@news.demon.co.uk>

Watch out for the latching.

When a session is resumable, it records every call in a view called v$resumable_session (or similar) which has to be a latch-protected area of the SGA. Consequently you might see latch contention in a highly concurrent system - but I haven't checked to see which latch it might be.

--
Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

  The educated person is not the person
  who can answer the questions, but the
  person who can question the answers -- T. Schick Jr


One-day tutorials:
http://www.jlcomp.demon.co.uk/tutorial.html
____Belgium__November (EOUG event - "Troubleshooting")
____UK_______December (UKOUG conference - "CBO")


Three-day seminar:
see http://www.jlcomp.demon.co.uk/seminar.html
____UK___November


The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html


"wangbin" <wangbin_at_start.com.au> wrote in message
news:2d15bd69.0311102342.79638850_at_posting.google.com...


> 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

>

Received on Tue Nov 11 2003 - 14:52:40 CST