RE: Wrong results using decode when db upgraded to 9205

From: Wolfgang Breitling <breitliw_at_centrexcc.com>
Date: Wed, 05 May 2004 10:47:12 -0600
Message-Id: <6.1.0.6.2.20040505104517.02a4a1a0@pop.centrexcc.com>

Aah, so it is not a decode issue/bug but a cursor_sharing=force (or is it similar?) issue/bug.

I'd be curious what the converted sql with system forced bind variables looks like.

At 10:25 AM 5/5/2004, you wrote:
>I just found that the query in question works ... In following
>conditions ...
>
>1. using case structure instead of DECODE
>2. by running the report with cursor_sharing=3Dexact or providing
>cursor_sharing_exact hint at statement level
>3. Running the select with rule hint.
>
>BTW it is not datatype conversion issue, the actual decode statement is
>as follows ...
>
>"and decode('C8','C8','237','0') =3D '237'"
>=20
>It is becoming obvious to me that this is an optimizer issue. I'll be
>digging further ... =20
>
>Raj
>------------------------------------------------------------------------

regards

Wolfgang Breitling
Centrex Consulting Corporation
www.centrexcc.com

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Wed May 05 2004 - 11:45:50 CDT