DB2 FOR LUW / DB2FORLUW / A10 - DB2

During migration from V9.7 to V10.1 FP4 (or earlier) it's 
possible to hit a SQL1762N (Unable to connect to database 
because there is not enough space to allocate active log 
files. SQLSTATE=08004). 
Internally the code is suppose to check available disk space on 
the new path (and on the new mirror) path. If there is enough 
space DB2 will go ahead with creating the new log files. 
As ong as either the primary or mirror has enough space DB2 will 
continue to allocate files since we only need 1 path to be 
successfull. On this case, the database being mirated does not 
have a mirror path, so the mirror path free space should be zero 
and DB2 should only consider free space on the active logpath. 
However even though there is no mirror path, there is a timing 
hole where DB2 detects there is enough space on the mirror path, 
and so DB2 will go ahead to create logs but run out of room thus 
returning SQL1762N and migration will fail.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply DB2 Version V10.1.0.5                                  * 
****************************************************************

Reduce the count of active (primary) logs then restart 
the database migration. 
***This APAR is a new variation of APAR IC99671 fixed in V10.1 
   FP4.

Problem is first fixed in DB2 UDB version 10.1 fix pack 5.

not known / see Local fix

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

22.07.2014
24.07.2015
24.07.2015