000039087 - Database Import fails with 'ORA-39001: invalid argument value' if AVEKSA_HOME contains an '@' symbol in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jul 2, 2020Last modified by RSA Customer Support Employee on Jul 2, 2020
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000039087
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.2.0
 
IssueDatabase import fails with the following error:

cd /home/oracle/A@veksa/database/DBA/AVDB/scripts
./AVDB_Import_AVUSER.sh -t _1

Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Advanced Analytics
and Real Application Testing options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31640: unable to open dump file "/home/oracle/A@veksa/AveksaExportImportDir/Export_AVDB_avuser_1.dmp" for read
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory

Additional information: 3


 
CauseThis is a known issue reported in engineering ticket ACM-104010.

This issue occurs if there is an @ in the installation directory defined by $AVEKSA_HOME. For example:
 
/home/oracle/A@veksa
 


Starting in RSA Identity Governance & Lifecycle 7.2.0, the AVEKSA_HOME installation directory may be defined as some value other than /home/oracle which allows the possibility that the installation directory could contain an @ symbol.


 
ResolutionThis issue is resolved in RSA Identity Governance & Lifecycle 7.2.0 P02.

The resolution is to disallow the @ sign and other special characters such as a space in the installation directory name when performing an installation.
 

Attachments

    Outcomes