Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. SQL*Loader-605: Non-data dependent ORACLE error occurred -- load discontinued

    SQL*Loader-605: Non-data dependent ORACLE error occurred -- load discontinued

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    • Article Type: General
    • Product: Aleph
    • Product Version: 16.02

    Description:
    The p_manage_01 job completed this morning. It's seems to have finished OK, but I see the following in the log:

    Commit point reached - logical record count 14853242
    Commit point reached - logical record count 14853342
    Commit point reached - logical reSQL*Loader-605: Non-data dependent ORACLE erro
    r occurred -- load discontinued.

    cord count 14853442
    Commit point reached - logical record count 14853542
    Commit point reached - logical record count 14853642

    And later:

    mv /exlibris/aleph/u16_3/odn07/files/z98.seq /exlibris/aleph/u16_3/odn07/files/
    z98.seq.variable
    fixed_size 40
    Username:SQL*Loader-605: Non-data dependent ORACLE error occurred -- load disco
    ntinued.

    SQL*Loader: Release 9.2.0.3.0 - Production on Thu Apr 3 07:20:08 2008

    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

    Commit point reached - logical record count 100
    Commit point reached - logical record count 200

    Resolution:
    As described in KB 16384-2561, this "non-data-dependent ORACLE error" can be due to a lack of space. The job halts. If space is added, it continues. It seems that this is what happened since we see that the job *did* continue, and seems to have finished successfully.

    It may be that the tablespace is automatically extensible: this message occurred and after it automatically added the space, it continued.

    You can check the alert.log -- which, in this case, is on the $ORA_HOST server. That may show more.

    Though it's not always fool-proof, all of the p_manage_01_e.cycles lines have "+ +", indicating success.


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • SQL*Loader-510: Physical record in data file is longer than the maximum
      • SRU - DNB MABXML to Aleph
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 16.02
      2. contype:kba
      3. Prod:Aleph
      4. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved