Data Purging process (as part of Data Archiving) fails with ORA-01722 in RSA Identity Governance & Lifecycle
4 years ago
Originally Published: 2021-02-25
Article Number
000045174
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.2.1, 7.2.0, 7.1.1
 
Issue
Data Purging process, as part of Data Archiving, fails with the following exception in aveksaServer.log file:
  
10/31/2020 21:15:39.830 ERROR (Exec Task Consumer#0 - Main) [com.aveksa.server.xfw.TaskExecutor] Failed method=Execute ExecutionTask[TaskID=1294636 RunID=503884 Source=1 Type=DataPurging Status=InProgress]
com.aveksa.server.xfw.ExecutionException: com.aveksa.server.db.PersistenceException: java.sql.SQLSyntaxErrorException: ORA-01722: invalid number
ORA-06512: at "AVUSER.ARCHIVEPURGE_PKG", line 1176
ORA-02292: integrity constraint (AVUSER.FK_T_TEMP_PWD_CHG_REQ_DET) violated - child record found
ORA-06512: at "AVUSER.DATA_PRUNING_PKG", line 200
ORA-06512: at "AVUSER.DATA_PRUNING_PKG", line 99
ORA-06512: at line 1

 
Cause

This is a known issue in the following versions:

  • RSA Identity Governance & Lifecycle 7.1.1
  • RSA Identity Governance & Lifecycle 7.2.0
  • RSA Identity Governance & Lifecycle 7.2.1

This is caused by archiving canceled and rejected Change Requests with certain legacy data in them. 

Resolution

This issue is resolved in the following versions:

  • RSA Identity Governance & Lifecycle 7.1.1 P12
  • RSA Identity Governance & Lifecycle 7.2.0 P07
  • RSA Identity Governance & Lifecycle 7.2.1 P03

These versions contain an updated data migration package ACM-108570.sql that automatically removes references to legacy data in Change Requests so that Data Purging (as part of Data Archiving) can complete.

Workaround
If you are running into this issue and unable to apply the above patches, please contact RSA Customer Support for a workaround.
Notes
Note that ORA-01722 is generated for many different types of Data Archiving failures. The presence of this ORA code may mean you have this issue or another related issue.  Ensure the full stack trace matches exactly when using this KB article for guidance.

Related Articles

Trending Articles

Don't see what you're looking for?