SQL Language (MOSC)

MOSC Banner

pre RU16 hits no ORA-00918 ==>since RU17 ORA-00918 is raised

edited Oct 26, 2022 1:17PM in SQL Language (MOSC) 4 commentsAnswered

Oracle 19c, RU17

Hi, with new RU17 a bug was fixed, which caused so far, that an ambiguously defined column not raised an ORA-00918.

I wrote this, because I think that many applications maybe has wrong SQL which were tolerated bei parser until RU16, but with RU17 not.

Here is the way to reproduce the behavior:

create table t1 (id int);

create table t2 (id int);

insert into t1 values(1);

insert into t1 values(2);

insert into t2 values(1);

insert into t2 values(2);

commit;


>>POST RU17 (correct behavior)

select a_t2.id from t1 a_t1

inner join t2 a_t2 on a_t1.id=a_t2.id

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center