Support Article
Database-BadTableMapping-TooManyProperties error
SA-9864
Summary
When you are importing an application built in Pega 7.1.6 into Pega 7.1.7. When doing so, you receive an error "Database-BadTableMapping-TooManyProperties".
Error Messages
2015-05-04 13:23:15,683 [fault (self-tuning)'] [l0_WorkTab] [MyApp:03.10.01] (_CPMFW_Work_Interaction.Action) ERROR myserver.exampleorganization.com|testapp - obj-save failed.
com.pega.pegarules.pub.database.BadTableMappingException: Database-BadTableMapping-TooManyProperties Index-PegaCA-ContactInteractions MYSCHEMA.pca_index_interactions PegaDATA ContactChannel
From: (H4EF9283ED525E1E789CE9C3C3DEF7593:myserver.exampleorganization.com)
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:332)
at com.pega.pegarules.data.internal.access.DatabaseImpl.attemptToProcessUpdates(DatabaseImpl.java:2625)
at com.pega.pegarules.data.internal.access.DatabaseImpl.processUpdates(DatabaseImpl.java:2288)
at com.pega.pegarules.data.internal.access.Saver.save(Saver.java:663)
at com.pega.pegarules.data.internal.access.DatabaseImpl.save(DatabaseImpl.java:4930)
at com.pega.pegarules.data.internal.access.DatabaseImpl.save(DatabaseImpl.java:4916)
at com.pegarules.generated.activity.ra_action_cainteractionstartmanual_804120bd009ae21a5e94529722e0de22.step18_circum0(ra_action_cainteractionstartmanual_804120bd009ae21a5e94529722e0de22.java:1338)
at com.pegarules.generated.activity.ra_action_cainteractionstartmanual_804120bd009ae21a5e94529722e0de22.perform(ra_action_cainteractionstartmanual_804120bd009ae21a5e94529722e0de22.java:408)
Steps to Reproduce
Import legacy application rules to new Pega 7.1.7 environment.
Root Cause
User's database table is missing columns which are required for implementing configuration.
Resolution
This issue is resolved through the following local-change: Double-check your database table to ensure that all required columns have been added.
Published July 7, 2015 - 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.