DB2 FOR LUW / DB2FORLUW / 970 - DB2

If user-defined column defaults are altered while in a NOT 
LOGGED INITIALLY transaction, the NOT LOGGED INITIALLY 
(NLI) flag may be written to disk. Examples of such actions 
include: 
- adding a column with a user default 
- altering a column to include a user default 
- altering a column to remove a user default 
- dropping the last column in a table that included a user 
default 
 
In these situations, the NLI flag would be turned off 
in memory, allowing DB2 to operate normally. However, if the 
affected table's control block is flushed from memory (e.g. 
database was deactivated), the table's control information will 
be read from disk into memory. When the NLI flag becomes active 
in memory, DB2 will stop logging transactions related to the 
affected table. Other unexpected behaviour may occur due to the 
lack of logging. 
 
This flag can be reset to its proper value both in memory and on 
 
disk by performing a classic reorg on the table. 
 
To find if the NLI flag been written to disk for a table, 
use the DB2DART utility with the "/DD" parameter on page 0 of 
table with "/V YES". 
 
In the output, search for the heading "Record Type = Table 
Directory Record". Underneath, table directory flags similar to 
the one below can be found. The NLI flag is the sixth bit from 
the end. If it is set to "1" like the example below, then the 
table is affected by this APAR. 
 
Flags = x0000000106000024 
   bit representation = 00000000 00000000 00000000 00000001 
                        00000110 00000000 00000000 00100100

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* After a specific set of alter table commands, the NOT LOGGED * 
* INITIALLY flag could be erroneously set on disk, causing     * 
* erratic behaviour.                                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack 5.                              * 
****************************************************************

Perform classic reorg on the affected table. If the lack of 
logging is a concern, perform a backup.

DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

This problem was first fixed in DB2 V9.7 Fix Pack 5.

not known / see Local fix

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

28.06.2011
19.01.2012
19.01.2012

9.7.FP5