db2 plugin broken on DB 9.1 FP 3a
---------------------------------

                 Key: GEOT-1572
                 URL: http://jira.codehaus.org/browse/GEOT-1572
             Project: GeoTools
          Issue Type: Bug
          Components: data db2
         Environment: DB2 9.1 AIX FP 3a 64 Bit
            Reporter: Christian Mueller
            Priority: Critical



class:  
DefaultFIDMapperFactory

method:     
protected ColumnInfo[] getPkColumnInfo(String catalog, String schema,
String typeName, Connection conn)
throws SchemaNotFoundException, DataSourceException 


line:
pkInfo = dbMetaData.getPrimaryKeys(catalog, schema, typeName);

results in

com.ibm.db2.jcc.a.SqlException: DB2 SQL error: SQLCODE: -443, SQLSTATE: 38553, 
SQLERRMC: SYSIBM.SQLPRIMARYKEYS;PRIMARYKEYS;SYSIBM:CLI:-805


I wrote i little test program and the following code snippet

con= DriverManager.getConnection(connectURL);

DatabaseMetaData dbMetaData = con.getMetaData();

ResultSet pkInfo = null;
pkInfo = dbMetaData.getPrimaryKeys(null, "SDE", "KATGEM");

causes this exception.

Doing the same against DB2 8.2 or DB2 9.1 FP2 works.

Obviously, this is not a problem of the plugin, it is a Problem of the jdbc 
drvier. I think you have the connections to investigate this because my app 
depends on your plugin.







-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to