RE: How to get a 10053 trace on a recursive query
- From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- To: "Finn Jorgensen" <finn.oracledba@xxxxxxxxx>, <gparc@xxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 1 May 2008 09:14:37 -0700
Thanks, but I already tried both updating and deleting the stats on
sysauth$. I didn't bother locking them though since I was just testing
immediately after the delete.
Regards,
Brandon
________________________________
From: Finn Jorgensen [mailto:finn.oracledba@xxxxxxxxx]
How about removing the stats on the sysauth$ table and locking the stats
down?
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.
- References:
- Re: How to get a 10053 trace on a recursive query
- From: Finn Jorgensen
Other related posts:
- » How to get a 10053 trace on a recursive query
- » Re: How to get a 10053 trace on a recursive query
- » Re: How to get a 10053 trace on a recursive query
- » RE: How to get a 10053 trace on a recursive query
- » RE: How to get a 10053 trace on a recursive query
- » RE: How to get a 10053 trace on a recursive query
- » RE: How to get a 10053 trace on a recursive query
- » Re: How to get a 10053 trace on a recursive query
- » RE: How to get a 10053 trace on a recursive query
- » Re: How to get a 10053 trace on a recursive query
- Re: How to get a 10053 trace on a recursive query
- From: Finn Jorgensen