DB2 - Problem description
Problem IT30388 | Status: Closed |
PRIMARY TRANSACTIONS MAY BE BLOCKED BY STANDBY WHERE LOG DISK FULL ERROR IS HAPPENING | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Log Disk full error on standby may block transactions on primary even BLK_LOG_DSK_FUL is set to NO, this is not expected. When this problem is happending, stack shows: #transactions are blocked at logging 0x00002AAAAEDFCEA0 sqloWaitThreshold + 0x01d0 0x00002AAAAEE9CFFB _Z17sqlpWaitThresholdP22sqlo_WaitPostThresholdmim + 0x00bb 0x00002AAAB1055B78 _Z27sqlpgWaitForLrecBufferLimitP14sqlpMasterDbcbm + 0x00f8 0x00002AAAB1EF2DCD _Z14sqlpWriteToLogP8sqeAgentmmmP14SQLP_LREC_PARTP9SQLP_LSN8Pm + 0x1d8d 0x00002AAAB1EEF29C _Z11sqlpWriteLRP8sqeAgentmmmmmP14SQLP_LREC_PARTmP9SQLP_LSN8Pm + 0x02ec # db2loggw is waiting for db2hadrp I think: 0x00002AAAAEDCFC55 sqloWaitEDUWaitPost + 0x02a5 0x00002AAAAEF114F9 _ZN11sqpLoggwEdu8sqlpgwlpEmmPK9SQLP_LSN8m + 0x18c9 0x00002AAAAEEC31EA _ZN11sqpLoggwEdu13sqlpLoggwMainEv + 0x168a 0x00002AAAAEF78668 _ZN11sqpLoggwEdu6RunEDUEv + 0x0028 # db2hadrp was waiting for db2hadrs: >>>27363.44.000.stack.txt | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * N/A * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 v11.1 or v11.5 with the latest fixpack level. * **************************************************************** | |
Local Fix: | |
Use DB2_HADR_PEER_WAIT_LIMIT to prevent this problem. As an example, set the following on both primary and standby: db2set DB2_HADR_PEER_WAIT_LIMIT=15 restart Db2 server to take effect | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * N/A * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 v11.1 or v11.5 with the latest fixpack level. * **************************************************************** | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.09.2019 12.03.2020 12.03.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |