Skip to main content
ExLibris
  • Subscribe by RSS
    • Back
    Aleph
    Ex Libris Knowledge Center

    oracle_impdp_current_lib failing; Java call terminated

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    I've been working with our Oracle support to get the import/export using the Oracle data pump working.

    I've been using the smallest of our libraries, ABC12 as the test subject, exporting data from our production instance with oracle_expdp_current_lib and using oracle_impdp_current_lib in our Test instance to import it.

    After several false starts due to Oracle permission problems, we have the export working but the import is failing. See log file /exlibris/aleph/u18_2/alephe/scratch/abc12_impdp_oct14.log.

    We performed the commands in KB 16384-15683, but got this error while running the oracle_expdp_current_lib.sql:

    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining Scoring Engine options

    aleph_admin@ALEPH11> @oracle_expdp_current_lib.sql

    Java created.


    PL/SQL procedure successfully completed.


    PL/SQL procedure successfully completed.


    PL/SQL procedure successfully completed.


    Procedure created.


    Grant succeeded.

    begin
    *
    ERROR at line 1:
    ORA-29532: Java call terminated by uncaught Java exception: java.lang.SecurityException: policy table update SYS:java.io.FilePermission, /bin/chmod
    ORA-06512: at "SYS.DBMS_JAVA", line 313


    We ran the oracle_impdp_current_lib for ABC12 again and got these messages:

    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at "SYS.UTL_FILE", line 475
    ORA-29283: invalid file operation

    Resolution:
    The directory /exlibris/aleph/u18_2/nov12/files/dpdir lacked the 'w' privlege for 'all' which prevented the Oracle user from writing a log file to it.

    We changed it -- as described in the article, oracle_impdp_aleph_libs: invalid file operation ... at "SYS.UTL_FILE",  and re-ran the import, which then succeeded.

    • Article last edited: 10/8/2013