Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting: Connecting to IBM DB2 databases with JDBC

Updated on September 13, 2021


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.


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

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


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.


  • Previous topic Troubleshooting: Commit error after exposing new column
  • Next topic Troubleshooting: Database-Saver-InsertUpdatefail error caused by multiple database schemas on one PegaRULES database


Pega Platform 7.1.1 - 8.3.1 System Architect System/Cloud Ops Administrator System Administration

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us