DB2 FOR LUW / DB2FORLUW / 970 - DB2

'db2trc' command might use only 8MB of trace buffer, regardless 
of available trace buffer allocated in DB2 instance memory set 
named "Trace". 
For example on AIX platform, after 'db2trc on -i 128M' command 
the 'db2trc info' output indicates only 8MB trace buffer is 
used: 
=========================================== 
maxBufferSize           : 8388608 bytes (8 MB) 
auxBufferSize           : 6291456 bytes (6 MB) 
=========================================== 
while the 'db2pd -memset' output indicates about 130MB trace 
buffer is available: 
=========================================== 
Memory Sets: 
Name         Address            Id          Size(Kb)   Key 
DBP    Type   Unrsv(Kb)  Used(Kb)   HWM(Kb)    Cmt(Kb) 
Uncmt(Kb) 
Trace        0x0770000000000000 131072030   137570 
0xEBD69A74  0      -1     0          137570     0 
137570     0 
=========================================== 
 
This happens only if the '-f' option was specified in the first 
successful 'db2trc on' command after instance startup, for 
example: 
  db2start 
  db2trc on -f db2trc.bin 
  db2trc off 
 
Once the problem happens, you can only resolve it by recycling 
DB2 instance: 
  db2stop 
  db2start

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.7 on Linux, Unix and Windows          * 
* platforms.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 LUW Version 9.7 Fix Pack 10 or higher levels.  * 
****************************************************************

To prevent the problem, avoid using '-f' option in the first 
'db2trc on' command after instance startup. Here is an example: 
  db2start 
  db2trc on 
  db2trc off 
After that, any subsequent 'db2trc on' command (even with the 
'-f' option) can make use of all available trace buffer 
allocated in the memory set.

First fixed in DB2 LUW Version 9.7 Fix Pack 10.

To prevent the problem, avoid using '-f' option in the first 
'db2trc on' command after instance startup. Here is an example: 
  db2start 
  db2trc on 
  db2trc off 
After that, any subsequent 'db2trc on' command (even with the 
'-f' option) can make use of all available trace buffer 
allocated in the memory set.

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

14.03.2014
10.11.2014
10.11.2014

9.7.FP10