How to determine the size of a backup before creating one in RSA Identity Governance & Lifecycle
Originally Published: 2014-10-20
Article Number
Applies To
Issue
*Also known as the database backup, database dump or datapump export file.
Resolution
expdp avuser/<password> directory=Aveksa_ExportImport_Directory ESTIMATE=blocks estimate_only=y logfile=log.log
For more information,
- expdp - Oracle datapump utility which is used for the backup.
- avuser/<password> - Credentials for database access
- directory=Aveksa_ExportImport_Directory - Output directory.
This directory is specified when the database is created and points to/home/oracle/AveksaExportImportDir.
To verify the name of the backup directory, execute "select * from all_directories" as 'avuser' in SQL*Plus.
To verify the name of the backup directory, execute "select * from all_directories" as 'avuser' in SQL*Plus.
- ESTIMATE=blocks estimate_only=y
Do not do the actual backup. Just report the size that the backup will be.
- logfile=log.log - File name that contains the output that you see in the terminal window.
An example session is shown here:
Notice that no backup file is created.
Related Articles
Measuring RSA AA Web Services performance 27Number of Views How to increase the logging of KCA on Solaris 5Number of Views Error message on RSA Identity Management and Governance workflow: requires at least one valid outbound transition path but… 160Number of Views Remote Backups not working with Authentication Manager 8.2 10Number of Views Why and how to increase Oracle redo log size using RSA Identity Governance & Lifecycle 318Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?