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

DB2 errors on startup

SA-8499

Summary



DB2 errors on PegaRULES application startup in PegaRULES log.

The system starts and user can log in, however, some instances cannot be seen. For example: user cannot view instance lists.


Error Messages



883 [ VMIKSA69901A4P] [ STANDARD] [ ] ( internal.es.NodesTableDAO) ERROR - Failed to update System-Status-Node instance: Database-BadTableMapping-TooManyProperties System-Status-Nodes PRPC.pr_sys_statusnodes PegaDATA PYSTARTEDDATETIME , PYACTIVEUSERCOUNT , PZASMCACHECONFIGID , PYSTOPPEDDATETIME , PYINDEXDIRECTORY , PYBATCHINDEXBUILT , PYCLUSTERADDRESS , PYCLEANSHUTDOWN , PYNODENAME , PYCODESETSLIST , PXCREATEDATETIME , PYSYSNODEID , PZINSKEY , PYINDEXERSTATE , PYLASTPULSEDATETIME , PYINDEXERADDRESS , PYLASTINDEXBUILDDATETIME , PYRUNSTATE , PYSYSTEMNAME , PYSHUTDOWNNOW , PXINSNAME
.
.
.
133 [ VMIKSA69901A4P] [ STANDARD] [ ] (.internal.PRSearchProviderImpl) INFO - Initialized full text search functionality for this node.
165 [ VMIKSA69901A4P] [ STANDARD] [ ] ( pega.highavailability.quiesce) ERROR - [updateNodeAddress] Exception occured while updating node address
com.pega.pegarules.pub.database.BadTableMappingException: Database-BadTableMapping-TooManyProperties System-Status-Nodes PRPC.pr_sys_statusnodes PegaDATA PYSTARTEDDATETIME , PYACTIVEUSERCOUNT , PZASMCACHECONFIGID , PYSTOPPEDDATETIME , PYINDEXDIRECTORY , PYBATCHINDEXBUILT , PYCLUSTERADDRESS , PYCLEANSHUTDOWN , PYNODENAME , PYCODESETSLIST , PXCREATEDATETIME , PYSYSNODEID , PZINSKEY , PYINDEXERSTATE , PYLASTPULSEDATETIME , PYINDEXERADDRESS , PYLASTINDEXBUILDDATETIME , PYRUNSTATE , PYSYSTEMNAME , PYSHUTDOWNNOW , PXINSNAME
From: (B16FCB7BEDE4B37A00416721BFA6B643A:(PREnvironment))
at com.pega.pegarules.data.internal.access.PageDatabaseMapperImpl.fillInSaveStatementWithoutStream(PageDatabaseMapperImpl.java:1644)
at com.pega.pegarules.data.internal.access.Saver.addBatch(Saver.java:948)
at com.pega.pegarules.data.internal.access.Saver.saveInstance(Saver.java:796)
at com.pega.pegarules.data.internal.access.Committer.performOps(Committer.java:284)
at com.pega.pegarules.data.internal.access.DatabaseImpl.attemptToProcessUpdates(DatabaseImpl.java:2625)
at com.pega.pegarules.data.internal.access.DatabaseImpl.processUpdates(DatabaseImpl.java:2288)



Steps to Reproduce



Start the Pega 7.1.7 Server.

Root Cause



The root cause of this problem is a missing JDBC Custom property in IBM Websphere Application server’s PegaRULES Datasource.

Resolution



This issue is resolved by making the following change to the operating environment:
 
Advised user to add the following JDBC Custom property under the PegaRULES Datasource and restart the JVM(s) .
Name:  useJDBC4ColumnNameAndLabelSemantics
Value: 2

Published June 12, 2015 - 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