suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT18923 Status: Closed

SET INTEGRITY IMMEDIATE CHECKED may cause server to TERMINATE ABNORMALLY

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Issuing SET INTEGRITY IMMEDIATE CHECKED on a table that has 
indexes and XML columns may cause the DB2 server to terminate 
abnormally with the following error: 
 
SQL1034C  The database is damaged. All applications processing 
the 
      database have been stopped. 
 
Below is an example of the a db2diag.log entry from Linux: 
 
2017-01-20-12.24.48.079354-300 I120090E2091          LEVEL: Info 
PID     : 9297                 TID : 46912904358208  PROC : 
db2sysc 0 
INSTANCE: user                 NODE : 000            DB   : 
TESTDB 
APPHDL  : 0-52                 APPID: *N0.user.170120172423 
AUTHID  : USER                 HOSTNAME: hotel52 
EDUID   : 72                   EDUNAME: db2agntp (TESTDB) 0 
FUNCTION: DB2 UDB, base sys utilities, 
sqeLocalDatabase::ForceDBShutdown, probe:13769 
MESSAGE : Regular agent EDU doing ForceDBShutdown.  Force DB 
shutdown agent ID 
          is: 
DATA #1 : APPHDL, PD_TYPE_SQLZ_APPHDL, 4 bytes 
0-52 
DATA #2 : sqeApplication_acbInfo, 
PD_TYPE_sqeApplication_acbInfo, 4 bytes 
x8000 
        - SQLEINDEX 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x00002AAAABC4C269 pdLog + 0x3B9 
  [1] 0x00002AAAAD7E777E 
_ZN16sqeLocalDatabase15ForceDBShutdownEi + 0x2BE 
  [2] 0x00002AAAAD660C08 
_Z15sqldDumpContextP9sqeBsuEduiiiiiPKcPvi + 0x6F8 
  [3] 0x00002AAAAEE82319 
_Z12sqldRowFetchP8sqeAgentP8SQLD_CCBmmPP10SQLD_VALUEP8SQLZ_RIDmP 
12SQLD_ID_LISTP9SQLP_LSN8 + 0x1159 
  [4] 0x00002AAAAF0665EE _Z10sqlriFetchP8sqlrr_cbP9sqlri_taol + 
0xAE 
  [5] 0x00002AAAAF0769E5 _Z7sqlritaP8sqlrr_cb + 0x515 
  [6] 0x00002AAAACCA908F _Z8sqlrievlP8sqlrr_cb + 0x12F 
  [7] 0x00002AAAACCA8552 _Z8sqlricseP8sqlrr_cb + 0xD2 
  [8] 0x00002AAAAF0702E9 _Z8sqlriftrP8sqlrr_cb + 0xB9 
  [9] 0x00002AAAAF0697BD 
_Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x1AD 
  [10] 0x00002AAAAE401F5D _Z16sqlrr_dss_routerP8sqlrr_cb + 0x6CD 
  [11] 0x00002AAAACB92306 
_Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0x4C6 
  [12] 0x00002AAAABF33576 /home/user/sqllib/lib64/libdb2e.so.1 + 
0x1252576 
  [13] 0x00002AAAABF327B4 _Z21sqleProcessSubRequestP8sqeAgent + 
0xE4 
  [14] 0x00002AAAABF4DA5D _ZN8sqeAgent6RunEDUEv + 0x71D 
  [15] 0x00002AAAACFE8F63 _ZN9sqzEDUObj9EDUDriverEv + 0xF3 
  [16] 0x00002AAAACFE8E69 _Z10sqlzRunEDUPcj + 0x9 
  [17] 0x00002AAAACA50071 sqloEDUEntry + 0x2A1 
  [18] 0x00002AAAAABCE2A3 /lib64/libpthread.so.0 + 0x62A3 
  [19] 0x00002AAAB30E514D __clone + 0x6D
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 6                               * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 10.1 Fix Pack 6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.01.2017
02.03.2017
02.03.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)