Srini,
I am sure you have lots of users in Prod compared to QA :)
Anyway, the point is that you are suffering from hot block contention which
reflects itself in latch waits on 'cache buffer chain'. I remember that
Steve Adams has a SQL at his site that identifies blocks that are 'hot' - I
have used a modified version of that to identify objects that are hot. If I
know that there are corresponding Conc. Manager jobs that are accessing that
part of the Apps, then I know that this is due to contending reports.... I
have managed to reduce this by rebuilding stale indexes as heavy
inserts/updates/deletes also add to this. Short of re-scheduling jobs and
playing around with _DB_BLOCK_HASH_LATCHES, I don't see any solutions. Do
post us if you manage to reduce contention using the _ parameter as we have
a similar problem.
John Kanagaraj
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: John Kanagaraj
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
