Support Article
BadTableMappingException occurs during Rulebase upgrade
SA-60876
Summary
While upgrading to Pega 7.3.1, BadTableMappingException occurs during Rulebase upgrade. This occurs while running upgrade.sh on the Rulebase.
Error Messages
Caused by: com.pega.pegarules.pub.database.BadTableMappingException: Database-BadTableMapping-TooManyProperties System-Status-Nodes CATRDBA.pr_sys_statusnodes PegaRULES PYSTARTEDDATETIME , PYACTIVEUSERCOUNT , PZASMCACHECONFIGID , PYSTOPPEDDATETIME , PYINDEXDIRECTORY , PYBATCHINDEXBUILT , PYCLUSTERADDRESS , PYCLEANSHUTDOWN , PYNODENAME , PYCODESETSLIST , PXCREATEDATETIME , PYSYSNODEID , PXCLUSTERID , PZINSKEY , PYINDEXERSTATE , PYLASTPULSEDATETIME , PYLASTINDEXBUILDDATETIME , PYINDEXERADDRESS , PYRUNSTATE , PYSYSTEMNAME , PZSOURCEREVISION , PYSHUTDOWNNOW , PXINSNAME
Steps to Reproduce
- Upgrade from PRPV 6.2 SP2 to Pega 7.3.1.
- Perform the upgrade until upgrade script execution on Rulebase upgrade.
- Run the upgrade.sh to upgrade the Rulebase.
Root Cause
A software use or operation error. The URL used for the upgrade did not have all necessary connection properties.
Resolution
Make the following change to the operating environment:
The URL used for the DB2 connection must follow the below format and include all of these connection properties.
jdbc:db2://localhost:50000/dbName:fullyMaterializeLobData=true;fullyMaterializeInputStreams=true;progressiveStreaming=2;useJDBC4ColumnNameAndLabelSemantics=2;
Published July 23, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.