Unable to tokenize and detokenize after recreating a deleted token class
Originally Published: 2015-03-13
Last Modified: 2023-10-06
Article Number
Applies To
RSA Product/Service Type: Data Manager Appliance
RSA Version/Condition: 3.5.2.2
Issue
You will see this in the log attempted 10 times:
DPM Server log (key-manager.log):
Failed with error : failed due to 'PreparedStatementCallback; SQL [INSERT INTO TOKEN (TOKEN_CLASS_MUID,INPUTVALUE,HASHVALUE,TOKEN,CREATE_TIME,LAST_ACCESS_TIME, MUID_HASH_TIME) VALUES (?,?,?,?,?,?,?)]; ORA-02291: integrity constraint (LOCAL.FK_TOKEN_TOKEN_CLASS) violated - parent key not found nested exception is java.sql.SQLIntegrityConstraintViolationException: The token application will fail to locate a token to detokenize or tokenize a token.
Workaround
Log in as root:
service tomcat restart
Related Articles
How to restore RSA SecurID hardware and software tokens accidentally deleted from RSA Authentication Manager Number of Views Authenticator Registration Number of Views How to delete or remove an Authentication Manager 8.x replica with SQL commands Number of Views Offline Authentication Policy Number of Views How to delete and reinstall a virtual RSA Identity Router Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme AFX Server and Remote Collection Agents fail to start after updating Java to version 1.8u241 (1.8.0_241) / 1.7u251 (1.7.0_… Upgrade Internal Authentication Manager Certificates to SHA-256 RSA Authentication Manager 8.9 Setup and Configuration Guide Upgrading the Internal SecurID Authentication Manager 8.6 Certificates to SHA-256
Don't see what you're looking for?
