home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC81013 Status: Geschlossen

IF THE CLI/ODBC CONFIGURATION KEYWORD TRACEREFRESHINTERVAL IS SET, THE
VALUE OF TRACEPIDLIST MIGHT CHANGE UNEXPECTEDLY.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of DB2 for Linux, UNIX and Windows                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* .                                                            * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
Problem was first fixed in Version 9.7 Fix Pack 6. 
At a minimum, this fix should be applied on the client.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.01.2012
15.06.2012
15.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList