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

Stale SAML related data left in pr_data_admin table



There are more than 50000 records related to SAML login processing in pr_data_admin table.

Error Messages

Not Applicable

Steps to Reproduce

1. Use OpenSAML2.0 for SSO

Root Cause

A defect in Pegasystems’ code or rules. DB contention in pr_data_admin table as this table is used by other Pega modules including SAML related classes. There has been huge amount of left over data from Data-Admin-LoginInfo and Data-Admin-Security-SSO-SAML-AuthRequestContext classes in the pr_data_admin table. pyCleanupWebSSO agent is scheduled to run every 24 hours which is intended to clean any SAML related data in the pr_data_admin, but it only purges 100 records at each run and would not suffice to clean up 50,000+ stale records.


Make the following change to the operating environment: Create a cron job scheduler that runs frequently to execute SQL DELETE on pr_data_admin table to purge instances of Data-Admin-LoginInfo and Data-Admin-Security-SSO-SAML-AuthRequestContext. Purge records 2 minutes or older

    FROM pr_data_admin
   WHERE PXOBJCLASS IN ('Data-Admin-LoginInfo', 'Data-Admin-Security-SSO-SAML-AuthRequestContext') AND
    PXCOMMITDATETIME < (SYSDATE - (2 / 1440));

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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