000028218 - AVUSER backup export script fails using RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Sep 1, 2016Last modified by RSA Customer Support on Jan 29, 2019
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000028218
Applies ToRSA Product Set:  RSA Identity Governance & Lifecycle
IssueAfter a failed attempt to backup, a new backup fails with the following errors: 

ORA-31626: job does not exist
ORA-31633: unable to create master table "AVUSER.AVDB_EXPORT_AVUSER"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 863
ORA-00955: name is already used by an existing object

Alternatively, the error shown here may be displayed:

- [Ljava.lang.StackTraceElement;@382839bd
0 [main] ERROR com.aveksa.cli.BaseExecCLIModule - [Ljava.lang.StackTraceElement;@382839bd

CauseThis error is usually due to a previous failed export, when running the export script either from the UI or from the command line.  A successful export deletes the temporary tables AVDB_EXPORT_AVUSER and/or AVDB_Export_AVUSER.job.  These temporary tables may still exist on a failed export.  If either of these tables exist when the script is executed, this will result in the Oracle errors or stack trace noted above.
ResolutionThere are two preferred options to correct this error.  These are by either removing or renaming this temporary table.  Both will work, but removing the table is a better option, as this more closely follows the correct successful behavior of the export script.

Login to the AVDB ACM database as AVUSER, using a tool such as SQL*Plus or SQL Developer and run the following SQL command to drop the temporary AVDB_EXPORT_AVUSER table that the export script creates.  In some versions you may also have an AVDB_Export_AVUSER.job table that will also need to be dropped.  After these commands are executed, repeat the export.

$ sqlplus avuser/secret
SQL> exit

Note that the AVDB_Export_AVUSER.job table menitoned in line 3 does not always exist.

WorkaroundAlternatively, prior to version 7.0.0, the error can also be bypassed by commenting out a line in the export file Export_AVDB_avuser.sh.

Creating a backup of the original file is always recommended before any edits are done. 

Once a successful backup is run, this temporary edit is no longer necessary and the original file can be restored. 

Execute the steps below while logged in as the Unix oracle user.
  1. Change directory to /home/oracle/database/DBA/AVDB/scripts.

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

  1. Create a backup of the file to be edited.

cp Export_AVDB_avuser.sh  Export_AVDB_avuser.org

  1. Edit the file named Export_AVDB_avuser.sh and comment out the line shown below by locating and adding a # in column 1.

echo Job_Name=${EXP_JOB_NAME}        >> ${EXP_PAR_FILE}


#echo Job_Name=${EXP_JOB_NAME}        >> ${EXP_PAR_FILE}

  1. Repeat the export.
  • The example shown in the Resolution section of this article makes use of SQL*Plus.
  • The password shown is the default. If this password is different on the system in question, use the appropriate password for the AVUSER account.