Severe performance degradation when running RMAN in RSA Identity Governance & Lifecycle

[#1]

Article Number

000037500

Applies To

RSA Product Set: RSA Identity Governance & Lifecycle
RSA Product/Service Type: Enterprise Software
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
 

Issue

On a software only RSA Identity Governance & Lifecycle implementation where the database is supplied by the customer and not RSA, customers may choose to run Recovery Manager (RMAN) to backup the database. When RMAN is running on an active database, severe performance degradation may occur.
 

Cause

Running RMAN on an active database can cause severe performance degradation. It can potentially deadlock the entire database. Because of the heavy reads on the database by RMAN, there can be row lock contention across multiple tables and indices. In addition, both database I/O and file system I/O can be affected.
 

Resolution

To avoid performance issues while running RMAN:

1. Schedule RMAN backup outside of peak hours.
2. Stop RSA Identity Governance & Lifecycle during RMAN backup.
3. Consider replacing RMAN with the Oracle Data Pump utility as a backup and restore strategy.

Notes

See related RSA Knowledge Base Article 000038563 -- Running out of disk space when using RMAN in RSA Identity Governance & Lifecycle for information on the impact RMAN can have on disk space usage.