SA-14942

Summary

Error message in PegaRULES log file after updating the JDBC driver version.
 

Error Messages

2015-07-07 13:13:30,524 [ your_node] [ STANDARD] [ ] (your_URI) ERROR - [updateNodeAddress] Exception occured while updating node address
com.pega.pegarules.pub.database.BadTableMappingException: Database-BadTableMapping-TooManyProperties System-Status-Nodes your_schema.pr_sys_statusnodes PegaDATA PYCLUSTERADDRESS , PYSYSTEMNAME , PZASMCACHECONFIGID , PXINSNAME , PYACTIVEUSERCOUNT , PYCLEANSHUTDOWN , PYNODENAME , PYBATCHINDEXBUILT , PYINDEXERADDRESS , PYSYSNODEID , PYINDEXDIRECTORY , PYCODESETSLIST , PYRUNSTATE , PYSTARTEDDATETIME , PYLASTPULSEDATETIME , PYLASTINDEXBUILDDATETIME , PYSHUTDOWNNOW , PZINSKEY , PYINDEXERSTATE , PXCREATEDATETIME , PYSTOPPEDDATETIME
 

Steps to Reproduce

Update JDBC driver from version 3.67.27 to 4.17.29.

Root Cause

A defect or configuration issue in the operating environment. You must specify, useJDBC4ColumnNameAndLabelSemantics=2 when using for IBM® Data Server Driver for JDBC and SQLJ version 4.0 and later.

Resolution

Here’s the explanation for the reported behavior:

progresssiveLocators=2
This suppresses the use of streaming when retrieving the data from any data source that happens to support that feature. The driver uses locators internally to retrieve LOB data in chunks on a need basis. Pega wants all inputs fully materialized by the driver. This is stated using the fullyMaterializeLobData=true and fullyMaterializeInputStreams=true parameters. 

​useJDBC4ColumnNameAndLabelSemantics=2
This reverts the driver to the level 3 semantics when intepreting alias references in SQL syntax. 
For IBM® Data Server Driver for JDBC and SQLJ version 4.0 and later, the default behavior of ResultSetMetaData.getColumnName and ResultSetMetaData.getColumnLabel differs from the default behavior for earlier JDBC drivers.

​Use the useJDBC4ColumnNameAndLabelSemantics property to change this behavior.