IC84598: CALLING SNAP_WRITE_FILE MAY CAUSE MEMORY CORRUPTION IN FMP PROCESS LEADING TO OUT OF MEMORY CONDITIONS IN DB2

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • You may encounter the following messages in db2diag.log
    indicating memory corruption in FMP process:
    
    DATA #1 : String, 146 bytes
    NON-FATAL ASSERTION FAILED!!!
    ASSERTION EXPRESSION: Invalid block eye-catcher (0x26E7D47F)
    found at:
    SOURCE FILENAME: snapPROC.C
    LINE NUMBER: 208
    CALLSTCK: (Static functions may not be resolved correctly, as
    they are resolved to the nearest symbol)
    [0] 0x00002AAAAAF6D183 pdLog + 0x1FF
    [1] 0x00002AAAAB8CA2B1 sqlzAssertFailedValist + 0x189
    [2] 0x00002AAAAC9C95EE ossAssertFailureAction + 0x1CA
    [3] 0x00002AAAAC9C9422 _Z21ossAssertMemoryFailedPKcS0_mS0_ + 0xE
    [4] 0x00002AAAAC9E712E _ossMemAllocCheck + 0x904
    [5] 0x00002AAAAC9E60A4 _ossMemFree + 0x104
    [6] 0x00002AAABBB235D8 snap_write_file + 0x2A4
    [7] 0x00002AAAAB02DB18 sqloInvokeFnArgs + 0x40
    [8] 0x00002AAAAB621515 /home/pcinst/sqllib/lib64/libdb2.so.1 +
    0xB70515
    [9] 0x00002AAAAB621897 sqlerDyload + 0x11B
    
    DATA #1 : String, 136 bytes
    NON-FATAL ASSERTION FAILED!!!
    ASSERTION EXPRESSION: Invalid pad type (0x43F66FB) found at:
    SOURCE FILENAME: snapPROC.C
    LINE NUMBER: 208
    CALLSTCK: (Static functions may not be resolved correctly, as
    they are resolved to the nearest symbol)
    [0] 0x00002AAAAAF6D183 pdLog + 0x1FF
    [1] 0x00002AAAAB8CA2B1 sqlzAssertFailedValist + 0x189
    [2] 0x00002AAAAC9C95EE ossAssertFailureAction + 0x1CA
    [3] 0x00002AAAAC9C9422 _Z21ossAssertMemoryFailedPKcS0_mS0_ + 0xE
    [4] 0x00002AAAAC9E6CA6 _ossMemAllocCheck + 0x47C
    [5] 0x00002AAAAC9E60A4 _ossMemFree + 0x104
    [6] 0x00002AAABBB235D8 snap_write_file + 0x2A4
    [7] 0x00002AAAAB02DB18 sqloInvokeFnArgs + 0x40
    [8] 0x00002AAAAB621515 /home/pcinst/sqllib/lib64/libdb2.so.1 +
    0xB70515
    [9] 0x00002AAAAB621897 sqlerDyload + 0x11B
    
    These messages may get logged when snap_write_file stored
    procedure is called. The system may run out of memory if this
    stored procedure gets called continuously over a period of time
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 10.1 Fixpack 1                        *
    ****************************************************************
    

Problem conclusion

  • Fixed in DB2 Version 10.1 Fixpack 1
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC84598

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-14

  • Closed date

    2013-03-28

  • Last modified date

    2013-03-28

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

    IC82278

  • 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

  • RA10 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

10.1

Reference #:

IC84598

Modified date:

2013-03-28

Translate my page

Machine Translation

Content navigation