Running out of disk space when using RMAN in RSA Identity Governance & Lifecycle

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
 

The disk drive where the RSA Identity Governance & Lifecycle Oracle database is located keeps running out of space.
 

On a software only RSA Identity Governance & Lifecycle implementation where the Oracle database is supplied by the customer and not RSA, customers may choose to run Recovery Manager (RMAN) to backup the database. When RMAN is enabled, archive redo logs are generated. If these logs are not monitored, they will cause the system to run out of disk space.
 

To resolve this problem, ask your DBA to monitor the disk space that is used by the archive redo logs and reconfigure the system as necessary to prevent the archived redo logs from using up all the available disk space.

Alternatively, consider replacing RMAN with the Oracle Data Pump utility as a backup and restore strategy. The RSA Identity Governance & Lifecycle application makes heavy use of temporary tables. This means the archived redo logs are logging create, update and delete statements of temporary data which can contribute to the large sizes of these files. Because the data is temporary, it is data that  does not need to be backed up.

See related RSA Knowledge Base Article 000038174 -- How to perform a database backup (export) and a database restore (import) in RSA Identity Governance & Lifecycle which explains the use of the Oracle Data Pump (import/export) utility on RSA-supplied databases. To use the Oracle Data Pump utility on a customer-supplied database, please contact your Oracle DBA.
 

Please note that the use of RMAN on an RSA Identity Governance & Lifecycle Oracle database can negatively impact performance. See RSA Knowledge Base Article 000037500 -- Severe performance degradation when running RMAN in RSA Identity Governance & Lifecycle for more information.