• Product: RSA Identity Governance & Lifecycle
• Version: 7.0.x, 7.1.x, 7.2.x
• Deployment Type: Hardware Appliance, Software Appliance (RSA-supplied Oracle database only)
• Component: Oracle Database (RSA-supplied)
• Platform: Linux

You may need to back up or restore the RSA-supplied Oracle database in the following situations:

• Performing a scheduled or pre-upgrade database backup.
• Migrating the database to a new or rebuilt server.
• Recovering from a system failure or data corruption event.
• Reducing database fragmentation as part of routine maintenance (export followed by import reclaims all unused space).

This article covers three methods: RSA-provided shell scripts, alias commands at the command line, and the backup utility in the application UI. All three methods apply to RSA-supplied Oracle databases on RSA Identity Governance & Lifecycle hardware and software appliances only.

CAUTION: If you are restoring the database to a different or rebuilt server, you must also back up and restore the Oracle encryption key files located in /home/oracle/security. Failing to restore these files alongside the database will result in a corrupt or unusable restore.

NOTE — Non-RSA-Provided Databases: If your Oracle database was not supplied by RSA, do not use this article. Contact your Oracle DBA for backup and restore procedures.

NOTE — AWS RDS: If you are running RSA Identity Governance & Lifecycle on RDS on AWS, do not use this article. Refer to the AWS documentation for RDS backup and restore facilities.

Prerequisites:

• Linux shell access to the RSA IGL appliance as the oracle user.
• Sufficient disk space in /home/oracle/AveksaExportImportDir to store the .dmp export file.
• The RSA IGL application must be stopped before running any export or import (acm stop).
• For UI-based backups (Method 3): access to the RSA IGL Admin UI with system administrator privileges.

Method 1: RSA-Provided Shell Scripts

Back Up (Export)

1. Log in to the appliance as the oracle user.
2. Stop the RSA IGL application.

   acm stop

3. Navigate to the scripts directory.

   cd /home/oracle/database/DBA/AVDB/scripts

4. Run the export script. Replace <tag> with a label of your choice (e.g., _YYYYMMDD).

   ./AVDB_Export_AVUSER.sh -t <tag>

5. Verification: Confirm the export file was created successfully.

   ls /home/oracle/AveksaExportImportDir/Export_AVDB_avuser<tag>.dmp

   Expected result: The .dmp file is present and its file size is greater than zero. If errors occurred, review: /home/oracle/AveksaExportImportDir/Export_AVDB_avuser-{YYYY-MM-DD-##-##}.log

Restore (Import)

CAUTION: If restoring to a different or rebuilt server, restore the encryption key files from /home/oracle/security before proceeding. See the Prerequisites in the Issue section.

1. Log in to the appliance as the oracle user.
2. Stop the RSA IGL application.

   acm stop

3. Navigate to the scripts directory.

   cd /home/oracle/database/DBA/AVDB/scripts

4. Run the import script using the same tag used during the export.

   ./AVDB_Import_AVUSER.sh -t <tag>

5. Start the RSA IGL application.

   acm start

6. Verification: Log in to the RSA IGL UI and confirm the application is functioning normally. If errors occurred, review: /home/oracle/AveksaExportImportDir/Import_AVDB_avuser.log

Method 2: Alias Commands

NOTE: Method 2 is functionally identical to Method 1. The alias commands are pre-configured shortcuts that call the same underlying scripts. The alias definitions are:

alias avdbexport='/home/oracle/database/DBA/AVDB/scripts/AVDB_Export_AVUSER.sh'
alias avdbimport='/home/oracle/database/DBA/AVDB/scripts/AVDB_Import_AVUSER.sh'

Back Up (Export)

1. Log in to the appliance as the oracle user.
2. Stop the RSA IGL application.

   acm stop

3. Run the export alias. Replace <tag> with a label of your choice (e.g., _YYYYMMDD).

   avdbexport -t <tag>

4. Verification: Confirm the export file was created successfully.

   ls /home/oracle/AveksaExportImportDir/Export_AVDB_avuser<tag>.dmp

   ✅ Expected result: The .dmp file is present and its file size is greater than zero. If errors occurred, review: /home/oracle/AveksaExportImportDir/Export_AVDB_avuser-{YYYY-MM-DD-##-##}.log

Restore (Import)

CAUTION: If restoring to a different or rebuilt server, restore the encryption key files from /home/oracle/security before proceeding.

1. Log in to the appliance as the oracle user.
2. Stop the RSA IGL application.

   acm stop

3. Run the import alias using the same tag used during the export.

   avdbimport -t <tag>

4. Start the RSA IGL application.

   acm start

5. Verification: Log in to the RSA IGL UI and confirm the application is functioning normally. If errors occurred, review: /home/oracle/AveksaExportImportDir/Import_AVDB_avuser.log

Method 3: UI Backup Utility

NOTE: This method is available on RSA Identity Governance & Lifecycle hardware and software appliances only. The backup can be performed while the system is online — no downtime is required for the backup step. However, the restore (import) still requires the application to be stopped.

CAUTION: If users are actively accessing the database during the backup, there is a risk to the integrity of the backup file due to database contention. RSA recommends scheduling UI backups during the quietest period, or enabling Maintenance Mode before running the backup (Admin > System > Maintenance > Edit > Maintenance Mode: On).

Back Up (Export via UI)

1. Log in to the RSA IGL UI as a system administrator.
2. Navigate to Admin > System > Backup > Edit.
3. Set Scheduled to Yes and save. The system will create a backup file in the following format:

   /home/oracle/AveksaExportImportDir/Export_AVDB_avuserYYYY-MM-DD-##-##-##.dmp

   For example: Export_AVDB_avuser2024-06-15-02-00-00.dmp

4. Verification: Confirm the export file was created in /home/oracle/AveksaExportImportDir. Note the exact filename — you will need the timestamp portion to run the import.

Restore (Import)

CAUTION: If restoring to a different or rebuilt server, restore the encryption key files from /home/oracle/security before proceeding.

1. Log in to the appliance as the oracle user.
2. Stop the RSA IGL application.

   acm stop

3. Run the import using the timestamp from the UI-generated backup filename. Replace the timestamp with the one from your actual backup file.

   Using the alias:

   avdbimport -t 2024-06-15-02-00-00

   Or using the script directly:

   cd /home/oracle/database/DBA/AVDB/scripts
   ./AVDB_Import_AVUSER.sh -t 2024-06-15-02-00-00

4. Start the RSA IGL application.

   acm start

5. Verification: Log in to the RSA IGL UI and confirm the application is functioning normally. If errors occurred, review: /home/oracle/AveksaExportImportDir/Import_AVDB_avuser.log