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 IC74728 Status: Closed

SQL16210N WHILE RUNNING MON_GET_CONNECTION_DETAILS() WHEN REMOTE CLIENTS
ARE CONNECTED

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
You can experience SQL16210N while running 
MON_GET_CONNECTION_DETAILS() when remote clients are connected 
to the database. For example, 
 
select XMLVALIDATE(XMLPARSE(document p.DETAILS) according to 
xmlschema id DB2_WLM_METRICS_SCHEMA) from TABLE 
(MON_GET_CONNECTION_DETAILS(NULL, CAST (NULL AS SMALLINT))) as p 
 
  SQL16210N  XML document contained a value "32860" that 
violates a facet constraint.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* You can experience SQL16210N while running                   * 
*                                                              * 
* MON_GET_CONNECTION_DETAILS() when remote clients are         * 
* connected                                                    * 
* to the database. For example,                                * 
*                                                              * 
*                                                              * 
*                                                              * 
* select XMLVALIDATE(XMLPARSE(document p.DETAILS) according to * 
*                                                              * 
* xmlschema id DB2_WLM_METRICS_SCHEMA) from TABLE              * 
*                                                              * 
* (MON_GET_CONNECTION_DETAILS(NULL, CAST (NULL AS SMALLINT)))  * 
* as p                                                         * 
*                                                              * 
*                                                              * 
*   SQL16210N  XML document contained a value "32860" that     * 
*                                                              * 
* violates a facet constraint.                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Recommended to upgrade to v97fp5 when available or follow    * 
* the steps provided in the Temporary Fix section              * 
****************************************************************
Local Fix:
This problem can we worked around by modifying the 
DB2MonRoutines.xsd schema file under the sqllib/misc directory 
under the install path  changing the data type of the 
"client_port_number" element from short to int. The modified 
data looks like this -- 
 
       <xs:element name = "client_port_number" 
                   type = "xs:int" 
                   minOccurs = "0" maxOccurs = "1" > 
         <xs:annotation> 
           <xs:documentation> 
           See monitor element client_port_number for more 
details. 
           </xs:documentation> 
         </xs:annotation> 
       </xs:element>
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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

Solution
The permanent fix will be available form v97fp5 onwards.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.02.2011
02.01.2012
02.01.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList