DB2 - Problembeschreibung
Problem IT28200 | Status: Geschlossen |
SEGV or SQL0901N (UNKNOWN DYNAMICRULES) MAY BE RETURNED DURING APREPARE OR A SQL1803N MAY BE RETURNED DURING A BIND OR REBIND | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problembeschreibung: | |
Due to a timing issue in package cache logic a number of different symptoms may result during the running of one of the NULLID.SYS* packages (used for CLI/Java/JDBC apps): 1) A sig-segv due to access to a stale pointer to a package entry in the package cache may occur during prepare or other processing. A trap might have the following calling stack included: [3] 0x0900000011B89A74 sqlra_cache_fill_pkg__FP8sqlrr_cbP20sqlra_cached_package + 0x1D94 [4] 0x0900000010678D74 sqlra_find_pkg__FP8sqlrr_cbPUcsT2T3T2T3iUlP14SQLP_LOCK_INFOPP20s qlra_cached_packagePUl + 0x12B4 [5] 0x0900000010687094 sqlra_open_pkg__FP8sqlrr_cbPUcsT2T3T2b + 0x4D4 [6] 0x0900000010697360 sqlra_load_pkg__FP8sqlrr_cbPUcsT2T3T2bT7 + 0x780 [7] 0x0900000013399004 sqlra_get_section__FP8sqlrr_cbPUcsT2T3T2UsUlP16db2UCprepareInfoP 15db2UCCursorInfoiUi + 0x8E4 [8] 0x0900000011B09F74 sqlrr_sql_request_pre__FP14db2UCinterfaceUiiP16db2UCprepareInfoP 15db2UCCursorInfo + 0x1A74 [9] 0x090000001088DA5C sqlrr_prepare__FP14db2UCinterfaceP16db2UCprepareInfo + 0x41C 2) FODC_Apperr dumps maybe generated and SQL0901n error may be returned during a package re-compilation. The entries in db2diag.log may look as follows: 019-01-08-05.29.46.858436-300 I17268A900 LEVEL: Severe PID : 12845140 TID : 32177 PROC : db2sysc 0 INSTANCE: idb2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-8490 APPID: 192.0.0.1.60320.190212180624 AUTHID : db2inst1 HOSTNAME: localhost EDUID : 32177 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:300 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 28 sqlerrmc: Unknown DYNAMICRULES option! sqlerrp : SQLRA0E8 sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFFF9C (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: db2 stack dump of the process may look as follows: -------Frame------ ------Function + Offset------ 0x09000000004ECF14 pthread_kill + 0xD4 0x090000001E97FFFC sqloDumpEDU + 0x9C 0x090000001F5AD2B0 sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2 + 0x150 0x09000000208C2B34 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x914 0x090000001EADDE38 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x158 0x090000001EADD91C sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc + 0x27C 0x090000001EADA40C sqlrrSqlCode + 0x18C 0x0900000021A4A888 sqlra_set_stmt_authid_dynrules__FP8sqlrr_cb + 0x228 0x0900000021A4900C sqlra_get_section__FP8sqlrr_cbPUcsT2T3T2UsUlP16db2UCprepareInfoP 15db2UCCursorInfoiUi + 0x420C 0x0900000022E1BBEC sqlrr_sql_request_pre__FP14db2UCinterfaceUiiP16db2UCprepareInfoP 15db2UCCursorInfo + 0x8EC 0x090000002036ADF8 sqlrr_prepare__FP14db2UCinterfaceP16db2UCprepareInfo + 0x398 0x0900000022E460D4 sqlrrProcessDeferredPrepare__FCP8sqlrr_cbCP14db2UCinterface + 0x274 0x0900000022E1CFF0 sqlrr_sql_request_pre__FP14db2UCinterfaceUiiP16db2UCprepareInfoP 15db2UCCursorInfo + 0x1CF0 db2 instance is not stopped due to this. The error eventually goes away during next recompile. 3) SQL1803N can be reported during the bind or rebind of db2ubind.lst or the NULLID.SYS* packages or while running db2rbind. This error reports that the package is not in use even though the package might be in use | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * **************************************************************** | |
Local-Fix: | |
No Local Fix for the SQL0901N error or the trap For the SQL1803N error, deactivating and then activating the database should clear the problem and allow the bind/rebind to succeed This APAR fix will also add additional checks and some additional dumps in case the error is returned from an unidentified condition. | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 22.02.2019 16.01.2020 16.01.2020 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version |