home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC87821 Status: Closed

-member/-dbp problems for db2fodc command on DPF

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FP 8                                     * 
****************************************************************
Local Fix:
For 1): Use db2fodc -hang option. 
For 2) and 3): Don't use -member option, use -host option 
instead
available fix packs:
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

Solution
Fixed in DB2 Version 9.7 Fix Pack 8
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC91577 IC91765 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.11.2012
19.04.2013
19.04.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.8 FixList