Tables of Unknown Origin Created In Data Schems
I am writing this post to try and determine the origin of about 200 tables that have been created in one of our Pega environments. The tables are not part of the application and were not created by anyone on the team. Given that we have to assume that Pega created them for some reason and are trying to understand why. Also note that we have deployed this application for 2 customers in 8 different environments and these additional tables are only showing up in one of these environments.
A small sample of the table names are contained in the attached screen shot......some of the table name prefixes are listed below
PR_HISTORY_CMIS_*
PR_HISTORY_CMIS_CMIS*
PR_HISTORY_DATA_DECISION*
PR_HISTORY_DATA_MO_DSM_*
PR_HISTORY_DATA_SAMLASSE_*
There are others and there now over 250 of them.
Most all of the tables have the same set of columns and all of then ones I checked have no data in them.
Thanks
***Updated by Moderator: Vidyaranjan. Removed user added #helpme and Ask the Expert tags. Apologies for confusion, shouldn't have been an end-user option***
***Updated by moderator: Marissa to update categories***
Pegasystems Inc.
IN
Hi Chris,
PRPC’s default mapping of concrete classes is to one of four default (and very generic) tables:
· PR_OTHER
· PR_DATA
· PR_HISTORY
· PR_INDEX
These tables are bare bones and do not have exposed columns nor indexes to support your queries.
The part coming up after the 'PR_HISTORY_CMIS_CMIS' is the hexadecimal conversion of the class that is used as the unique key for this table and mapping back with the Pega class.
You should not delete these table's since pega internal mechanisms are using the xml structure in it.
NASCO
US
So out of all of the environments that we have for this application. Why am I seeing them in just one of the environments. What happened to cause this behavior in this environment.