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

WHEN DDL ON AN UNDEFINED OBJECT IS EXECUTED, THE TRANSACTION IS OPENED EVEN
THOUGH THE DDL ITSELF FAILS WITH SQL0204N.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When DDL on an undefined object is executed, the transaction is 
opened even though the DDL itself fails with SQL0204N. It's 
because DB2 logs a record indicating that DDL has just started 
and then checks if the object exists. 
 
> db2 list applications 
 
Auth Id  Application    Appl.      Application Id 
DB       # of 
         Name           Handle 
Name    Agents 
-------- -------------- ---------- 
-------------------------------------------------------------- 
-------- ----- 
DB2INST7 db2bp          9049       *LOCAL.db2inst7.130214004413 
HADRDB   1 
 
> db2pd -d hadrdb -trans | egrep 'Address| 9049 ' 
Address            AppHandl [nod-index] TranHdl    Locks 
State   Tflag      Tflag2     Firstlsn           Lastlsn 
SpaceReserved   LogSpace        TID            AxRegCnt   GXID 
ClientUserID                   ClientWrkstnName 
ClientApplName                 ClientAccntng 
0x070000004007F900 9049     [000-09049] 18         0 
READ    0x00000000 0x00000000 0x0000000000000000 
0x0000000000000000 0               0 
0x0000000112FD 1          0        n/a 
n/a                            n/a 
n/a 
 
> db2 +c "drop table notab" 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0204N  "DB2INST7.NOTAB" is an undefined name.  SQLSTATE=42704 
 
> db2pd -d hadrdb -trans | egrep 'Address| 9049 ' 
Address            AppHandl [nod-index] TranHdl    Locks 
State   Tflag      Tflag2     Firstlsn           Lastlsn 
SpaceReserved   LogSpace        TID            AxRegCnt   GXID 
ClientUserID                   ClientWrkstnName 
ClientApplName                 ClientAccntng 
0x070000004007F900 9049     [000-09049] 18         2 
WRITE   0x00000000 0x00000000 0x0000000005457214 
0x0000000000000000 74              486 
0x0000000112FD 1          0        n/a 
n/a                            n/a 
n/a 
 
This could lead a system to 'Transaction Log Full' situation if 
it's run with AUTOCOMMIT OFF and never committed.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users on HADR with ROS                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V97FP9                                            * 
****************************************************************
Local-Fix:
Run COMMIT after DDL.
verfügbare FixPacks:
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
Fixed in V97FP9
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.02.2013
05.05.2014
05.05.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP9
Problem behoben lt. FixList in der Version
9.7.0.9 FixList
9.7.0.9 FixList