Symptom

When you're using a Rule-RDB-SQL rule to connect to an IBM DB2 database, if the instance contains a non-string tag substitution for a typed value, the DB2 JDBC drivers report an error -- because they are expecting an integer instead of a string.

Example:

select * from table where id = {page.propertyName}

[where {page.propertyName} is an integer value]

Solution

This problem occurs with version 1.0.581 of the DB2 JDBC drivers.  The problem is not present with version 1.5.54 of the drivers.  It appears that newer drivers are more forgiving when handling non-string values that are represented as strings when passed in with a prepared statement.