Database service


Managing ServiceName warnings

CR #428432

Description: You may receive one of the following ServiceName warnings:

Workaround: Ignore each warning.


Select statement sometimes returns an update count for each row

CR # 380113

Description: When a stored procedure or SQL statement executes a select * statement, an update count is sometimes returned for each row.

Workaround: Ignore the update counts if they are not necessary for your result.


Problems using JDBC and DB2 version 7

CR # 389255

Description: You may experience problems using JDBC and DB2 version 7.

Workaround: Check the DB2 product documentation for more information.


Using an Oracle database

CR # 401643

Description: When using Oracle, the database provides time zone information in the TIMESTAMP datatype; however, JDBC does not provide for time zone information, so a class cast exception results.

Workaround: You may want to use a third-party driver, such as the DataDirectJDBC driver for Oracle, if database operations have result sets with a TIMESTAMP column.


Using a stored procedure that returns an update count from an Oracle database

CR # 389565

Description: A problem occurs when you use a stored procedure that returns an update count from an Oracle database. When the database service runs, it returns an update count for any operation. Combined with the known problem concerning how Oracle handles update counts, this problem results in the procedure running in an infinite loop.

Workaround: Use a SQL statement instead of a stored procedure to perform work in the database service.

See the Oracle product documentation for additional information regarding this issue.