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

IF CONNECTING TO A DATABASE ON WINDOWS THROUGH IBM SSH, SOME SQLS FROM DATA
STUDIO FAIL WITH '< WRONG USAGE' MESSAGE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
If you connect to a database on Windows from Data Studio 
through IBM SSH, some SQL statements fail with '< wrong usage' 
message. 
 
  For example, 
 
  When you perform 'Configure Automatic Maintenance' with 
Automatic table and index reorganization option, 'CALL SYSPROC' 
is generated but it fails with '< wrong usage' message. 
 
  When you try the following SQL on Data Studio SQL Editor, it 
fails with '< wrong usage' message. 
 
  CALL SYSPROC.AUTOMAINT_SET_POLICY ( 'AUTO_REORG', BLOB('<?xml 
version="1.0" encoding="UTF-8"?><DB2AutoReorgPolicy 
xmlns="http://www.ibm.com/xmlns/prod/db2/autonomic/config"><Reor 
gOptions dictionaryOption="Keep" indexReorgMode="Offline" 
useSystemTempTableSpace="false"/><ReorgTableScope 
><FilterClause>TABSCHEMA LIKE ''%OPM%'' OR TABSCHEMA LIKE 
''%SYS%''</FilterClause></ReorgTableScope ></DB2AutoReorgPolicy> 
') )
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* IBM SSH on Windows user                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix    * 
* Pack 4) or higher                                            * 
****************************************************************
Local Fix:
Solution
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4)
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.03.2014
23.02.2015
23.02.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList