DB2 - Problembeschreibung
Problem IC91765 | Status: Geschlossen |
-member/-dbp problems for db2fodc command on DPF | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
1) In a partition environment the "db2fodc -perf -member all ( or -alldbp, or multiple number E.g. 0,1,2 )"does not gather the snapshot information. In the snapshot directory created by the FODC there will be the messages similar to the following: get monitor switches at dbpartitionnum 1 2 3 4 5 6 7 8 SQL0104N An unexpected token "2" was found following "<identifier>". Expected tokens may include: "END-OF-STATEMENT". SQLSTATE=42601 get snapshot for all on at dbpartitionnum 1 2 3 4 5 6 7 8 SQL0104N An unexpected token "dbpartitionnum" was found following "AT". Expected tokens may include: "GLOBAL". SQLSTATE=42601 These error are due to incorrect syntax used. 2) "db2fodc -perf full -member all (or -alldbp, or multiple numbers e.g. 0,1,2 )" will not collect db2perfcoun data, becuase -member option does not work with -perfcount option for db2trc. The following error will be logged in db2perfcount.*.out: Incorrect option. Usage: db2trc [facility] clear Incorrect option. Cannot dump trace when trace is off. Usage: db2trc [facility] clear Trace is already off; no action was taken. 3) If -member option contains remote memer(s) ( member on another host ), db2fodc command may not work properly on remote host | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 10.1 FixPack 3 * **************************************************************** | |
Local-Fix: | |
For 1): Use db2fodc -hang option. For 2) and 3): Don't use -member option, use -host option instead | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in DB2 UDB Version 10.1 FixPack 3 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 22.04.2013 21.10.2013 21.10.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |