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

DATABASE CRASHES WHEN ATTEMPTING A DROP COMMAND THAT CONTAINS
"NULLS"

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
For example, when attempting to drop a schema containing special 
characters or a table containing spaces, 
the database can crash and the following can appear in the 
db2diag.log: 
 
2012-08-23-09.56.31.086951-300 E9434658E1679       LEVEL: Info 
(Origin) 
PID     : 36889                TID  : 140713350129408PROC : 
db2sysc 0 
INSTANCE: DB2INST1             NODE : 000          DB   : SAMPLE 
APPHDL  : 0-20781              APPID: 
172.32.1.79.2536.120823145630 
AUTHID  : DB2INST1 
EDUID   : 4646                 EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, SW- common services, sqlnn_cmpl, probe:650 
MESSAGE : ZRC=0x8704002F=-2029780945=SQLD_PARM "PARAMETER ERROR" 
DIA8544C An invalid data type was encountered, the value was "". 
DATA #1 : String, 62 bytes 
An unexpected error was detected during statement compilation. 
DATA #2 : Boolean, 1 bytes 
true 
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: -902   sqlerrml: 2 
 sqlerrmc: 47 
 sqlerrp : SQLRC06B 
 sqlerrd : (1) 0x8704002F      (2) 0x0000002F      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000Page 29 of 120 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
DATA #8 : Hex integer, 4 bytes 
0x04000040 
DATA #9 : String, 371 bytes 
Compiler error stack for rc = -2029780945: 
sqlnn_cmpl[300] 
sqlnp_main[250] 
sqlnp_parser[510] 
sqlnp_smactn[100] 
sqlnq_drop_db_object[430] 
sqlnq_table_old[110] 
sqlnq_handle_from_table_re[10] 
sqlnq_handle_table_ref[5] 
sqlnq_handle_named_ref[110] 
sqlnq_handle_named_ref[110] 
sqlnq_handle_named_ref[120] 
sqlnq_handle_qtb_extref_re[20] 
sqlnq_cat_look[170] 
sqlnq_cat_look2[120]
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix    * 
* Pack 4) or higher                                            * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4)
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.12.2013
22.09.2014
22.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList