Re: Misbehaving select

From: Brent Day <coloradodba_at_gmail.com>
Date: Mon, 4 Nov 2013 19:45:16 -0700
Message-ID: <CAEz8shz4Sg3TC8k-KMYhyy7dty7TuxxYhX4kUtsBXazuMsxDQA_at_mail.gmail.com>

Jack - sorry the last response was my keyboard acting up and gmail sent before I was done.

We ran into this issue in AIX on 10.2.0.4. Look at bug 11899774

The solution was to set the following

Set "_add_col_optim_enabled"=false

You can set that at the session level and retry your query as a test. Ultimately I would recommend having Oracle to sign off on this before making it a permanent change in production.

Brent

On Mon, Nov 4, 2013 at 7:41 PM, Brent Day <coloradodba_at_gmail.com> wrote:

> Jack,
>
>
>
> On Mon, Nov 4, 2013 at 7:15 PM, Carlos Sierra <carlos.sierra.usa_at_gmail.com
> > wrote:
>
>> Jack,
>>
>> If you have the same SQL, different execution Plan, and different
>> results, then most probably you are hitting a wrong results bug in some of
>> the query transformations. I suggest you open an SR with Support and
>> provide a Test Case to reproduce your issue.
>>
>

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

Received on Tue Nov 05 2013 - 03:45:16 CET