000029813 - Unable to tokenize and detokenize after recreating a deleted token class

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 22, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000029813
Applies ToRSA Product Set: Data Protection Manager
RSA Product/Service Type: Data Manager Appliance
RSA Version/Condition: 3.5.2.2
 
IssueIf a token class gets deleted and recreated.
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. 
WorkaroundAfter recreating a token class after it has been deleted bounce Tomcat:
Log in as root:
service tomcat restart

Attachments

    Outcomes