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

Using server option DB2_REQUESTS_IO_BLOCK_BUF may cause a database forced
shutdown when SELECT from NICKNAME

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Select nicknames caused ForceDBShutdown when  server option 
DB2_REQUESTS_IO_BLOCK_BUF is added. 
In db2trace ,we could see the following messages: 
 2013-10-23-10.55.02.235018-420 I1112717E578          LEVEL: 
Severe 
PID     : 10812                TID : 47462697920832  PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000            DB   : 
FEDDB 
APPHDL  : 0-108                APPID: *N0.db2inst1.131023175322 
AUTHID  : DB2INST1             HOSTNAME: 
xxxxxxx.xxxx.xxxxx 
EDUID   : 127                  EDUNAME: db2agent (TEST) 0 
FUNCTION: DB2 UDB, global services, sqlzeMapZrc, probe:45 
MESSAGE : ZRC=0x8604000B=-2046558197=SQLD_NOENT "OBJECT DOES 
NOT EXIST" 
          DIA8412C A table "" could not be found. 
2013-10-23-10.55.02.274040-420 I1130772E882          LEVEL: 
Severe 
PID     : 10812                TID : 47462697920832  PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000            DB   : 
FEDDB 
APPHDL  : 0-108                APPID: *N0.db2inst1.131023175322 
AUTHID  : DB2INST1             HOSTNAME: 
xxxxxxx.xxxx.xxxxx 
EDUID   : 127                  EDUNAME: db2agent (TEST) 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: -980   sqlerrml: 0 
 sqlerrmc: 
 sqlerrp : SQLRI096 
 sqlerrd : (1) 0x8604000B      (2) 0x0000000B      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFE0C      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
The trap stack is: 
0        ossDumpStackTraceInternal 
1        ossDumpStackTraceV98 
2        OSSTrapFile::dumpEx 
3        sqlo_trce 
4        sqloDumpDiagInfoHandler 
5        __pthread_mutex_cond_lock 
6        pthread_kill 
7        ossPthreadKill 
8        sqloDumpEDU 
9        sqldDumpContext 
10       sqlrr_dump_ffdc 
11       sqlzeDumpFFDC 
12       sqlzeMapZrc 
13       sqlrrMapZrc 
14       sqlri_djx_rta 
15       sqlriSectInvoke 
16       sqlrr_process_fetch_request 
17       sqlrr_open 
18       sqljs_ddm_opnqry 
19       sqljsParseRdbAccessed 
20       sqljsParse 
21       sqluParseFiletmod 
22       sqluParseFiletmod 
23       sqlfGetEffectiveCAMemSize 
24       sqljsDrdaAsDriver 
25       sqeAgent::RunEDU 
26       sqzEDUObj::EDUDriver 
27       sqlzRunEDU 
28       sqloEDUEntry 
Repro steps: 
The reproduce depends on two factor, 
a) DB2_REQUESTS_IO_BLOCK_BUF is large enough, 
b) remote table's row size is small enough. 
1>. CREATE WRAPPER "MSSQLODBC3" LIBRARY 'libdb2mssql3.so' 
OPTIONS (DB2_FENCED  'Y' ) 
2>. create server mssql type mssqlserver version 2008 wrapper 
MSSQLODBC3 options(DB2_REQUESTS_IO_BLOCK_BUF  '256', node 
'<nodename>', dbname '<dbname>') 
3> .create user mapping for <username> server mssql 
options(remote_authid '<username>', remote_password 
'<password>') 
4> .create nickname n1 for mssql."<schema>"."t697" 
5>.select  c1  from n1 fetch first rows only
Problem-Zusammenfassung:
N/A
Local-Fix:
Drop the server option DB2_REQUESTS_IO_BLOCK_BUF can bypass 
this crash issue 
 
alter server <server-name> options (drop 
DB2_REQUESTS_IO_BLOCK_BUF)
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
N/A
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
19.11.2013
23.09.2014
23.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList