DB2 FOR LUW / DB2FORLUW / A10 - DB2

You might receive an error when calling the sysproc.admin_cmd 
for runstats when the command string includes table, index, 
and/or column identifiers with non-ASCII characters.  The 
problem can occur when the connection is made by an application 
whose codepage is different from the database codepage. 
 
You can examine an application's codepage from an application 
snapshot.  You can examine the database's codepage from the 
database configuration file. 
 
The following error codes can be observed: 
- SQL2301N  The tablename parameter is not valid.  Either it is 
too long, only an authorization ID was specified, or the address 
of the name is not valid. 
- SQL2309N  The index name "<name>" is not valid.  It is too 
long or only a qualifier was specified. 
- SQL0205N  Column or attribute "<name>" is not defined in 
"<table>".  SQLSTATE=42703 
-SQL3015N  An SQL error "-104" occurred during processing. 
-SQL3304N  The table does not exist.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.1 fix pack 1.                  * 
****************************************************************

1) In the same unequal codepage connection, use the 
runstats/import/load 
command or API, instead of the admin_cmd procedure, or 2) Use an 
equal codepage connection and make the admin_cmd call using the 
object name in the database codepage.

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 UDB Version 10.1 Fix pack 1.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

14.06.2012
05.11.2012
05.11.2012