The number of STX tables in RSA Identity Governance & Lifecycle database is increasing
Originally Published: 2018-03-05
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
Allow a large number of RADIUS clients to authenticate without adding an agent for each client in RSA Authentication Manag… 312Number of Views iOS App Transport Security ATS enablement notification for RSA SecurID Software Token for iOS and RSA Authentication Manag… 24Number of Views FINAL REMINDER: iOS App Transport Security ATS enablement notification for RSA SecurID Software Token for iOS and RSA Auth… 7Number of Views REMINDER: iOS App Transport Security ATS enablement notification for RSA SecurID Software Token for iOS and RSA Authentica… 7Number of Views Maximum number of incorrect login attempts for RSA Authentication Manager Operations Console administrator 191Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Governance & Lifecycle 8.0.0 Installation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA MFA Agent for UNIX Platform Support Matrix Performing RADIUS authentication tests with NTRadPing to RSA Authentication Manager
Don't see what you're looking for?