IBM Support

IC77802: DB2 ALTER TABLESPACE REDUCE with invalid size produces db2diag.log error messages

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If a user issues
    
    DB2 ALTER TABLESPACE REDUCE <size>
    
    and specifies a size that exceeds the tablespace's available
    pages, but below the tablespace's total pages, then the
    following
    db2diag.log messages might appear (note that the command might
    return without error):
    
    2011-07-28-12.43.56.787512-240 E779929E520         LEVEL: Info
    PID     : 21379                TID  : 47684874398016PROC :
    db2sysc
    INSTANCE: dbinstance             NODE : 000          DB   :
    TESTDB
    APPHDL  : 0-51                 APPID: *LOCAL.DB2.110728164356
    AUTHID  : USER
    EDUID   : 98                   EDUNAME: db2agent (TESTDB)
    FUNCTION: DB2 UDB, buffer pool services, sqlb_locate_extent,
    probe:232
    MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic
    error detected"
              DIA8501C A buffer pool logic error has occurred.
    DATA #1 : <preformatted>
    
    2011-07-28-12.43.56.787512-240 E779929E520         LEVEL: Info
    PID     : 21379                TID  : 47684874398016PROC :
    db2sysc
    INSTANCE: dbinstance             NODE : 000          DB   :
    TESTDB
    APPHDL  : 0-51                 APPID: *LOCAL.DB2.110728164356
    AUTHID  : USER
    EDUID   : 98                   EDUNAME: db2agent (TESTDB)
    
    FUNCTION: DB2 UDB, buffer pool services,
    sqlbBuildContOpListForReduce, probe:10
    MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic
    error detected"
              DIA8501C A buffer pool logic error has occurred.
    
    2011-07-28-12.43.56.787512-240 E779929E520         LEVEL: Info
    PID     : 21379                TID  : 47684874398016PROC :
    db2sysc
    INSTANCE: dbinstance             NODE : 000          DB   :
    TESTDB
    APPHDL  : 0-51                 APPID: *LOCAL.DB2.110728164356
    AUTHID  : USER
    EDUID   : 98                   EDUNAME: db2agent (TESTDB)
    FUNCTION: DB2 UDB, buffer pool services, sqlbAlterPool, probe:70
    MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic
    error detected"
              DIA8501C A buffer pool logic error has occurred.
    
    2011-07-28-12.43.56.787512-240 E779929E520         LEVEL: Info
    PID     : 21379                TID  : 47684874398016PROC :
    db2sysc
    INSTANCE: dbinstance             NODE : 000          DB   :
    TESTDB
    APPHDL  : 0-51                 APPID: *LOCAL.DB2.110728164356
    AUTHID  : USER
    EDUID   : 98                   EDUNAME: db2agent (TESTDB)
    FUNCTION: DB2 UDB, buffer pool services, sqlbEMReduceContainers,
    probe:3608
    MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic
    error detected"
              DIA8501C A buffer pool logic error has occurred.
    DATA #1 : String, 14 bytes
    Error occurred
    
    2011-07-28-12.43.56.787512-240 E779929E520         LEVEL: Info
    PID     : 21379                TID  : 47684874398016PROC :
    db2sysc
    INSTANCE: dbinstance             NODE : 000          DB   :
    TESTDB
    APPHDL  : 0-51                 APPID: *LOCAL.DB2.110728164356
    AUTHID  : USER
    EDUID   : 98                   EDUNAME: db2agent (TESTDB)
    FUNCTION: DB2 UDB, buffer pool services, sqlbLockAndMoveExtents,
    probe:4439
    MESSAGE : ADM6008I  Extents within table space "DMS"  (ID "3")
    have been moved.
              Reason code = "0".
    
    Total pages and available pages are state info about a
    tablespace and they can have different meanings throughout the
    life of a tablespace.  The simplest scenario for this problem to
    occur would be a customer issuing ALTER to reduce the tablespace
    to 0 size, which is a very unlikely scenario.  However, it is
    also possible that the tablespace currently is in some state
    that causes the totalpages to be way bigger than the available,
    and customer only take notice of the total pages parameter and
    issue a reduce based on that, causing the problem to occur.
    

Local fix

  • Query the tablespace size and only reduce the tablespace to
    above the available pages
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See error description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Query the tablespace size and try to use a size that is      *
    * above the tablespace's available pages                       *
    ****************************************************************
    

Problem conclusion

  • fixed in v97 fp 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC77802

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-07-28

  • Closed date

    2012-01-17

  • Last modified date

    2012-01-17

  • 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

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC77802

Modified date: 17 January 2012