IBM Support

JR34042: RECORD REPORTED AS REJECTED WHEN IT WAS NOT REJECTED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The user has configured Oracle Connector stage to load data to
    the database in bulk-load mode. The user has also configured a
    reject link on the stage through which to send the records that
    could not be loaded. One of the input records fails to load but
    is also not rejected because the reason for which it failed was
    not included in the list of conditions specified for the reject
    link. The record causes the job to fail as expected but the
    problem is that this record is counted towards the total number
    of rejected records reported in the job log.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of Oracle Connector who are writing data to Oracle table
    in bulk load mode and have reject link defined for the
    connectorstage.
    ****************************************************************
    PROBLEM DESCRIPTION:
    The connector would report record as rejected even if the
    recordwas not actually sent down the reject link. This would
    happen incases when the reject link was defined for the
    connector stage, the connector would write data to the target
    table in bulk load mode, and the record would fail to load due
    to an error that    was not included in the reject conditions
    specified for the     reject link.
    ****************************************************************
    RECOMMENDATION:
    Install Connector Rollup Patch 2 (CCRP2)
    This change is included in 8.1 Fix Pack 1.
    ****************************************************************
    

Problem conclusion

  • The code was fixed not to include the record that caused the
    jobto abort towards the total count of records that were
    rejected  by the connector.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR34042

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-08-18

  • Closed date

    2009-09-28

  • Last modified date

    2009-12-15

  • 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

  • R810 PSN

       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":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 December 2009