The number of STX tables in RSA Identity Governance & Lifecycle database is increasing
Originally Published: 2018-03-05
Last Modified: 2023-11-30
Article Number
Applies To
Issue
Cause
One known reason for the STX tables not being dropped is when the circuit breaker is triggered.
Resolution
STX tables that are being used by active collections should not be dropped. Therefore, the safest way to remove these tables is to shutdown acm to ensure no collections are running. Steps to follow are shown below.
- Shutdown acm
$ acm stop
- Login to SQL as the AVUSER.
- Execute the following SQL to find all the tables to be dropped:
SELECT table_name FROM user_catalog WHERE table_name LIKE 'STX%'
- Drop all the STX tables:
BEGIN FOR tablename IN (SELECT table_name FROM user_catalog WHERE table_name LIKE 'STX%') LOOP EXECUTE IMMEDIATE 'DROP TABLE ' || tablename.table_name || ' purge'; END LOOP; END;
- Restart acm:
$ acm start
Related Articles
A large number of user sessions showing on the UI in SecurID Governance & Lifecycle 193Number of Views How to modify the number of allowable active tokens per user on RSA Authentication Manager 8.x 73Number of Views Allow a large number of RADIUS clients to authenticate without adding an agent for each client in RSA Authentication Manag… 312Number of Views Maximum number of offline days allowed for an RSA Authentication Agent for Windows 227Number of Views 'UT000047: The number of parameters exceeded the maximum of 1000' error when adding User Attributes in RSA Identity Govern… 187Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?