Skip to main content

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.

Support Article

After upgrade DB2 drivers and unable to connect



User unable to connect to external database after DB2 JDBC driver upgrade. User has replaced new db2jcc4.jar file, modified the required CLASSPATH entries within IBM WebSphere Application Server, stopped all applications, cleared out the temp files and restarted the applications.
Running "Test Connections" on the Database rule failed throwing the ERROR below:

** There was a database problem when performing an RDBExecute: code: -4460 SQLState: <none> Message: [jcc][10150][10300][4.19.26] Invalid parameter: Unknown column name PZPVSTREAM. ERRORCODE=-4460, SQLSTATE=null

Error Messages

Caused by SQL Problems.

Problem #1, SQLState null, Error code -4460: [jcc][10150][10300][4.19.26] Invalid parameter: Unknown column name PZPVSTREAM. ERRORCODE=-4460, SQLSTATE=null

Steps to Reproduce

1. Navigate to Records > Database.
2. Click “Test Connection”.

Root Cause

A third-party product configuration issue. The above DB2 ErrorCode is thrown, when the DB2 JDBC Datasource does not have the connection property “useJDBC4ColumnNameAndLabelSemantics” set to “2”.  When using a DB2 JDBC driver which uses JDBC 4.0 standards, this property must be set for the database query to handle column labels correctly. This has been documented in the PRPC WAS DB2 installation guide. 


Make the following local-change to the operating environment: 

Set the following DB2 JDBC Datasource connection property -  
For complete instructions refer to section “Configure Data Source Connection” in Page 45 of the Install guide in link below:

Suggest Edit

Published May 2, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us