My Oracle Support Banner

Application Queries Failing With ORA-00918 Since Applying 19.17.0.0.221018DBRU or Higher (Doc ID 2939777.1)

Last updated on JUNE 29, 2023

Applies to:

Oracle Database - Enterprise Edition - Version 19.17.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Since applying the 19.17.0.0.221018DBRU (or higher), application queries with nested ANSI joins are failing with ORA-918 reporting ambiguous column references:

00918, 00000, "column ambiguously defined"
// *Cause:     A column name used in a join exists in more than one
//             table and was thus referenced ambiguously. In a join, any
//             column name that occurs in more than one of the tables must be
//             prefixed by its table name when referenced. The column should
//             be referenced as TABLE.COLUMN or TABLE_ALIAS.COLUMN. For
//             example, if tables EMP and DEPT are being joined and both
//             contain the column DEPTNO, then all references to DEPTNO
//             should be prefixed with the table name, as in EMP.DEPTNO or
//             E.DEPTNO.
// *Action:    Prefix references to column names that exist in
//             multiple tables with either the table name or a table alias
//             and a period (.), as in the examples above. 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.