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

Update to JDBC 4 DB2 driver BadTableMapping-TooManyProperties

SA-36065

Summary



DB2 Driver update to JDBC driver version : 4.12.55 produces errors.

Error Messages



[setRunState] Exception occured while setting RunState
com.pega.pegarules.pub.database.BadTableMappingException: Database-BadTableMapping-TooManyProperties System-Status-Nodes data.pr_sys_statusnodes PegaDATA PYSTARTEDDATETIME , PYACTIVEUSERCOUNT , PZASMCACHECONFIGID , PYSTOPPEDDATETIME , PYINDEXDIRECTORY , PYBATCHINDEXBUILT , PYCLUSTERADDRESS , PYCLEANSHUTDOWN , PYNODENAME , PYCODESETSLIST , PXCREATEDATETIME , PYSYSNODEID , PZINSKEY , PYINDEXERSTATE , PYLASTPULSEDATETIME , PYLASTINDEXBUILDDATETIME , PYINDEXERADDRESS , PYRUNSTATE , PYSYSTEMNAME , PYSHUTDOWNNOW , PXINSNAME
From: (BF302880FB63B2749935473D0E723833E:(Master For New Agents))

[3/31/17 13:12:04:970 EDT] 0000007d SystemOut O 2017-03-31 13:12:04,968 [r.SRMWorkManager : 1] [ STANDARD] [ ] [ PegaRULES:07.10] (unt.System_Status_Nodes.Action) ERROR - obj-save failed.
com.pega.pegarules.pub.database.BadTableMappingException: Database-BadTableMapping-TooManyProperties System-Status-Nodes data.pr_sys_statusnodes PegaDATA PYSTARTEDDATETIME , PZASMCACHECONFIGID , PYACTIVEUSERCOUNT , PYSTOPPEDDATETIME , PYINDEXDIRECTORY , PYBATCHINDEXBUILT , PYCLUSTERADDRESS , PYCLEANSHUTDOWN , PYNODENAME , PYCODESETSLIST , PXCREATEDATETIME , PYSYSNODEID , PZINSKEY , PYINDEXERSTATE , PYLASTPULSEDATETIME , PYLASTINDEXBUILDDATETIME , PYINDEXERADDRESS , PYRUNSTATE , PYSYSTEMNAME , PYSHUTDOWNNOW , PXINSNAME


Steps to Reproduce

  1. For the DB2 JDBC Provider, update the DB2 driver JAR file from db2jcc.jar to db2jcc4.jar.
  2. Restart the JVM.


Root Cause



A third-party product issue

Part of the update to the JDBC 4 compliance DB2 driver technology changed the way that column aliases are handled.
The error is thrown if the
useJDBC4ColumnNameAndLabelSemantics=2 custom parameter is not set for the data source.

Resolution



Make the following change to the operating environment:

Set the custom property
useJDBC4ColumnNameAndLabelSemantics=2 in the JDBC data source.

Published May 1, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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.

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