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 IC83878 Status: Geschlossen

ADM1542W MESSAGE MAY SHOW EMPTY STRINGS FOR APPLICATION HANDLE AND OTHER
FIELDS.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The following message may dump out empty fields for "application 
handle", "application id", 
"authentication id", and MAX_LOG (current value)" when the 
application violates the database 
configuration parameter MAX_LOG.  For example you will see the 
following message in 
the db2diag.log: 
 
 
2012-05-27-00.51.13.686611-240 E9714111A797       LEVEL: Error 
PID     : 54657160             TID  : 31556       PROC : db2sysc 
2 
INSTANCE: db2inst1        NODE : 001         DB   : SAMPLE 
APPHDL  : 1-29417              APPID: 
xx.x.xx.xx.xxxxx.xxxxxxxxxxxx 
AUTHID  : DB2INST1 
EDUID   : 31556                EDUNAME: db2agntp (SAMPLE) 2 
FUNCTION: DB2 UDB, data protection services, sqlpgResSpace, 
probe:560 
MESSAGE : ADM1542W  Application 
          "samp.1-29417.xx.x.xx.xx.xxxxx.xxxxxxxxxxxx.DB2INST1 
.75.." with 
          application handle "" and application id "" executing 
under 
          authentication id "" will be forced off of the 
database for violating 
          database configuration parameter MAX_LOG (current 
value ""). The unit 
          of work will be rolled back.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP7 or                                    * 
* You can use the APPHDL, APPID, AUTHID from the db2diag       * 
* message                                                      * 
* to identify the missing fields, eg:                          * 
*                                                              * 
* APPHDL  : 1-29417              APPID:                        * 
* xx.x.xx.xx.xxxxx.xxxxxxxxxxxx                                * 
* AUTHID  : DB2INST1                                           * 
****************************************************************
Local-Fix:
You can use the APPHDL, APPID, AUTHID from the db2diag message 
to identify the missing fields, eg: 
 
APPHDL  : 1-29417              APPID: 
xx.x.xx.xx.xxxxx.xxxxxxxxxxxx 
AUTHID  : DB2INST1
verfügbare FixPacks:
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 fixed in DB2 Version 9.7 Fix Pack 7 and subsequent fix 
packs.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
31.05.2012
05.11.2012
05.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP7
Problem behoben lt. FixList in der Version
9.7.0.7 FixList