home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC77886 Status: Geschlossen

AN ERROR MIGHT OCCUR FOR SYSPROC.ADMIN_CMD EXECUTION OF
RUNSTATS/IMPORT/LOAD WHEN NON-ASCII CHARACTERS APPEAR IN COMMAND STRING

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* 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.                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.7 fixpack 6.                    * 
****************************************************************
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.
verfügbare FixPacks:
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
Problem was first fixed in DB2 UDB Version 9.7 FixPack 6
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC84428 IC84429 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.08.2011
04.06.2012
04.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList