This is a known issue in the following versions when using Oracle RAC (Real Application Clusters):
 

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

This issue may occur intermittently when using Oracle RAC as the database.  A failure may occur when creating a new Data Archive if the internal unique identifier for that archive is obtained from a secondary RAC node.  When there is a Suspended Archive in the list the Create button should be disabled and only the Delete and Resume buttons should be enabled.  The top item in the list of Data Archives should always be the most recent Data Archive, and this is the only Data Archive that may have the Archive Status of Suspended.  RSA Identity Governance & Lifecycle incorrectly orders the most recent Data Archive event by a sequence number instead of the date and this may sometimes cause the most recent item to be the second item in the list.  This may incorrectly disable the Delete and Resume button for the Suspended Archive. 

1. This issue can be prevented by making changes to the Oracle SEQUENCE.  Contact RSA Customer Support and quote this KB article for more information.
2. If you have any Data Archive runs in Suspended state that cannot be Resumed, contact RSA Customer Support and quote this KB article for a cleanup script to move these items to deleted.

This issue may be mitigated by avoiding Data Archiving that results in an Archive status of Suspended.

• Reduce the Date Range so that the Data Archive can be completed in the Maximum Run time or increase the Maximum Run time to match the Date Range.