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

SQL0901N MAY BE RETURNED WHEN DROPPING AN INVALID FUNCTION CONTAINING AN
INDEX EXTENSION

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Starting in DB2 Version 9.7, when a function is being dropped, 
its dependent functions will get invalidated. If the dependent 
function has an index extension, dropping the parent function 
will cause the index extension to be dropped from the system 
catalogs during the invalidation. Thus, when the dependent 
function gets dropped at a later time, SQL0901N gets returned as 
the corresponding record for the user-defined predicate 
specification cannot be found in the system catalogs. 
 
You will find the following record in the db2diag.log: 
 
2011-08-17-15.15.46.994781-300 E197133A1440       LEVEL: Info 
(Origin) 
PID     : 3159                 TID  : 8           PROC : db2sysc 
INSTANCE: regres5              NODE : 000         DB   : XTNDDB 
APPHDL  : 0-277                APPID: 
*LOCAL.regres5.110817201533 
AUTHID  : NEWTON 
EDUID   : 8                    EDUNAME: db2agent (XTNDDB) 
FUNCTION: DB2 UDB, SW- common services, sqlnn_cmpl, probe:650 
MESSAGE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT 
          "SQLCA has already been built" 
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: -901   sqlerrml: 25 
 sqlerrmc: predicate entry not found 
 sqlerrp : SQLRL1E4 
 sqlerrd : (1) 0x801A006D      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFFEC      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
DATA #8 : Hex integer, 4 bytes 
0x00000040 
DATA #9 : String, 167 bytes 
Compiler error stack for rc = -2145779603: 
sqlnn_cmpl[300] 
sqlnp_main[250] 
sqlnp_parser[510] 
sqlnp_smactn[100] 
sqlnq_drop_db_object[700] 
sqlnq_drop_db_object_end[290] 
 
And failing with the below call stack, which can be found in the 
FODC* directory: 
 
(11) 0xc0000000177bc590  sqlrrSqlCode + 0x260 at 
sqlrr_error.C:159 
[/view/db2_v97fp5_hpipf64_s110814/vbs/INST/lib/libdb2e.so] 
(12) 0xc000000018285870  _Z20sqlrl_delete_UDPspecP8sqlrr_cbii + 
0x310 at sqlrl_index_extension.C:2647 
[/view/db2_v97fp5_hpipf64_s110814/vbs/INST/lib/libdb2e.so] 
(13) 0xc0000000184c3ae0 
_Z11sqlrldrf_swP8sqlrr_cbPhiS1_iS1_ii18sqlrldrf_sw_callerbbb + 
0x3430 at sqlrl_function.C:7959 
[/view/db2_v97fp5_hpipf64_s110814/vbs/INST/lib/libdb2e.so] 
(14) 0xc0000000162503d0 
_Z24sqlnq_drop_db_object_end15sqlnq_ddlobjectP9sqlnq_qtbi19sqlnq 
_statementType 
+ 0x2290 at sqlnq_ddl_misc.C:7089 
[/view/db2_v97fp5_hpipf64_s110814/vbs/INST/lib/libdb2e.so] 
(15) 0xc000000016245310 
_Z20sqlnq_drop_db_objectPP8stknode_i10actiontypePhP3loc + 0x1c10 
at sqlnq_ddl_misc.C:4601 
[/view/db2_v97fp5_hpipf64_s110814/vbs/INST/lib/libdb2e.so] 
(16) 0xc0000000122a6410  _Z12sqlnp_smactnP8sqlnp_cbi + 0x2d0 at 
sqlnp_prs.C:990 
[/view/db2_v97fp5_hpipf64_s110814/vbs/INST/lib/libdb2e.so] 
(17) 0xc0000000122a3ef0  _Z12sqlnp_parserP8sqlnp_cb + 0xe90 at 
sqlnp_driver.C:1084 
[/view/db2_v97fp5_hpipf64_s110814/vbs/INST/lib/libdb2e.so] 
(18) 0xc00000001226ae90 
_Z10sqlnp_mainP12sqlnq_stringbP3locPP9sqlnq_qur + 0x2f0 at 
sqlnp_main.C:490 
[/view/db2_v97fp5_hpipf64_s110814/vbs/INST/lib/libdb2e.so]
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users trying to drop a function associated with an index * 
* extension using DB2 Version 9.7 on platforms Linux, Unix and * 
* Windows.                                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Starting in DB2 Version 9.7, when a function is being        * 
* dropped, its dependent functions will get invalidated. If    * 
* the dependent function has an index extension, dropping the  * 
* parent function will cause the index extension to be dropped * 
* from the system catalogs, syscat.predicatespecs and          * 
* syscat.indexexploitrules, during the invalidation. Thus,     * 
* when the dependent function gets dropped at a later time,    * 
* SQL0901N gets returned as the corresponding record for the   * 
* user-defined predicate specification cannot be found in the  * 
* system catalogs.                                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 Version 9.7 Fix Pack 6 or follow the local     * 
* fix.                                                         * 
****************************************************************
Local-Fix:
Drop the dependent function with the index extension first.
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
The problem was first fixed in DB2 Version 9.7 Fix Pack 6.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.09.2011
05.06.2012
05.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList