Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Optimize Schema says to drop pr_index_trackstatus from PegaData



After updating from PRPC 6.3 to Pega 7.1.9, the Optimize Schema tool shows the pr_index_trackstatus table should be dropped from the Data schema and the Rules schema.

Error Messages

Not applicable

Steps to Reproduce

Go to optimize schema wizard and see the list of unused tables in data and rules schema. 

Root Cause

A defect in Pegasystems’ code or rules.  The Data-Admin-DB-Table (DADT)  instance mapping the Index-TrackStatus class to the pr_index_trackstatus table in the PegaDATA schema is missing in Pega 7.1.9.  The DADT instance exists in both Pega 7.1.8 and 7.2


Perform the following local-change: 

Create a DADT instance mapping the Index-TrackStatus to PegaDATA pr_index_trackstatus. 

Suggest Edit

Published March 25, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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

Pega Community 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
Contact us