CA-Ingres II 2.6 SP2: JDBC EDBC Driver: DatabaseMetaData.getTables() method

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

Dear everyone.

We are experience abnormal behaviour with the CA-Ingres II 2.6 SP2: JDBC
EDBC Driver: DatabaseMetaData.getTables() method.

Our Environment:
· Solaris 8
· CA-Ingres II 2.6 SP2 DBMS
· Database with tables using LONG VARCHAR and LONG BYTE

The DatabaseMetaData.getTables() method includes the "iietab" tables thare
the DBMS uses to store LONG VARCHAR and LONG BYTE data.

We believe this is incorrect behaviour given that those tables are not
intended to be manipulated by applications or DBMS users. These tables are
for DBMS usage only.

Has anyone experienced this behaviour? Has anyone logged any support calls
with CA? If so, what is the outcome?

Does anyone have any immediate workarounds?

The issue is inconvenient, where we want to use the dbunit (www.dbunit.org)
tool to export data from one database and import to another database.

I am interested in any responses.

Kind Regards,


--
Jason Tepoorten
@HOME
+61 433 176 821 (mobile telephone)
jason (AT) tepoorten (DOT) com
8MP
Australia

I've posted this message on dbForums at URL:
http://www.dbforums.com/showthread.p...11#post4376111

--
Jason Tepoorten
@HOME
+61 433 176 821 (mobile telephone)
jason (AT) tepoorten (DOT) com
8MP
Australia

"djtep" <spare1 (AT) djtep (DOT) com> wrote

A support call was raised with Computer Associates and they were able
to provide a patched EDBC.JAR.

--
Jason Tepoorten
@HOME
+61 433 176 821 (mobile telephone)
jason (AT) tepoorten (DOT) com
8MP
Australia

"djtep" <spare1 (AT) djtep (DOT) com> wrote