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
How to modify the number of allowable active tokens per user on RSA Authentication Manager 8.x 73Number of Views A large number of user sessions showing on the UI in SecurID Governance & Lifecycle 191Number 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 223Number of Views Maximum number of incorrect login attempts for RSA Authentication Manager Operations Console administrator 195Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory
Don't see what you're looking for?