RE: v$sql.parsing_user_id=0 when parser was not SYS
- From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- To: <jeremiah@xxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 25 Jul 2006 17:28:46 -0700
Not sure about the parsing_user_id=0, but to answer your question about
the separate child cursors in v$sql:
No, there should not be a separate child cursor for each user, there
should only be separate child cursors if for some reason different
executions of the same query have different schemas, optimizer parameter
settings, etc. that make it impossible for them to share the same
cursor. Usually you can see the cause of the multiple child cursors in
v$sql_shared_cursor, but not always.
Regards,
Brandon
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jeremiah Wilton
Sent: Tuesday, July 25, 2006 5:11 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: v$sql.parsing_user_id=0 when parser was not SYS
Looking at v$sql, I see that quite often a cursor that was actually
originally parsed by some user other than SYS shows a PARSING_USER_ID of
0 (SYS). How can I tell who really parsed this cursor? Shouldn't there
be a separate child cursor in v$sql for each user that uses the cursor?
Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind. Opinions, conclusions and
other information in this message that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
