- 08 Nov, 2021
- 0 Comments
- 3 Mins Read
ORA-00918: column ambiguously defined
ORA-00918: COLUMN AMBIGUOUSLY DEFINED
ORA-00918: column ambiguously defined error occurs when a column name in a join exists in more than one table and is thus referenced ambiguously. The ORA 00918 column ambiguously defined error occurs when attempting to join two or more tables with the same name across columns. This column name is referred as an ambiguous reference. If a column with the same name exists in two or more tables, the column name should be prefixed with the table name in joins. Otherwise, the column is identified ambiguously in the join, and the sql query is unable to determine the column name from the tables. In this scenario, the error message ORA-00918: column ambiguously defined will be shown.
The joins in the sql query combine all of the columns from two or more tables. If a column name is used in two or more tables, the column name is ambiguously recognized in the SQL join. Oracle will give an error ORA-00918: column ambiguously defined, if the column name is used to refer. The reference to the column name should be distinguished in some way. There are several methods for uniquely identifying the column names in the join.
When the ORA-00918 error occur
If two or more tables with the same column name are created and joined in a sql query, the column name may be recognized ambiguously. Because the column name is available in all of the join tables, Oracle could not match with any one table to get the data. The error ORA-00918: column ambiguously defined will be thrown in this scenario.
Problem
1 2 3 4 5 6 7 8 9 10 11 12 | create table dept(deptid number primary key,deptname varchar2(100));create table employee(id number primary key,name varchar2(100),deptid number, foreign key(deptid) references dept(deptid));select * from dept, employee where deptid=1; |
Error
1 2 3 4 5 | ORA-00918: column ambiguously defined00918. 00000 - "column ambiguously defined"*Cause: *Action:Error at Line: 16 Column: 36 |
Root Cause
If more than one table includes the same column name and refers to those columns in a join, the column name will be ambiguous. Oracle will search in the joined tables if you refer to the column name. If the same column name appears in two or more tables, the column name is identified ambiguously. With those tables, the join could not be performed. There is no way to distinguish the columns.
Solution 1
If the same column name appears in multiple tables and is referenced in a join, the column name becomes ambiguous. In sql joins, the column name is identified ambiguously. It is necessary to differentiate the columns in the joins. One method is to prefix the table name when referring it in joins. The table name is used to uniquely identify the column name
Problem
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | create table dept(deptid number primary key,deptname varchar2(100));create table employee(id number primary key,name varchar2(100),deptid number, foreign key(deptid) references dept(deptid));select * from dept, employee where deptid=1;ORA-00918: column ambiguously defined00918. 00000 - "column ambiguously defined" |
Solution
1 | select * from dept, employee where dept.deptid=1; |
Solution 2
The column name becomes ambiguous if it occurs in many tables and is referenced in a join. The column name is ambiguously recognized in sql joins. In order to separate the columns in the joins, they must be differentiated. If you use the same table in a sql join again, referencing the column by table name will fail. The table alias should be used to refer to the column name in this situation.
Problem
1 2 3 4 5 6 7 8 9 10 | create table employee(id number primary key,name varchar2(100),managerid number, foreign key(managerid) references employee(id));select * from employee, employee where id=managerid;ORA-00918: column ambiguously defined00918. 00000 - "column ambiguously defined" |
Solution
1 | select * from employee mgr, employee emp where mgr.id=emp.managerid; |
Solution 3
When a column name appears in many tables and is referenced in a join, it becomes confusing. In sql joins, the column name is recognized ambiguously. The columns in the joins must be distinct in order to be separated. You may use a select query to change the column names before using them in joins. The select query will provide a list of unique column names to which you may refer. In the example below a select query is used in the joins.
Problem
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | create table dept(deptid number primary key,deptname varchar2(100));create table employee(id number primary key,name varchar2(100),deptid number, foreign key(deptid) references dept(deptid));select * from dept, employee where deptid=1;ORA-00918: column ambiguously defined00918. 00000 - "column ambiguously defined" |
Solution
1 | select * from dept, (select deptid departmentid from employee) where deptid=1; |