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 IC84244 Status: Geschlossen

CALL CAPTURE_STORAGEMGMT_INFO RETURNS ERROR SQL0443N, "SQL0407
TOKEN:TBSPACEID=2, TABLEID=8, COLNO=3 ". SQLSTATE=38553

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
call CAPTURE_STORAGEMGMT_INFO returns error SQL0443N, "SQL0407 
Token:TBSPACEID=2, TABLEID=8, COLNO=3".  SQLSTATE=38553 
 
This issue occurs only when database is created in Oracle mode, 
where the empty string cannot be assigned to NOT NULL column. 
 
Test Case: 
 
$ db2set -all 
[i] DB2_COMPATIBILITY_VECTOR=ORA 
 
$ db2stop force 
db2sSQL1064N  DB2STOP processing was successful. 
 
$ db2start 
db2 create db oSQL1063N  DB2START processing was successful. 
 
$ db2 create db ordb 
DB20000I  The CREATE DATABASE command completed successfully. 
 
$ db2 connect to ordb 
 
   Database Connection Information 
 
 Database server        = DB2/LINUXX8664 9.7.6 
 SQL authorization ID   = LAPPANNA 
 Local database alias   = ORDB 
 
$ db2 "call drop_storagemgmt_tables(1)" 
  Return Status = 0 
 
$ db2 "call create_storagemgmt_tables('USERSPACE1')" 
  Return Status = 0 
 
$ db2 "call CAPTURE_STORAGEMGMT_INFO(0,'','ORDB')" 
SQL0443N  Routine "*GMT_INFO" (specific name "") has returned an 
error SQLSTATE with diagnostic text "SQL0407 Token:TBSPACEID=2, 
TABLEID=8, COLNO=3".  SQLSTATE=38553
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Unknown                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10 FixPack 1                                 * 
****************************************************************
Local-Fix:
N/A
verfügbare FixPacks:
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

Lösung
First Fixed in DB2 V10 FixPack 1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.06.2012
05.11.2012
05.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList