|
Problem IC74728
|
Status: Geschlossen |
SQL16210N WHILE RUNNING MON_GET_CONNECTION_DETAILS() WHEN REMOTE CLIENTS ARE CONNECTED |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* 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> |
| verfügbare FixPacks: |
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
|
| Lösung |
The permanent fix will be available form v97fp5 onwards. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 28.02.2011
02.01.2012
02.01.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP5
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.5
|
 |
