Re: Misbehaving select
- From: Jack van Zanen <jack@xxxxxxxxxxxx>
- To: Brent Day <coloradodba@xxxxxxxxx>
- Date: Tue, 5 Nov 2013 14:05:34 +1100
Hi Brent
I don't think this bug is applicable as we actually get the result we
expect when using parallel query.
Jack van Zanen
-------------------------
This e-mail and any attachments may contain confidential material for the
sole use of the intended recipient. If you are not the intended recipient,
please be aware that any disclosure, copying, distribution or use of this
e-mail or any attachment is prohibited. If you have received this e-mail in
error, please contact the sender and delete all copies.
Thank you for your cooperation
On Tue, Nov 5, 2013 at 1:52 PM, Brent Day <coloradodba@xxxxxxxxx> wrote:
> What a night - sorry to repost on this. I gave the wrong solution from the
> SR we had opened.
>
> The final solution for the parallel query wrong results can be found in
> DOC ID 1079184.1
>
> This issue is from 10.2.0.4 - 11.1.x adn fixed in 11.2.0.2
>
> Hope that helps reduce the time to get resolution for your issue.
>
> Brent
>
>
> On Mon, Nov 4, 2013 at 7:47 PM, Brent Day <coloradodba@xxxxxxxxx> wrote:
>
>> Sorry I gave you the wrong version. This was for 11.1 but I suspect you
>> are running against the same issue.
>>
>> Brent
>>
>>
>> On Mon, Nov 4, 2013 at 7:45 PM, Brent Day <coloradodba@xxxxxxxxx> wrote:
>>
>>> 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@xxxxxxxxx> wrote:
>>>
>>>> Jack,
>>>>
>>>>
>>>>
>>>> On Mon, Nov 4, 2013 at 7:15 PM, Carlos Sierra <
>>>> carlos.sierra.usa@xxxxxxxxx> 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.
>>>>>
>>>>
>>>
>>
>
Other related posts:
