IBM Support

PI83614: SQL5105 RETURNED FROM BIGSQL QUERY AGAINST ORC TABLES CAUSED BY INDEX OUT OF BOUNDS EXCEPTION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The symptoms of this problem is the sqlcode SQL5105 that is
    given from the java reader as follows:
    SQL5105N  The statement failed because a Big SQL component
    encountered an
    error. Component receiving the error: "BigSQL IO". Component
    returning the
    error: "UNKNOWN". Log entry identifier: "[BSL-3-4b0fc5fa3]".
    SQLSTATE=58040
    Use the error log identifier string in the sql5105 error to map
    the error to the bigsql log.  For this problem, the bigsql log
    will capture the error detail showing that the cause was an
    index out of bounds error when processing an orc file like the
    following:
    java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
            at java.util.ArrayList.rangeCheck(ArrayList.java:664)
            at java.util.ArrayList.get(ArrayList.java:440)
            at
    java.util.Collections$UnmodifiableList.get(Collections.java:1320
    )
            at
    org.apache.orc.mapred.OrcInputFormat.parseInclude(OrcInputFormat
    .java:69)
            at
    com.ibm.biginsights.bigsql.dfsrw.orc.DfsOrcReader.getRecordReade
    r(DfsOrcReader.java:397)
            at
    com.ibm.biginsights.bigsql.dfsrw.orc.DfsOrcReader$ReaderWorker.r
    un(DfsOrcReader.java:266)
            at java.lang.Thread.run(Thread.java:785)
    If you look at the orc files for the table on hdfs, look for
    very small files (in the known case they were 49 bytes long).
    These small files are the cause of the problem.  These files
    are safe to ignore and do not contain data, but without this
    fix, the IO reader trips over them and fails.
    With this APAR, the IO reader can tolerate these files without
    failure.
    

Local fix

  • manually delete those small orc files from the hdfs path
    

Problem summary

  • See error description
    

Problem conclusion

  • The problem is fixed in Version 5.0.0.0 and later fix packs
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI83614

  • Reported component name

    INFO BIGINSIGHT

  • Reported component ID

    5725C0900

  • Reported release

    420

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-26

  • Closed date

    2018-03-01

  • Last modified date

    2018-03-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • Unknown
    

Fix information

  • Fixed component name

    INFO BIGINSIGHT

  • Fixed component ID

    5725C0900

Applicable component levels

  • R425 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCRJT","label":"IBM Db2 Big SQL"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"420","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
25 August 2020