Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Apoorva Matolli (ApoorvaMatolli)
Marsh

Marsh
US
ApoorvaMatolli Member since 2014 14 posts
Marsh
Posted: Jun 23, 2015
Last activity: Jul 18, 2017
Posted: 23 Jun 2015 15:28 EDT
Last activity: 18 Jul 2017 10:40 EDT
Closed
Solved

BadTableMappingException

We got the following exception in all the environments -

obj-save failed.

com.pega.pegarules.pub.database.BadTableMappingException: Database-BadTableMapping-TooManyProperties <classname>

After deleting and recreating a property and clearing the conclusion cache, it now works fine in Dev. We moved the newly created property to QA and UAT and cleared the conclusion cache. We still see the error in QA and UAT.

Any idea why is this happening?

Environment pega 7.1.7

***Updated by moderator: Lochan to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

To see attachments, please log in.
Reporting
System Administration
Data Integration
Updates

Posted: 9 years ago
Posted: 23 Jun 2015 15:40 EDT
Eric Osman (ericosman_GCS) Senior Software Solutions Engineer
Pegasystems
US

uh oh this again

Sorry, it's just bringing back some memories

For starters, review any external mappings on your class, and make sure the upper-lower-case-ed-ness of all your db columns and properties and external mappings are in agreement.

/Eric

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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