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

YOU MAY ENCOUNTER A FODC PANIC DURING DROP TABLE COMMAND in DPF.

Produkt:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problembeschreibung:
In a DPF environment, if the execution of a DROP TABLE is 
interrupted, if a second DROP TABLE for the same object is 
executed 
in the same connection in the same transaction a trap 
may occur producing FODC_Panic or FODC_Trap within a subagent 
EDU. 
 
Note that in order to be exposed to this issue, the DROP TABLE 
has to be issued from a connection that is not connected to 
the catalog partition. 
 
 
The following may be logged in db2diag.log file (interrupt and 
incomplete invalidation): 
 
2018-06-05-18.01.00.670328-240 E4654872A1573        LEVEL: Info 
(Origin) 
PID     : 46530564             TID : 54843          PROC : 
db2sysc 2 
INSTANCE: db2inst             NODE : 002           DB   : SAMPLE 
APPHDL  : 0-11381              APPID: 
111.2.333.444.55555.180605213502 
AUTHID  : A123456              HOSTNAME: hostname 
EDUID   : 54843                EDUNAME: db2agntp (SAMPLE) 2 
FUNCTION: DB2 UDB, SW- common services, sqlnn_cmpl, probe:650 
MESSAGE : ZRC=0x80580003=-2141716477=SQLKD_INTERRUPT "Mapping 
for SQLKF_INTRP" 
          DIA8003C The interrupt  has been received. 
DATA #1 : String, 62 bytes 
An unexpected error was detected during statement compilation. 
DATA #2 : Boolean, 1 bytes 
false 
DATA #3 : Boolean, 1 bytes 
false 
DATA #4 : Boolean, 1 bytes 
true 
DATA #5 : Boolean, 1 bytes 
false 
DATA #6 : Hex integer, 4 bytes 
0x00000000 
DATA #7 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: 0   sqlerrml: 0 
 sqlerrmc: 
 sqlerrp : SQL11012 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000002 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
DATA #8 : Hex integer, 4 bytes 
0x00000000 
DATA #9 : String with size, 33 bytes 
DROP TABLE XY.TABLE1 
DATA #10: String, 167 bytes 
Compiler error stack for rc = -2141716477: 
sqlnn_cmpl[300] 
sqlnp_main[250] 
sqlnp_parser[510] 
sqlnp_smactn[180] 
sqlnq_drop_db_object[700] 
sqlnq_drop_db_object_end[225] 
  
I.e. evidence a drop table statement failing with an interrupt 
error in sqlnq_drop_db_object_end() 
  
followed by a message that a previous invalidation was not 
cleaned up: 
  
2018-06-05-18.01.45.757119-240 I4828645A731         LEVEL: Error 
PID     : 9044082              TID : 57287          PROC : 
db2sysc 1 
INSTANCE: db2inst               NODE : 001           DB   : 
SAMPLE 
APPHDL  : 0-11381              APPID: 
111.2.333.444.55555.180605213502 
AUTHID  : A123456              HOSTNAME: hostname 
EDUID   : 57287                EDUNAME: db2agntp (SAMPLE) 1 
FUNCTION: DB2 UDB, access plan manager, sqlra_inval_obj_hard, 
probe:10 
DATA #1 : String, 36 bytes 
previous invalidation not cleaned up 
DATA #2 : String with size, 19 bytes 
TABLE1 
DATA #3 : String with size, 8 bytes 
XY       
DATA #4 : ASCII Char, 1 bytes 
T 
DATA #5 : unsigned integer, 4 bytes 
25 
DATA #6 : unsigned integer, 4 bytes 
3 
 
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1 Fixpack 3 Mod 2 or higher                * 
****************************************************************
Local-Fix:
If a drop is interrupted, re-issue the drop, only after 
committing the transaction. 
Alternatively issue drop tables from connections that are at the 
catalog partition.
Lösung
First fixed in Db2 11.1 Fixpack 3 Mod 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.06.2018
07.08.2018
07.08.2018
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version