Running out of disk space when using RMAN in RSA Identity Governance & Lifecycle
Originally Published: 2020-03-12
Last Modified: 2023-11-30
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
How to enable Verbose logging without consuming your Disk Space on RSA Authentication Manager 8.x 231Number of Views Examining the Disk Space Usage on Authentication Manager 8.x 775Number of Views Running out of disk space on KCA system 27Number of Views RSA Authentication Manager 8.x: Large Disk Space Used by Logs 602Number of Views RSA Authentication Manager 8.x requires more disk space 1.85KNumber of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?