IBM Support

IT31613: UNNECESSARY SQLO_BAD_USER LOGGING INTO DB2DIAG.LOG

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You may encountering unnecessary SQLO_BAD_USER in db2diag.log
    like the following:
    
    2020-01-17-14.34.00.480708+060 I5819328E668         LEVEL: Error
    PID    : 13800               TID : 47679098840832 PROC : db2sysc
    0
    INSTANCE: db2inst1              NODE : 000           DB  :
    SAMPLE
    APPHDL : 0-630               APPID: *LOCAL.db2t03.200117133407
    HOSTNAME: localhost
    EDUID  : 91                  EDUNAME: db2agent (SAMPLE) 0
    FUNCTION: DB2 UDB, oper system services,
    sqloGetUserAttribByName, probe:20
    MESSAGE : ZRC=0x800F006A=-2146500502=SQLO_BAD_USER "Bad User"
             DIA8117C Error with userid "".
    DATA #?1 : String, 40 bytes
    getpwnam failed: user name, system error
    DATA #?2 : String, 8 bytes
    user1
    DATA #?3 : signed integer, 4 bytes
    0
    
    The lastest v11.1 Fixpack 5 and v11.5 introduced extra logging
    which caused this issue.
    This APAR will reduce logging for this specific scenario.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All DB2 systems on all Linux, Unix and Windows platforms at  *
    * service level 11.1.4.5. Earlier releases of Db2 are not      *
    * affected                                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1.4.6                                      *
    ****************************************************************
    

Problem conclusion

  • The complete fix for this problem first appears in DB2 Version
    11.1.4.6 and all the subsequent Fix Packs.
    
    The fix will ensure that Db2 does not log SQLO_BAD_USER at Error
    level when it is an expected result from an OS function call.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT31613

  • 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

    2020-01-22

  • Closed date

    2021-03-11

  • Last modified date

    2021-03-11

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

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

    IT31615

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 May 2022