| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: 9.2 V$ views
Regarding v$lock slow and dba_jobs_running
It seems that these are known bugs.
See =
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_da=
tabase_id=3DBUG&p_id=3D2578217
and =
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_da=
tabase_id=3DBUG&p_id=3D2799566
where there are suggested replacements from gv$lock, v$lock, =
dba_jobs_running
and a list of other views which cause accesses to gv$lock.
I had somewhat similar problems under 81745 and there was a replacement = for catblock.sql as described in Metalink note 122567.1.
However, the 817 problems could be reproduced with just 1 lock & 1 =
blocker.
Under 9.2.0.5 patch 2 on W2K SP4, I can't notice a slow performance of =
v$lock with just 1 lock - maybe it requires a few more.
HTH,
Bruce Reardon
NOTICE: This e-mail and any attachments are private and confidential and =
may contain legally privileged information. If you are not an =
authorised recipient, the copying or distribution of this e-mail and any =
attachments is prohibited and you must not read, print or act in =
reliance on this e-mail or attachments. This notice should not be =
removed.
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Tanel P=F5der
Sent: Tuesday, 27 July 2004 8:10 AM
<snip>
> from
> v$_lock l
> ,x$ksuse s
> ,x$ksqrs r
> where l.saddr=3Ds.addr
> and l.raddr=3Dr.addr
> ;
And when you go RAC, your queries from v$lock will start returning extra rows for each instance, because there is no inst_id restriction in the = view.
Generally I'd advise against changing any of v$ views or public synonyms =
on
them, instead I'd try to find another solution first (like even =
analyzing DD
in 9.2, etc.).
One solution to get your own custom v$ views is to make a v$lock view or
synonym to your own schema. Local schema objects take preference over =
public
synonyms when referenced in SQL, that way you don't change any of the =
SYS
objects, which is mostly unsupported anyway.
Tanel.
-- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------Received on Mon Jul 26 2004 - 17:28:26 CDT
 |
 |