sql parsing would be reflected in Library cache not rowcache
Basic stuff
Not that basic. Rowcache will get hit during any hard parse, since you need
to get information about objects from DD. And if objects information isn't
cached yet, it has to be loaded into row cache.
Btw, row cache locks
Hi,
Thanks for your suggestions. Usually Friday we have low traffic on our website. I
will run the database with one node to check the row cache problem.
Muqthar
-Original Message-
Sent: Friday, September 26, 2003 7:15 AM
To: Multiple recipients of list ORACLE-L
sql parsing would
To: Multiple recipients of list ORACLE-L
Subject: Re: ROW CACHE HIGH - Priority 1
sql parsing would be reflected in Library cache not rowcache
Basic stuff
Sam
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003
of list ORACLE-L
Subject: Re: ROW CACHE HIGH - Priority 1
sql parsing would be reflected in Library cache not rowcache
Basic stuff
Sam
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003 1:14 PM
General answer
Subject: Re: ROW CACHE HIGH - Priority 1
I HAVE to ask this question: Is it possible for you to turn
off RAC and
thereby completely avoiding this issue?
Yeah, that's kind of funny. Except it isn't, really. Invalidations of
objects, drops, in general breaking of breakable parse locks
sql parsing would be reflected in Library cache not rowcache
Basic stuff
Sam
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003 1:14 PM
General answer: upgrade to 9.2.0.4 and hope that the bug has been fixed.
Row cache
General answer: upgrade to 9.2.0.4 and hope that the bug has been fixed.
Row cache locks are data dictionary locks. You can see the contents of row
cache
by inspecting v$rowcache. You may need to increase shared pool.
Last but not least, how fast is your private network connection between the
two
I HAVE to ask this question: Is it possible for you to turn off RAC and
thereby completely avoiding this issue?
Yeah, that's kind of funny. Except it isn't, really. Invalidations of
objects, drops, in general breaking of breakable parse locks - they will
all need to be communicated to all the
