Running out of disk space when using RMAN in RSA Identity Governance & Lifecycle
Originally Published: 2020-03-12
Article Number
Applies To
RSA Product/Service Type: Enterprise Software
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
Issue
Cause
Resolution
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.
Notes
Related Articles
Running out of disk space on KCA system 25Number of Views Examining the Disk Space Usage on Authentication Manager 8.x 732Number of Views How to enable Verbose logging without consuming your Disk Space on RSA Authentication Manager 8.x 215Number of Views RSA Authentication Manager 8.x: Large Disk Space Used by Logs 568Number of Views RSA Authentication Manager 8.x requires more disk space 1.78KNumber of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?