UE export (create_customer_data): "invalid operation ...Unable to open the log"

• Article Type: General
• Product: Aleph
• Product Version: 21
• Relevant for Installation Type: Dedicated-Direct; Direct; Local;

After correcting the problem described in Article 000039941 ("ORA-01187 cannot read from file 201 because it failed verification tests..temp01"), we were getting the following error for each library in running the Upgrade Express 20-21 export (create_customer_data):

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:
Note: The following deletions should be performed when the problem is seen in the *export*. In the import, if the data was produced by oracle_expdp_aleph_libs (rather than Upgrade Express) and placed in the dpdir directories on this target instance, these dpdir directories need to exist and should not be deleted

We deleted each library's ./files/dpdir directory. (These directories were empty, .)

> dlib abc50
> df1
> rmdir dpdir

If the directory is not empty, then the following needs to be used: > rm -fr dpdir

The following command can be used to remove the ./files/dpdir directory in all libraries in this Aleph instance with a single command:

rm -fr /exlibris/aleph/u2n_1/*/files/dpdir

[where "u2n_1" is the value of ${ALEPH_VERSION}_${ALEPH_COPY} in this Aleph instance]
(It's possible that the problem had to do with the file permissions. I didn't really check that. But deleting these empty directories definitely fixed the problem.)

Note: We found that one library, the $usr_library abc00, was not exported. It had the problem described in Article 000041904 ("Data Pump: job does not exist; unable to create master table; name is already used ..."). We had to do the DROP TABLE described in that Article and rerun the create_cusotmer_data for abc00.

See also, Article 000045252, "Oracle Data Pump doesn't work in UE Create Customer Data step (or otherwise)"