WITH Clause Query Returning Wrong Column Results After Database Upgrade From 22.214.171.124 To 126.96.36.199
(Doc ID 2571683.1)
Last updated on FEBRUARY 26, 2020
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206.0 [Release 12.2 to 19]
Information in this document applies to any platform.
- After database upgrade from 220.127.116.11 to 18.104.22.168, WITH clause query returns wrong column values
- Example testcase shows the symptom:
create table t1 as
select rownum as n1, 'C'||rownum as c1 from dual connect by level <= 2;
with s1 as (
select /*+ MATERIALIZE */ c1 from t1 a1
, s2 as (
select /*+ MATERIALIZE */ n1
, nvl((select max('Y') from t1 a2, s1
where a2.n1 = a3.n1 and a2.c1 = s1.c1), 'N') as yn1
from t1 a3
select (select max(yn1) from s2 where s2.n1 = 2) as yn2
Above query returns output 'N', but it should return 'Y'.
Database upgraded from 22.214.171.124 to 126.96.36.199.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document