My Oracle Support Banner

'311 : ZZZZZ : com.sybase.jdbc2.jdbc.SybSQLException' Message Signaled In An ODI Integration Interface With Sybase Jconnect JDBC Driver (Doc ID 423985.1)

Last updated on JUNE 16, 2022

Applies to:

Oracle Data Integrator - Version and later
Information in this document applies to any platform.


An ODI Integration Interface includes 2 Source Datastores, one of which is a lookup table. A filter is set on the lookup Datastore and a simple join is inserted between the 2 Datastores.

When the Loading KM runs, the generated SQL instruction appears to be applying the filter to the reference Datastore. However, the instruction fails with the following message :

311 : ZZZZZ : com.sybase.jdbc2.jdbc.SybSQLException: The optimizer could not find a unique index which it could use to scan table '<myTable>' for cursor 'jconnect_implicit_<theCursorNumber>'

When running the SQL instruction directly against the Datastore it works correctly.

Is it mandatory to create an index on the lookup table ?


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
 What are the implications for performance of this parameter value?

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