DB2 FOR LUW / DB2FORLUW / A50 - DB2

HADR Standby might fail with DISK FULL error as - 
2016-05-12-17.19.19.473722+330 I25102691E501         LEVEL: 
Error 
PID     : 10903                TID : 46912858220864  PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000            DB   : 
IFMSMIGR 
HOSTNAME: HYDMGOMDBS004 
EDUID   : 8317                 EDUNAME: db2logalloc.0 (IFMSMIGR) 
0 
FUNCTION: DB2 UDB, oper system services, 
sqlo_file_ext_and_commit, probe:100 
MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full." 
          DIA8312C Disk was full. 
DATA #1: Codepath, 8 bytes 
25:26 
 
Ideally, once the log files are archived on primary the 
corresponding log files on standby should be deleted 
immediately. 
Currently, the design is DB2 reads the head extent ID on disk to 
understand the Log file status.It is not updated while Standby 
is replaying. Since the head extent ID is not moving, DB2 
assumes the number of Log files is not increasing, therefore, 
DB2 assumes there is no need to delete extra files log files. 
Once the head extent ID is flushed to disk, DB2  notices the 
need to delete the log files and starts deleting them. But in 
some cases, the customer can hit disk full even before the head 
extent ID is flushed to disk.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 10.5 Fix Pack 9 or higher                     * 
****************************************************************

Deactivate and reactivate standby database, all those old logs 
would be removed from active path and this hdrSNextExtToRename 
value should automatically move up.

First fixed in Db2 10.5 Fix Pack 9

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

16.06.2016
29.09.2017
29.09.2017

9.0.