RSA Identity Governance & Lifecycle requests stuck in an open state due to datafile resizing
Originally Published: 2018-08-30
Last Modified: 2022-06-20
Article Number
000041262
Applies To
RSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.0.x 7.1
 
Issue
New Change Requests remain in an Open state until ACM is restarted at which point they proceed to progress.
Cause
There can be multiple causes for this scenario. This article is about the following root cause:

A resize operation on datafiles was executed at an earlier time, and the files were resized to a smaller size: 
Fri Aug 10 07:43:12 2018 alter database datafile '/data01/AVDBP/datafile/o1_mf_data_50m_03.dbf' resize 13000m 
Resize operation completed for file# 26, old size 17387520K, new size 13312000K 
Completed: alter database datafile '/data01/AVDBP/datafile/o1_mf_data_50m_03.dbf' resize 13000m

Subsequently, ACM and Oracle needed to increase the size of some of those files again: 
Fri Aug 10 07:46:59 2018
Resize operation completed for file# 26, old size 13312000K, new size 13414400K
Resize operation completed for file# 26, old size 13414400K, new size 13516800K
Resize operation completed for file# 26, old size 13516800K, new size 13619200K

Since the datafiles were needed for ACM operations, and  file extension was constantly running, no progress on workflows could be made and the requests became stuck in the 'Open' state during that period.
Resolution
  • Avoid datafile resize operations during active business hours.
  • Avoid resizing datafiles down to inappropriate sizes.
  • Upgrade to later versions like 7.0.2 and 7.1 where data pruning operations on ACM internal tables are automated and scheduled to avoid the need for database file resizing.

If you are concerned about database growth, please open a case with RSA Support.

Related Articles

Trending Articles

Don't see what you're looking for?