DB2 FOR LUW / DB2FORLUW / 910 - DB2

If the CLI/ODBC configuration keyword TraceRefreshInterval is 
set, the value of TracePIDList might change unexpectedly. 
 
That is demonstrated by the following UNIX shell script. 
 
<code> 
    set -x 
    DATABASE=sample  # Set DATABASE to the name of a database. 
 
#Start from scratch by making sure that: 
#1) There is no Command Line Processor back-end process for this 
session. 
#2) The DB2 instance is stopped. 
#3) No ODBC/CLI configuration keywords are set. 
    db2 "terminate" 
    db2stop force 
    rm $DB2INSTANCE/sqllib/cfg/db2cli.ini 
 
# Set Trace to 0, set TraceRefreshInterval, and set TracePIDList 
to some value. 
    db2 "update cli configuration for section common using trace 
0 tracerefreshinterval 5 tracepidlist 1" 
    db2 "get cli configuration" 
 
# Start DB2 and connect to a database. 
    db2start 
    db2 "connect to $DATABASE" 
 
#Wait 180 seconds. 
    sleep 180 
 
# Set Trace to 1, and set TracePIDList to a new value. 
    db2 "update cli cfg for section common using trace 1 
tracepidlist 2" 
    db2 "get cli configuration" 
 
# Wait 180 seconds. 
    sleep 180 
 
# Now when you run GET CLI CONFIGURATION, it shows that 
TracePIDList has reverted from 2 to its earlier value 1. 
    db2 "get cli configuration" 
</code>

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of CLI/ODBC applications with DB2 for Linux, UNIX and  * 
* Windows                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* .                                                            * 
****************************************************************

As a workaround you can make it so that when the DB2 instance is 
started TraceRefreshInterval is not set, and set 
TraceRefreshInterval only AFTER the DB2 instance is started.

Fix Release: DB2 9.5 and DB2 9.7 
Fix Commitment Level: 999

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

25.01.2012
07.02.2012
07.02.2012