IBM Support

JR31768: TABLE ROW CORRUPTION REPORTS ERROR "NULL MAPPING BUFFER DURING READNORM" IN DB2DIAG.LOG BUT THERE IS NO INFORMATION ABOUT TABLE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Access to a table with some corruption on its rows on disk might
    produce the following error in the db2diag.log:
    
    C:\tmp>db2 "select count(*) from
    DB2ADMIN.V8T85CCBBEE487811594699DEB1D5E9FC4A"
    
    1
    -----------
    SQL0901N  The SQL statement failed because of a non-severe
    system error.
    Subsequent SQL statements can be processed.  (Reason "Null
    mapping
    buffer
    during ReadNorm".)  SQLSTATE=58004
    
    
    
    2009-01-05-14.52.22.877000+000 I1100H674          LEVEL: Severe
    PID     : 3072                 TID  : 6904        PROC :
    db2syscs.exe
    INSTANCE: DB2                  NODE : 000         DB   : EMIBM
    APPHDL  : 0-7423               APPID: *LOCAL.DB2.090105144203
    AUTHID  : MARIAJ
    EDUID   : 6904                 EDUNAME: db2agent (EMIBM) 0
    FUNCTION: DB2 UDB, data management, sqldReadRow, probe:3197
    MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR
              "non-severe dms programming error"
              DIA8532C An internal processing error has occurred.
    DATA #1 : String, 35 bytes
    Null mapping buffer during ReadNorm
    DATA #2 : String, 7 bytes
    sqldfrd
    
    There is no information regarding the table that has the issue
    in the db2diag.log.
    
    This APAR is to improve the messages in the db2diag.log so we
    include more information about the table to be able to speed up
    problem determination.
    

Local fix

  • N/A
    

Problem summary

  • USER AFFECTED: ALL
    PROBLEM DESCRIPTION:
    
    TABLE ROW CORRUPTION REPORTS ERROR "NULL MAPPING BUFFER DURING
    READNORM" IN DB2DIAG.LOG BUT THERE IS NO INFORMATION ABOUT TABLE
    
    Access to a table with some corruption on its rows on disk
    mightproduce the following error in the db2diag.log:
    
       C:\tmp>db2 "select count(*) from
      DB2ADMIN.V8T85CCBBEE487811594699DEB1D5E9FC4A"
    
    1
    -----------
    SQL0901N  The SQL statement failed because of a non-severe
    system error.
    Subsequent SQL statements can be processed.  (Reason "Null
    mapping
    buffer
    during ReadNorm".)  SQLSTATE=58004
    
    
    
    2009-01-05-14.52.22.877000+000 I1100H674   LEVEL: Severe
    PID : 3072         TID  : 6904   PROC :
    db2syscs.exe
    INSTANCE: DB2         NODE : 000   DB   : EMIBM
    APPHDL : 0-7423        APPID: *LOCAL.DB2.090105144203
    AUTHID : MARIAJ
    EDUID : 6904         EDUNAME: db2agent (EMIBM) 0
    FUNCTION: DB2 UDB, data management, sqldReadRow, probe:3197
    MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR
      "non-severe dms programming error"
     DIA8532C An internal processing error has occurred.
    DATA #1 : String, 35 bytes
    Null mapping buffer during ReadNorm
    DATA #2 : String, 7 bytes
    sqldfrd
    
    There is no information regarding the table that has the issue
    in the db2diag.log.
    
    This APAR is to improve the messages in the db2diag.log so we
    include more information about the table to be able to speed up
    problem determination.
    

Problem conclusion

  • Problem was first fixed in Version 9.1FP8
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR31768

  • Reported component name

    DB2 UDB EXE WIN

  • Reported component ID

    5724E4901

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-01-23

  • Closed date

    2009-10-29

  • Last modified date

    2009-10-29

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

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

    JR31769

Fix information

  • Fixed component name

    DB2 UDB EXE WIN

  • Fixed component ID

    5724E4901

Applicable component levels

  • R910 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"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":"910"}]

Document Information

Modified date:
07 October 2021