RE: Wrong results using decode when db upgraded to 9205

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
------------------------------------------------------------------------
--------=20
Rajendra dot Jamadagni at nospamespn dot com=20
All Views expressed in this email are strictly personal.=20
select standard_disclaimer from company_requirements;=20
QOTD: Any clod can have facts, having an opinion is an art !

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Stefan Jahnke
Sent: Wednesday, May 05, 2004 11:56 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: AW: Wrong results using decode when db upgraded to 9205

Hi again

Sorry, haven't looked into it. Since we already changed everything to =
=3D
CASE on 9.2.0.4.0. The reason wasn't a bug but to be coherent with the =
=3D
usage of DECODE / CASE. We agreed upon ANSI style stuff (INNER JOIN, =3D
CASE blahblah) since 2 developers have a SQL Server background and seem
=3D to comprehend that faster (no pun intended, they're great).

Stefan


----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
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
-----------------------------------------------------------------

Other related posts: