Re: Strange Behaviour (with Test Case)

From: Tanel Poder <tanel_at_tanelpoder.com>
Date: Wed, 5 Aug 2015 16:29:08 -0500
Message-ID: <CAMHX9JKaqhAyWkbpqpN+-x+kyE7=ns36D6huwS8ksXujmxQVzA_at_mail.gmail.com>



Try with this ;-)

ALTER SESSION SET EVENTS '10055 trace name context forever, level 0x200';

(parse a new cursor or flush shared pool for testing)

On Tue, Aug 4, 2015 at 4:51 AM, Patrick Jolliffe <jolliffe_at_gmail.com> wrote:

> I have been working though a strange case, seems specific to Exadata 12c.
> I have simplified as much as possible for now, testcase below.
> Obviously we are following up with Oracle support, but wonder if anyone is
> able to confirm what we are seeing.
> And/Or anybody want to hazard a guess as to what is going wrong?
> TIA
> Patrick
>
>
> CREATE TABLE TEST_FACT(CHRTYPE VARCHAR2(3), RATE NUMBER)
> INSERT INTO TEST_FACT VALUES('R03', 1.3)
> INSERT INTO TEST_FACT VALUES('R03', 1.3)
> INSERT INTO TEST_FACT VALUES('LDU', 0.21)
> COMMIT;
>
> SELECT SUM(
> CASE
> WHEN (CHRTYPE = 'R03' OR CHRTYPE = 'LDU')
> THEN RATE /10
> END )
> FROM TEST_FACT;
>
> Result on 11.2.0.4.4 and 12.1.0.2.3 (Linux)
> 0.281
>
> 12.1.0.2.7 (Exadata)
> -8.70E+103
>

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Aug 05 2015 - 23:29:08 CEST

Original text of this message