"Unable to open the log file" error from oracle_expdp_aleph_libs

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Product: Aleph
Product Version: 20, 21, 22, 23
Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

Description:
We tried to run oracle_expdp_aleph_libs, as mentioned in the How To From Support document on copying data from one Aleph library to another, but it only dumped the demo libraries, not our ABCxx ones. See the log file on our PROD server, $alephe_scratch/oracle_expdp_aleph_libs.20100219.log for error messages. The error messages include these:

Directory ABC01_DIR already created
Export library is ABC01
rm: No match.

Export: Release 11.1.0.7.0 - Production on Friday, 19 February, 2010 13:45:46

Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-39002: invalid operation
ORA-39070: Unable to open the log file.
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283: invalid file operation

Resolution:
The problem that you encountered was apparently due to a previous run of some kind of export process from v.16 of Aleph. When the export process runs, it first has to create a DIRECTORY object in Oracle. The DIRECTORY object tells the export process where to put its output files and log files. There is usually no need to create an Oracle DIRECTORY each time the export process is run; if one is already there, it just uses it. In your case, the DIRECTORY objects for ABC01, 10, 30, 50 and 60 were already created, so the process tried to use them. Unfortunately, they seem to have come from a previous run of the export, so they were set to the wrong path. For example, ABC01_DIR was set to this path:

/exlibris/aleph/upgrade_express_1901_2001/data/a16_1/abc01/files/dpdir

I was able to fix this by going into Oracle as the ALEPH_ADMIN user and correcting the names with a command like this:

create or replace directory ABC01_DIR as '/exlibris/aleph/u20_2/abc01/files/dpdir';

Now that these DIRECTORY objects have the right paths, your export process should run smoothly.

NOTE: If the create_customer_data step fails with "invalid operation" messages even though the DIRECTORY objects *do* have the correct paths, consult Article: "UE export (create_customer_data): "invalid operation ...Unable to open the log" (KB 16384-47986).

Article last edited: 12-Mar-2016