|
Problem IC99726
|
Status: Closed |
CALL SYSPROC.AUTOMAINT_SET_POLICY() TO SET A NEW AUTO_REORG POLICY MAY RETURN SQL1437N - 'UNTERMINATED END TAG' DB2AUTOREORG |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Calling SYSPROC.AUTOMAINT_SET_POLICY() to set a AUTO_REORG
policy with an xml policy description may fail with error
SQL1437N despite a correct xml policy file is being used.
SQL1437N The XML in the automatic maintenance policy file or
LOB parameter passed to AUTOMAINT_SET_POLICY or
AUTOMAINT_SET_POLICYFILE is not valid at line number "8"
and column number "21". Validation error
message: "Unterminated end tag, ' DB2AutoReorg
Sample db2diag.log message:
2011-10-19-08.02.21.241939+120 I2275125E366 LEVEL:
Warning
PID : 421 TID : 1105262912 PROC : db2fmp
(
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, Policy, sqlpiValidateAutomaintPolicy,
probe:40
DATA #1 : <preformatted>
Validation Error at Line number: 8 Column: 21 Message:
Unterminated end tag, '.DB2AutoReorgPolicy.'
This happens if the XML description that is passed as argument
strictly fits within the string, i.e. there are no leading or
trailing blanks enclosed. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
Add at least one trailing blank to the XML policy description |
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.1 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.02.2014
13.10.2014
13.10.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
| 10.1.0.5
|
|
