Driver | Database/ Adapter IS Operating System/ Platform Affected | Limitation Description |
JT400 versions lower than 6.0 | DB2 for AS/400 (all versions) | StoredProcedureWithSignature adapter services cannot operate on a DB2 for AS/400 database when:  A stored procedure has a stored procedure name that is different from its specific name.Two stored procedures exist with the same procedure name but with different specific names. |
DB2 Net Type 3 Driver | DB2 7 on OS/390 | If you attempt to insert 20k or more records, either the system stops responding or you will receive a timeout error.StoredProcedureWithSignature services and StoredProcedureNotificationWithSignature notifications are supported only on DB2 for OS/390 V6. Instead, you can use the StoredProcedure service or StoredProcedure Notification. |
DB2 Net Type 3 Driver | DB2 7.2 on OS/390 | When configuring a Adapter for JDBC notification in Software AG Designer (File > New > Adapter Notification), the Base Name you specify on the Notification Configure tab must be no more than 5 characters because triggers on OS/390 name cannot be more than 8 characters. |
DB2 Net Type 3 Driver | DB2 on OS/390 | Using a SelectSQL service, you cannot select a large volume of data (20k) using the CLOB data type. |
DB2 Net Type 3 Driver | UDB 7.2 | The driver does not write to the JDBC log, even when the log option is enabled. The workaround is to create an empty log file. To do this, use Integration Server Administrator and select Settings > Extended > Edit Extended Settings and type: watt.adapter.JDBC.JDBCLogFile= c:\log.txtIf you run a BatchUpdateSQL service that has no records that match your search criteria, you will receive an error; you must have at least one record that matches the criteria to execute successfully. |
DB2 Net Type 3 Driver | UDB 8.1 | No error message is issued when inserting a string that is larger than the size of the column defined for CHAR(N) or VARCHAR(N). |
DB2 Net Type 3 Driver | UDB 7.2 and UDB 8.1 | StoredProcedure and StoredProcedureWithSignature adapter services, and StoredProcedure and StoredProcdeureNotificationWithSignature adapter notifications do not display functions in the Procedure Name field. The workaround is to use the StoredProcedure service or the StoredProcedureNotification and type the function name in the Procedure Name field. |
DB2 Net Type 3 Driver | UDB 9.1 | The DB2 database system does not support the type 3 driver. |
DB2 Universal Type 4 | UDB 8.x | Does not support XA transactions for versions earlier than UDB 8.2. Instead, use the Universal type 2 driver if you need XA_TRANSACTION support in versions earlier than UDB 8.2.White space characters are not removed from the SQL statements entered in the SQL textbox for CustomSQL or DynamicSQL services. This driver passes the SQL statements to the server exactly as entered. Ensure that the SQL you enter has no extraneous white space characters, such as new lines or tabs. |
DB2 Universal Type 4 | DB2 6 and DB2 7 on OS/390 | Insert, Delete, Update, Basic, and Ordered Notifications cannot be enabled if the source table contains CHAR, VARCHAR, or LONG VARCHAR columns. |
DataDirect Connect for JDBC 3.2 | DB2 UDB 7.2 | Does not support the BLOB data types. If you try to select data from a table that has BLOB data types, you receive the following message: [DataDirect][DB2 JDBC Driver][DB2]AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION 2 ON A PREPARE OR DESCRIBE OPERATION. Note: This driver supports BLOB data types using OS/390 or DB2 iSeries V5R2. Driver does not support XA_TRANSACTIONS using Java Transaction API (JTA). Instead, use UDB 8.1.Cannot insert into a BLOB column type if you use byte array as the Input Field Type. The workaround is to use the IBM drivers (DB2 app type 2 or DB2 net type 3). |
DataDirect Connect for JDBC 3.2 | DB2 UDB 7.2 and UDB 8.1 | Cannot use the CLOB data type in the OUT parameter in StoredProcedure services. You receive the following message: [DataDirect][DB2 JDBC Driver][DB2]DATA TYPE/LENGTH/VALUE OF ARGUMENT 1 OF CLOBSP1 IS INVALID. The CallableStatement.getClob() does not work; instead, use the IBM driver versions (DB2 app type 2 or DB2 net type 3). Cannot run a StoredProcedure service using BLOB and CLOB data types (java.sql.Blob or java.sql.Clob) as the IN parameter. Instead, use an IBM driver (DB2 app type 2 or DB2 net type 3) with UDB 8.1 to work with IN, OUT LOB parameters. |
DB2 JDBC App Type 2 | Linux | Cannot enable XA_TRANSACTION connections. |
DB2 JDBC App Type 2 | AIX5.1 | Cannot enable XA_TRANSACTION connections. |
DB2 JDBC App Type 2 | UDB DB2 8.1/Oracle Solaris | Cannot run a SelectSQL adapter service with table names that use special characters. Note that you can do so if you use a Microsoft Windows NT operating system and a JDBC app (type 2) driver. |
DB2 JDBC App Type 2 | UDB DB2 7.2 | If a Stored Procedure Notification has been enabled for long periods of time, the following message is posted: [IBM][CLI Driver][DB2/] SQL1131N DARI (Stored Procedure) process has been terminated abnormally is posted. SQLSTATE=38503 |
DB2 JDBC App Type 2 | UDB DB2 8.1 | No error message is issued when inserting a string that is larger than the size of the column defined for CHAR(N) or VARCHAR(N). |
DB2 JDBC App Type 2 | UDB DB2 8.1 on AIX5.1 | Integration Server crashes if the database is shut down while executing an InsertSQL adapter service using an XA_TRANSACTION connection. |
DB2 JDBC App Type 2 | UDB DB2 7.2 and UDB 8.1 | StoredProcedure and StoredProcedureWithSignature adapter services, and StoredProcedure and StoredProcdeureNotificationWithSignature adapter notifications do not display functions in the Procedure Name field. The workaround is to use the StoredProcedure service or the StoredProcedureNotification and type the function name in the Procedure Name field. |
DB2 JDBC App Type 2 | UDB DB2 9.1 | The support for DB2 JDBC App Type 2 driver is deprecated. |