IBM Support

JR57033: THE DB2_CC WRONG CONVERTS PARTITION NUMBER, WHEN CLIENT AND SERVER HAS A DIFFERENT ORDER OF BITS.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • the DB2_CC wrong converts partition number, when client and
    server has a different order of bits.
    

Local fix

  • unknown
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    DB2 connector users running db2 servers on systems with
    different endiannes than information server system.
    ****************************************************************
    PROBLEM DESCRIPTION:
    When DataStage and DB2 server are set up on systems with
    different endianness, data could be sent to wrong DB2
    partitions.
    Partition numbers are not correctly converted between DB2 server
    and DataStage endianness (big-endian vs little-endian).
    
    The problem can be detected when:
    - most or all rows are sent to partition 0 - in this case no
    error is raised, but data is not distributed evenly between
    partitions
    - data rows are sent to random (very large or negative)
    partition number - this results in job error
    It shows as one of the messages in the DataStage job logs:
    DEBUG: Row 51 will be sent to node 0 partition 914.
    DEBUG: Row 15 will be sent to node 6 619 251 partition 911.
    DEBUG: Row 32 will be sent to node 0 partition -28,413.
    
    
    Customer reported following error when they used partition
    numbers 911-914:
    
    TRACE: CC_DB2_MSG_EXIT_METHOD(int), IIS-CONN-DB2-00275(ext)
    TRACE: <-  CC_DB2Partitioner::prepare
    TRACE: CC_DB2_MSG_ENTER_METHOD(int), IIS-CONN-DB2-00274(ext)
    TRACE: -> CC_DB2Partitioner::partitionOneTopLevelDataItem
    DEBUG: CC_DB2_MSG_ROW_SENT_TO_NODE(int), IIS-CONN-DB2-00375(ext)
    DEBUG: La ligne 1 sera envoyée au noeud 7 536 748 de la
    partition 911.
    TRACE: CC_DB2_MSG_EXIT_METHOD(int), IIS-CONN-DB2-00275(ext)
    TRACE: <-  CC_DB2Partitioner::partitionOneTopLevelDataItem
    ****************************************************************
    RECOMMENDATION:
    Install Patch JR57033
    ****************************************************************
    

Problem conclusion

  • DB2 connector partitioning code has been fixed with JR57033
    patch.
    

Temporary fix

  • N/A
    

Comments

APAR Information

  • APAR number

    JR57033

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    B50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-21

  • Closed date

    2016-12-12

  • Last modified date

    2016-12-12

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

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

Fix information

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • RB50 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 December 2016