|
Problem IC84429
|
Status: Closed |
AN ERROR MIGHT OCCUR FOR SYSPROC.ADMIN_CMD EXECUTION OF RUNSTATS/IMPORT/LOAD WHEN NON-ASCII CHARACTERS APPEAR IN COMMAND STRING |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 10.1 fix pack 1. *
**************************************************************** |
| Local Fix: |
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. |
| available fix packs: |
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
|
| Solution |
Problem was first fixed in DB2 UDB Version 10.1 Fix pack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
05.11.2012
05.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
