IBM Support

IT31380: REMOVE ERROR MESSAGES FROM DB2DIAG.LOG FOR ORACLE WRAPPER WHEN SQL0803N ERROR IS RECEIVED

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

  • When applications violate table constraints(i.e. insert
    duplicate data which violates an unique index), SQL0803N will be
    reported.  As for SQL0803N error, given it is an application
    error, so it only logged when diaglevel is 4.
    
    But if the target is an oracle nickname, the application will
    receive SQL0803N error, additionally the following 2 error
    messages are logged in db2diag.log:
    
    == ERROR 1 ==
    2019-12-19-14.00.02.811984+480 E1957A562            LEVEL: Error
    PID     : 32571518             TID : 3085           PROC :
    db2fmp (C) 0
    INSTANCE: db2inst1               NODE : 000
    HOSTNAME: tsthost
    EDUID   : 3085                 EDUNAME: db2fmp (C) 0
    FUNCTION: DB2 UDB, net8 wrapper, Net8_Statement::error_report,
    probe:60
    DATA #1 : String, 28 bytes
    Oracle Error - Current User
    DATA #2 : String with size, 6 bytes
    db2inst1
    DATA #3 : String, 22 bytes
    Oracle Error Received
    DATA #4 : String, 63 bytes
    ORA-00001: unique constraint (TIGER.UNIQIDX) violated
    
    == ERROR 2 ==
    2019-12-19-14.00.02.812301+480 I2520A462            LEVEL: Error
    PID     : 32571518             TID : 3085           PROC :
    db2fmp (C) 0
    INSTANCE: db2inst1               NODE : 000
    HOSTNAME: tsthost
    EDUID   : 3085                 EDUNAME: db2fmp (C) 0
    FUNCTION: DB2 UDB, Query Gateway, sqlqg_fedstp_hook, probe:40
    MESSAGE : Unexpected error returned from outer RC=
    DATA #1 : Hexdump, 4 bytes
    0x00000001120F9D30 : 8026 0160
    .&.`
    
    With this fix of this APAR,  ERROR 1 will only be logged when
    diaglevel is 4; ERROR 2 will be removed from db2diag.log.
    

Local fix

  • Prevent operations which may cause SQL0803N from application
    side.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * n/a                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 for LUW V11.1 Mod4 Fixpack6 or later.         *
    ****************************************************************
    

Problem conclusion

  • This problem is firstly fixed on V11.1 Mod4 Fixpack6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT31380

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-12-24

  • Closed date

    2021-03-21

  • Last modified date

    2021-03-21

  • 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

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1"}]

Document Information

Modified date:
22 March 2021