DB2 FOR LUW / DB2FORLUW / A50 - DB2

Restart and crash recovery of a DB2 database might fail with 
SQL1042C. 
 
Following entry will be written to the db2diag.log at the 
beginning of the crash recovery operation: 
 
2014-02-04-10.38.44.516160+060 I8094835A533       LEVEL: Severe 
PID     : 7405980              TID  : 5912        PROC : db2sysc 
0 
INSTANCE: db2v97               NODE : 000         DB   : SAMPLE 
APPHDL  : 0-53                 APPID: *N0.db2tbp.140204093845 
AUTHID  : DB2V97 
EDUID   : 5912                 EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, sqlpgint, probe:450 
RETCODE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic 
Error" 
          DIA8526C A fatal error occurred in data protection 
services. 
 
 
To hit this issue following conditions must be true: 
 
1. database configured for infinite logging (LOGSECOND -1) 
 
2. slow or not working log file archiving 
 
3. force down the database / instance 
 
4. attempt database restart while log archiving is still not 
working correctly 
 
 
Due to the second condition no log file re-name and re-use will 
take place. Log files will stay in the active log directory and 
DB2 will start to allocate new log files up to the allowed 
maximum of 256 (+ 2) since last successfully archived log file. 
This is tracked in the log file array and log file count in the 
database log control files (SQLOGCTL.LFH.1/SQLOGCTL.LFH.2). 
As soon as DB2 reached the maximum of 256 (+2) log files the 
database database will appear to hang. 
 
A forced shutdown of the database / instance to release the hang 
situation will leave the database in the need for crash recovery 
at the next activation. 
 
If the database is restarted while log archiving is still not 
working DB2 will fail to create new log files during crash 
recovery and fail with the crash recovery operation. 
In addition the log file count is further increased by 1 to 259. 
 
This is not expected and will cause any subsequent attempt to 
bring up the database to fail with SQL1042C.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 FixPack 4                        * 
****************************************************************

Fix the log archiving issue instead of forcing down the 
database. With log files being archived successfully again the 
database will continue to work.

First fixed in DB2 version 10.5 FixPack 4

not known / see Local fix

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

26.03.2014
09.09.2014
09.09.2014