Support Article

Getting "BadTableMappingException" in logs



Table mapping exceptions appear post server restart with PRPC 6.2 SP2.

Error Messages

Error in commit() Database-BadTableMapping-TooManyProperties OB-Int-RDB-Entity entity gb_onboardingMIFIDComments

Steps to Reproduce

  1. Restart the server.
  2. Clear the pega_temp folder and perform a transaction (new/update).

Root Cause

A defect in Pegasystems code or rules related to property inheritance between internal and external tables combined with explicit property-column mappings.


Apply HFix-32029.

Published February 14, 2017 - Updated March 3, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.