Upgrade Express: ".. unable to obtain file status... No such file or directory"

• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
We are trying to import our v22 data to v23. We run upgrade_util   "2. Install customer data".  It doesn't work, and the error messages in the log are:
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31640: unable to open dump file "/exlibris/aleph/upgrade_express_2201_2301/data/a22_1/xxx01/files/dpdir/xxx0101.dmp" for read
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

Resolution:

The install_utree proc takes the /exlibris/aleph/upgrade_express_2201_2301/data/a22_1.tar.gz file and unzips/untars it, generating an       /exlibris/aleph/upgrade_express_2201_2301/data/a22_1/xxxnn/files/dpdir/ directory for each library which has been exported.  You should see the following line near the beginning of the log:

  Found ./data/a22_1/xxx01/files/dpdir - Processing...

where xxx01 is the first exported library.

The "Unable to open dump file /exlibris/aleph/upgrade_express_2201_2301/data/a22_1/xxx01/files/dpdir/xxx101.dmp" ... "No such file or directory" messages indicate that it was unable to find this directory/file.  

Check the /aleph/upgrade_express_2201_2301/data/a22_1/xxx01/files/dpdir/ directory and see what's there. If it's empty or there is no xxx0101.dmp file in it, then there must have been a problem with the export.

Note that you should be seeing "/exlibris/aleph/upgrade_express_2201_2301/data/a22_1/".  Though this is on the v23 target instance, the file was created on the v22 source instance.  And the name seen here should be "a22_1" *not* "a23_1".  

If the above all seem OK, then do the following:

> su - oracle 
> sqlplus / as sysdba
SQL> select DIRECTORY_NAME,DIRECTORY_PATH from dba_directories where DIRECTORY_NAME LIKE 'XXX%DIR';  <where "XXX" is your library code>

If the directories shown in this ./upgrade_express_2201_2301/data/ path are "a23_1", that's wrong.  If the export was done on v22, they should be "a22_1".  It may be that they were somehow incorrectly changed.  {The problem may have been a result of trying upgrade_util option 9 (transfer data between servers)...}  Try correcting them to "a22_1".