Error faced while getting the VDB Metadata using the ODBC Driver

[cgausub]

The issue is occurring in a specific scenario for an oracle source model.

Consider the following table in oracle-

Name Null? Type

----------------------------------------- -------- ----------------------------

CUSTOMER_ID NOT NULL NUMBER

CUST_FIRST_NAME NOT NULL VARCHAR2(20)

CUST_LAST_NAME NOT NULL VARCHAR2(20)

CUST_STREET_ADDRESS1 VARCHAR2(60)

CUST_STREET_ADDRESS2 VARCHAR2(60)

CUST_CITY VARCHAR2(30)

CUST_STATE VARCHAR2(2)

CUST_POSTAL_CODE VARCHAR2(10)

PHONE_NUMBER1 VARCHAR2(25)

PHONE_NUMBER2 VARCHAR2(25)

CREDIT_LIMIT NUMBER(9,2)

CUST_EMAIL VARCHAR2(30)

Customer_ID is a NUMBER type column with Scale and precision as undefined.

In this case the oracle jdbc driver returns the Scale as 38 and precision as 2147483647and the following function ((4 + (65536 * t1__1."Precision")) + t1__1.Scale) exceeds the Integer Max Value.

This results in an exception while Querying the VDB metadata using the ODBC driver.

[rareddy]

With addressed some precision issues with JIRA [TEIID-3517] The oracle importer should offer an option to use integral types - JBoss Issue Tracker in 8.11. Are you using 8.11.Final or can you try 8.11.Final and see if this is still an issue?

[cgausub]

We are using teiid embedded build 8.11.0.Final. Let me in case I need to share any other information regarding the issue being faced.

[rareddy]

BTW, the above only comes into play if you are using the Dynamic VDB. If you are using the Designer, you can manually edit the column properties to set a correct precision. If that is the case you can also log a JIRA for Designer import.

[cgausub]

Yes we are using a dynamic VDB with Teiid embedded

[rareddy]

As JIRA says use "useIntegralTypes" option, check the docs for the how to set it.

[shawkins]

TEIID-3502 or a new issues needs to address the metadata overflow.

[shawkins]

This will be addressed in 8.12 and 8.11.1

[cgausub]

Thanks, that should help