JDBC/ODBC eWay not honoring default schema in the JDBC URL (Doc ID 1025393.1)

Last updated on NOVEMBER 02, 2016

Applies to:

Oracle Java CAPS - Version 5.1.0 and later
Information in this document applies to any platform.
***Checked for relevance on 16-Oct-2016***


Symptoms

Our connection url:
jdbc:as400://<hostname>;naming=sql;errors=full;libraries=TEST

I would expect our SQL to resolve unqualified names using that schema. But it didn't, it looks like it is using the userid instead to qualify it by the message we got from the log:

[#|2007-04-17T15:39:13.572-0500|SEVERE|IS5.1.2|STC.eWay.DB.JDBC.com.stc.connector.jdbcadapter.base.PreparedStatementAgentImpl|_ThreadID=29; ThreadName=Worker: 50;|[SQL0204] <database_tablename> in <database_username> type *FILE not found.|#]

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms