Support Article
PR_DATA_DM_ADMMART_PRED_FACT table data growth causes lock
Summary
In Pega 7.2, PR_DATA_DM_ADMMART_PRED_FACT table has grown to 42+ million records in six days in only one data center.
Is this expected behavior, and are there recommendations to optimize it?
Also, observe locks on the table created by the daily executed query:
Delete From PR_DATA_DM_ADMMART_PRED_FACT Where pxObjClass = :"SYS_B_0" and pySnapshotTime = :1
Is there an agent causing this, such that one can change the scheduled time when it is running?Error Messages
Data growth and the locks mentioned during daily execution of the query.
Steps to Reproduce
Pega 7.2's DSM application executed.
Root Cause
If the predictor binning snapshot for the ADM models is enabled; there will be huge writes seen on the PR_DATA_DM_ADMMART_PRED_FACT database table.
Resolution
If predictor binning snapshots are not required, then disable it on the DSM Services landing page.
Published August 24, 2016 - 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.