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

THE GLOBAL FEDERATED SNAPSHOTS WILL FAIL IF FEDERATED APPLICATIO NS EXIST
ON MORE THAN ON MEMBER IN DPF AND SD ENVIRONMENTS.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The following snapshots will fail if federated applications 
exist on more than one member in DPF or SD environments: 
 
    get snapshot for all remote_databases global 
    get snapshot for all remote_applications global 
    get snapshot for remote_databases on <databaseAlias> global 
    get snapshot for remote_applications on <databaseAlias> 
global 
 
The snapshot fails with this SQLCODE: 
 
SQL1042C  An unexpected system error occurred.  SQLSTATE=58004 
 
and probes similar to the following are written to the 
db2diag.log: 
 
2013-04-23-15.42.53.548687-240 I609423E707           LEVEL: 
Severe 
PID     : 23146                TID : 46912841443648  PROC : 
db2sysc 1 
INSTANCE: jwr                  NODE : 001            DB   : 
APPHDL  : 1-106                APPID: *N1.jwr.130423194316 
AUTHID  : JWR                  HOSTNAME: hotel38 
EDUID   : 194                  EDUNAME: db2agent (instance) 1 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging function), probe:50 
MESSAGE : No aggregation rule. Element1 (232) is: 
DATA #1 : Hexdump, 32 bytes 
0x00002AAB265393FC : 1800 0000 0100 E800 0400 0000 3800 2C01 
............8.,. 
0x00002AAB2653940C : 0100 0000 0400 0000 3800 2D01 68A0 0A00 
........8.-.h... 
 
2013-04-23-15.42.53.548942-240 I610131E707           LEVEL: 
Severe 
PID     : 23146                TID : 46912841443648  PROC : 
db2sysc 1 
INSTANCE: jwr                  NODE : 001            DB   : 
APPHDL  : 1-106                APPID: *N1.jwr.130423194316 
AUTHID  : JWR                  HOSTNAME: hotel38 
EDUID   : 194                  EDUNAME: db2agent (instance) 1 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging function), probe:50 
MESSAGE : No aggregation rule. Element2 (232) is: 
DATA #1 : Hexdump, 32 bytes 
0x00002AAB264E92EF : 1800 0000 0100 E800 0400 0000 3800 2C01 
............8.,. 
0x00002AAB264E92FF : 0000 0000 0400 0000 3800 2D01 3813 0000 
........8.-.8... 
 
2013-04-23-15.42.53.549130-240 I610839E614           LEVEL: 
Severe 
PID     : 23146                TID : 46912841443648  PROC : 
db2sysc 1 
INSTANCE: jwr                  NODE : 001            DB   : 
APPHDL  : 1-106                APPID: *N1.jwr.130423194316 
AUTHID  : JWR                  HOSTNAME: hotel38 
EDUID   : 194                  EDUNAME: db2agent (instance) 1 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging function), probe:50 
MESSAGE : No aggregation rule. Parent (34) is: 
DATA #1 : Hexdump, 8 bytes 
0x00002AAB26469254 : 0000 0000 0100 2200 
......". 
 
2013-04-23-15.42.53.549283-240 I611454E499           LEVEL: 
Severe 
PID     : 23146                TID : 46912841443648  PROC : 
db2sysc 1 
INSTANCE: jwr                  NODE : 001            DB   : 
APPHDL  : 1-106                APPID: *N1.jwr.130423194316 
AUTHID  : JWR                  HOSTNAME: hotel38 
EDUID   : 194                  EDUNAME: db2agent (instance) 1 
FUNCTION: DB2 UDB, database monitor, 
sqm_aggr_snapshot_buffer::aggregate, probe:65 
RETCODE : ZRC=0x000000E8=232
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 10                       * 
****************************************************************
Local-Fix:
Rather than specifying "GLOBAL" to direct the snapshot to all 
members specify "AT MEMBER" to direct the snapshot to a specific 
member.
Lösung
First fixed in Version 9.7 Fix Pack 10
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.07.2014
17.11.2014
17.11.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP10
Problem behoben lt. FixList in der Version
9.7.0.10 FixList