IBM Support

IT25952: DB2 V11.1: GETTING STMM DATABASE NAME IS NOT VALID MESSAGES IN DB2DIAG.LOG

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

  • 2018-07-30-13.20.19.555084-360 E3010603A3836 LEVEL: Warning
    PID : 7995728 TID : 59083 PROC : db2sysc 0
    INSTANCE: db2inst1 NODE : 000 DB : ***
    APPHDL : 0-58922 APPID: ***
    AUTHID : DB2INST1 HOSTNAME: ***
    EDUID : 59083 EDUNAME: db2agent (SAMPLE) 0
    FUNCTION: DB2 UDB, buffer pool services, sqlbFindPageInBPOrSim,
    probe:2006
    MESSAGE : ZRC=0x00000003=3
    SQL0003N The database name is not valid.
    
    DIA8003C The interrupt has been received.
    DATA #1 : String, 41 bytes
    Excessive retries while removing STMM BPD
    DATA #2 : unsigned integer, 4 bytes
    300
    DATA #3 : Buffer page descriptor, PD_TYPE_SQLB_BPD, 112 bytes
    Pagekey: {pool:4;obj:337;type:0} PPNum:51226
    objectPageNum: 0
    bucketGroupHashIndex: -1
    hashnext: 0x0000000000000000
    hashprev: 0x0000000000000000
    bpdLatch:
    
    SXLatch :etc....
    
    This does not affect the performance and/or functionality of
    your database.
    

Local fix

  • - Upgrade to v11.1m4fp4
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL using Self Tuning Memory                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * db2diag.log file is recording messages like:                 *
    * 2018-07-30-13.20.19.555084-360 E3010603A3836 LEVEL: Warning  *
    * PID : 7995728 TID : 59083 PROC : db2sysc 0                   *
    * INSTANCE: db2inst1 NODE : 000 DB : SAMPLE                    *
    * APPHDL : 0-58922 APPID: 192.168.1.1.46277.180731100134       *
    * AUTHID : DB2INST1 HOSTNAME: bugdbug                          *
    * EDUID : 59083 EDUNAME: db2agent (SAMPLE) 0                   *
    * FUNCTION: DB2 UDB, buffer pool services,                     *
    * sqlbFindPageInBPOrSim,                                       *
    * probe:2006                                                   *
    * MESSAGE : ZRC=0x00000003=3                                   *
    * SQL0003N The database name is not valid.                     *
    *                                                              *
    * DIA8003C The interrupt has been received.                    *
    * DATA #1 : String, 41 bytes                                   *
    * Excessive retries while removing STMM BPD                    *
    * DATA #2 : unsigned integer, 4 bytes                          *
    * 300                                                          *
    * DATA #3 : Buffer page descriptor, PD_TYPE_SQLB_BPD, 112      *
    * bytes                                                        *
    * Pagekey: {pool:4;obj:337;type:0} PPNum:51226                 *
    * objectPageNum: 0                                             *
    * bucketGroupHashIndex: -1                                     *
    * hashnext: 0x0000000000000000                                 *
    * hashprev: 0x0000000000000000                                 *
    * bpdLatch:                                                    *
    *                                                              *
    * SXLatch :etc....                                             *
    *                                                              *
    * This does not affect the performance and/or functionality of *
    * your database, other than STMM may be a bit slower to tune   *
    * memory.                                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 11.1.4                                *
    ****************************************************************
    

Problem conclusion

  • Upgrade to DB2 Version 11.1.4
    

Temporary fix

  • To stop the error you could update the diaglevel to 2 but this
    will also reduce other useful information that may be written to
    the db2diag.log file at diaglevel 3
    ie db2 update dbm cfg using diaglevel 2
    

Comments

APAR Information

  • APAR number

    IT25952

  • 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

    2018-08-13

  • Closed date

    2019-06-03

  • Last modified date

    2019-06-03

  • 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

  • RB10 PSN

       UP

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

Document Information

Modified date:
03 June 2019