IBM Support

JR33888: REMOVE EXTRANEOUS PRIMARY KEY VIOLATION MESSAGES IN DIRECTOR LOG BY UPSERT METHOD OF ODBC CONNECTOR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Director log file gets flooded with warnings, two warnings every
    record updated. Message in the log file is:
    
    ODBC_Connector_1,0: [IIS-CONN-ODBC-000013] ODBC Info:  SQLSTATE
    = 23000: Native Error Code = 2,627: Msg = [IBM(DataDirect
    OEM)][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY
    KEY constraint 'PK__britinsurance__7F60ED59'. Cannot insert
    duplicate key in object 'dbo.testupsert'.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All Users of ODBC Common Connector to load data using the method
    "insert then update"
    ****************************************************************
    PROBLEM DESCRIPTION:
        When Upsert method of ODBC CC is used and there are some
    primary key violations in the
        records to be inserted, for each record, two log entries
    are made in Director
        Log which is making it huge and also the corresponding row
    information is not there.
        So the messages are not useful to the user.
        The logged messages will be in the following way:
    
    Msg1:
        ODBC_Connector_1,0: [IIS-CONN-ODBC-000013] ODBC Info:
    SQLSTATE = 23000: Native Error Code = 2,627:
        Msg = [Microsoft][SQL Server Native Client 10.0][SQL
    Server]Violation of PRIMARY KEY constraint
        'PK__testupse__3213663B5AEE82B9'. Cannot insert duplicate
    key in object 'dbo.testupsert'.
    
    Msg2:
        ODBC_Connector_1,0: [IIS-CONN-ODBC-000013] ODBC Info:
    SQLSTATE = 01000: Native Error Code = 3,621:
        Msg = [Microsoft][SQL Server Native Client 10.0][SQL
    Server]The statement has been terminated.
    
    ****************************************************************
    RECOMMENDATION:
    Apply this APAR.
    ****************************************************************
    

Problem conclusion

  • Code has been modified not to log these messages and
    suggest using Reject Link with RejectErrorCode
     and RejectErrorText fields which will log the reason
    along with the rejected row information.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR33888

  • 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-03

  • Closed date

    2009-08-12

  • Last modified date

    2009-08-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

  • 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:
12 August 2009