Database Import fails with 'ORA-39001: invalid argument value' if AVEKSA_HOME contains an '@' symbol in RSA Identity Governance & Lifecycle
Originally Published: 2020-07-02
Article Number
Applies To
RSA Version/Condition: 7.2.0
Issue
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
Cause
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.
Resolution
The resolution is to disallow the @ sign and other special characters such as a space in the installation directory name when performing an installation.
Related Articles
How to generate a report of registered users in RSA Authentication Manager 8.x database Number of Views Service cannot start after Patch upgrade or reboot Number of Views How to generate a report from CLI for the Last Updated Auto Reg status for Agents with Auto Registration enabled in RSA Au… Number of Views Authentication Manager rsaserv Fails with "log4j:ERROR Could not read configuration file" Number of Views Cloud Access Service and Authenticators Historical Release Notes (July 2025 - January 2025) Number of Views
Don't see what you're looking for?
