IBM Support

IT32039: Open error on primary log path could lead to forced database shutdown and panic

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A bad log condition such as below could lead to an unnecessary
    forced database shutdown and panic
    
    MESSAGE : ADM1839W An error occurred while DB2 was writing log
    data to log
        file "S0078319.LOG" on path
    "/DB2/PRD/Logs/NODE0000/LOGSTREAM0000/".
        The log file is still available on log path
        "/DB2/PRD/mDb2Logs/NODE0000/LOGSTREAM0000/". DB2 will
    attempt to use
        both paths for subsequent log files. In the meantime, check
    that the
        specified log path in which the error occurred exists and is
        accessible. Also check that there is space available in the
    file
        system.
    
    2020-01-10-06.24.28.916903-300 I72860372E594    LEVEL: Info
    PID  : 17290       TID : 139850451773184 PROC : db2sysc 0
    INSTANCE: db2admin      NODE : 000     DB : NOW
    HOSTNAME:
    EDUID : 29         EDUNAME: db2loggw (NOW) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgoleMergeRCs,
    probe:100
    MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File
    cannot be used"
        DIA8414C Logging can not continue due to an error.
    DATA #1 : <preformatted>
    Open error on primary path
    /DB2/PRD/Logs/NODE0000/LOGSTREAM0000/S0078320.LOG
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 11.1 Fix Pack 6                       *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 Version 11.1 Fix Pack 6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT32039

  • 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

    2020-02-28

  • Closed date

    2021-03-23

  • Last modified date

    2021-03-23

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

    IT31894

  • 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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 May 2022