Re: workaround for v$sql

From: Wolfgang Breitling <breitliw_at_centrexcc.com>
Date: Fri, 16 Mar 2007 12:47:41 -0600
Message-Id: <20070316184636.3FF6D647BC5@turing.freelists.org>

10gR2 if I'm not mistaken. A client encountered the ora-600 errors on a 10.1.0.5 system. Interestingly enough not on their 9.2.0.7 system. It probably depends on the complexity of the sql whether you hit the bug or not.

They were given a workaround: set _cursor_plan_unparse_enabled = false. As far as I recall, Could also be _cursor_plan_enabled = false;

At 11:10 AM 3/16/2007, Alberto Dell'Era wrote:
>On 3/16/07, Ankur Godambe <agodambe_at_ketera.com> wrote:
>>changes. I hit this bug#4434689 with 9.2.0.7 where selects on v$sql_plan
>>failes with ora-600 [504].
>
>I haven't found the bug on Metalink; if the bug is similar to 2525630,
>you can avoid the ORA-600 by not selecting access_predicates
>and filter_predicates. These informations are lost, but at least you have
>the rest of the plans.
>
>The bug is solved in 10g.

Regards

Wolfgang Breitling
Centrex Consulting Corporation
www.centrexcc.com

This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email

--
http://www.freelists.org/webpage/oracle-l

Received on Fri Mar 16 2007 - 13:47:41 CDT

Re: workaround for v$sql_plan