IBM Support

JR31595: THE DB2DIAG.LOG WHICH SIZE WAS 138 MB,AND 3 STACK.BIN FILES WHIC H WERE 1 GB TOTAL WERE CREATED DURING RUNNING INFORSPHERE INFO

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The problem was found during running InforSphere Information
    Analyzer v8.1 SVT.
    During creating A column frequency report was created using the
    'Most Frequent Formats" option in InforSphere Information
    Analyzer v8.1 SVT,  Numerous "Unable to find donor to satisfy
    minSize constraint", and "A buffer pool logic error has
    occurred" messages were written to db2diag.log  db2diag.log
    was 138 MB, and 3 stack.bin files were created which were 1 GB
    total. If a customer runs frequent reports with large volumes
    of data, the system disk space could be consumed.
    This was tested on Windows 2003 SP2.  32 bit, 16-way machine,
    with 16 GB of RAM.  DB2 V9.5 FP2 was installed as part of the
    m7_17 bundle.
    ......................................
    2008-07-17-22.38.43.406000-420 I5480H451   LEVEL: Error
    PID : 23840         TID  : 29344   PROC :
    db2syscs.exe
    INSTANCE: DB2         NODE : 000
    EDUID : 29344         EDUNAME: db2pfchr (IADB) 0
    FUNCTION: DB2 UDB, buffer pool services,
    sqlbReadAndReleaseBlock, probe:110
    MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic
    error detected"
       DIA8501C A buffer pool logic error has occurred.
    2008-07-17-22.38.43.406000-420 I5933H451   LEVEL: Error
    PID : 23840         TID  : 22152   PROC :
    db2syscs.exe
    INSTANCE: DB2         NODE : 000
    EDUID : 22152         EDUNAME: db2pfchr (IADB) 0
    FUNCTION: DB2 UDB, buffer pool services,
    sqlbReadAndReleaseBlock, probe:110
    MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic
    error detected"
       DIA8501C A buffer pool logic error has occurred.
    2008-07-17-22.38.43.593000-420 I6386H448   LEVEL: Error
    PID : 23840         TID  : 29344   PROC :
    db2syscs.exe
    INSTANCE: DB2         NODE : 000
    EDUID : 29344         EDUNAME: db2pfchr (IADB) 0
    FUNCTION: DB2 UDB, buffer pool services,
    sqlbReadAndReleaseBlock, probe:110
    DATA #1 : String, 103 bytes
    Tablespace 3 (IADBSPACE) flags=3102
    HighWaterMark=751088ConOffset=34078720, startpage=1024,
    numPages=16
    2008-07-17-22.38.43.593000-420 I6836H448   LEVEL: Error
    PID : 23840         TID  : 22152   PROC :
    db2syscs.exe
    INSTANCE: DB2         NODE : 000
    EDUID : 22152         EDUNAME: db2pfchr (IADB) 0
    FUNCTION: DB2 UDB, buffer pool services,
    sqlbReadAndReleaseBlock, probe:110
    DATA #1 : String, 103 bytes
    Tablespace 3 (IADBSPACE) flags=3102
    HighWaterMark=751088ConOffset=39321600, startpage=1184,
    numPages=16
    .............................................................
    If you need more information, pls contact Carlene P
    Nakagawa/Silicon Valley/IBM@IBMUS. Thank you very much!
    

Local fix

  • This is a problem specific to block based prefetching and withou
    t it the database will still be fully functional with convention
    al page-based prefetching.  To bypass the proble,  turn off bloc
    k based bufferpool, remove the following 2 attributes from the c
    reate bufferpool command
    CREATE BUFFERPOOL IABUFFPOOL IMMEDIATE
           SIZE 8000 AUTOMATIC
           NUMBLOCKPAGES 2048 BLOCKSIZE 32    <---- Remove these att
    ributes
           PAGESIZE 32 K ;
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Using block based buffer pool on a Windows platform.         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Numerous "A buffer pool logic error has  occurred" messages  *
    * were written to db2diag.log.                                 *
    * The file size of db2diag.log  grows rapidly.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Install v95 fp4                                              *
    ****************************************************************
    

Problem conclusion

  • It is fixed in v95 FP4. With the fix, the error messages will
    not appear in the db2diag.log.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR31595

  • Reported component name

    DB2 UDB ESE WIN

  • Reported component ID

    5765F4101

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-01-05

  • Closed date

    2009-06-02

  • Last modified date

    2009-06-02

  • 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 UDB ESE WIN

  • Fixed component ID

    5765F4101

Applicable component levels

  • R950 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
02 June 2009