Skip to main content
Ex Libris Knowledge Center

Oracle Data Pump doesn't work in UE Create Customer Data step (or otherwise)

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

Problem Symptoms:
[NOTE: If the problem occurs on an import, such as the UE Install Customer Data, see #3 in Additional Information below.]

1. Though the Upgrade Express ./logs/log/main.log shows:

Start Create customer data at ...
yyyy-mm-dd hh:mm:ss Step create_customer_data - OK

the ./create_customer_data.log has, for each library, only:

Step begin create_customer_data
Archiving Oracle and Unix data : xxxmm, xxxnn, etc.
creating tar file
<end>

that is, the

Starting util/oracle_exp_aleph_libs_a. conf_or_data: both
. . exported "XXX01"."Znn" ...
. . exported "XXX01"."Znnn" ...
<etc.>

lines which *should* appear between the "Archiving" and "creating tar file" steps are not present.

2. The Upgrade Express ./data/a20_1/xxxnn/files/dpdir/ directories lack the correct files.

3. The Upgrade Express ./create_customer_data.log *may* have:

start : Oracle export using DP . Libraries: xxxnn, yyynn, etc.
ERROR:
ORA-03114: not connected to ORACLE

CREATE OR REPLACE AND RESOLVE JAVA SOURCE NAMED "Host" AS
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel
<etc.>

4. The ./data/a20_1.tar.gz file is too small, for example, at a site with 260G of Oracle data it might be just 1G.

5. A test $aleph_proc/oracle_expdp_table run gets the following errors:

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

Cause:
Oracle Data Pump not working properly

1. because of pre-existing dpdir directories/files with permissions problems. (See "Resolution" below.)

2. the "CREATE OR REPLACE AND RESOLVE JAVA SOURCE NAMED "Host" AS" indicates that the JVM (Oracle Java Virtual Machine component) java_jit_enabled = 'true' is invalid. Aleph currently uses JVM only in the upgrade kit.

Resolution:
1. If the "CREATE OR REPLACE AND RESOLVE JAVA SOURCE NAMED 'Host' AS" message appears, set java_jit_enabled to 'false'

2. su to oracle and drop each library's XXXNN_DIR_UE directory:

a. sqlplus
b. connect /as sysdba
c. select * from all_directories;
d. drop directory XXXNN_DIR_UE; <where "XXXNN" is the library (xxx01, xxx50, etc.) >

3. in the Aleph u-tree, delete the dpdir directories in each library's $data_files:

a. > dlib xxxnn
b. > df1
c. > rm -rf dpdir

4. Re-run the upgrade_util create_customer_data process ( -> 2. Export customer data)

Additional Information

1. Ex Libris recommends setting java_jit_enabled to 'false' *only* if the "CREATE OR REPLACE ..." error is occurring.

2. See also KB 16384-64769 ( Procedure to automatically delete each library's ./files/dpdir directory

3. If the problem occurs on an oracle_impdp_aleph_libs proc IMPORT and the dpdir directories have already been populated, they should *not* be deleted.** See Article 000036726 oracle_impdp_aleph_libs: invalid file operation ... at "SYS.UTL_FILE  in that case.

4.. The export/import *could* be run without the Data Pump, but that takes five times as long and involves omitting the Keyword tables -- necessitating the running of the manage-01 Service (in v21).

5. See also Article 000034268  Size of .tar.gz file produced by Upgrade Express "Create Customer Data" step .
 

Category: System management


  • Article last edited: 2/24/2015