My Oracle Support Banner

Ambiguous Column References On Some Repository Queries (Doc ID 2002992.1)

Last updated on DECEMBER 22, 2016

Applies to:

Oracle Commerce Platform - Version 9.0 to 10.0.3.5 [Release 9 to 10]
Information in this document applies to any platform.

Symptoms

Querying a repository may result in the following SQL exceptions:

Oracle

2015-04-21 10:05:37,978 ERROR [nucleusNamespace.atg.dynamo.droplet.RQLQueryForEach] (http-127.0.0.1-8280-1) unable to parse/execute query due to RepositoryException
CAUGHT AT:
CONTAINER:atg.repository.RepositoryException; SOURCE:java.sql.SQLException: java.sql.SQLSyntaxErrorException: ORA-00918: column ambiguously defined

MySQL

09:46:33,738 ERROR [STDERR] CONTAINER:atg.repository.RepositoryException;
SOURCE:java.sql.SQLException: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Not unique table/alias: 't2'

DB2

SOURCE EXCEPTION:
java.sql.SQLException: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-203, SQLSTATE=42702, SQLERRMC=T3.TRANSLATION_ID, DRIVER=4.16.53

This only occurs with certain repository definitions that require a query to have multiple inner joins.

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
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.