Getting "BadTableMappingException" in logs
SummaryTable mapping exceptions appear post server restart with PRPC 6.2 SP2.
Error MessagesError in commit()
com.pega.pegarules.pub.database.BadTableMappingException: Database-BadTableMapping-TooManyProperties OB-Int-RDB-Entity entity gb_onboardingMIFIDComments
Steps to Reproduce
- Restart the server.
- Clear the pega_temp folder and perform a transaction (new/update).
Root CauseA defect in Pegasystems code or rules related to property inheritance between internal and external tables combined with explicit property-column mappings.
Published February 14, 2017 - Updated March 3, 2017