home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC89032 Status: Closed

SQLI_SMP_ERR ERROR DURING ROLLBACK OF FREE PAGE OPERATION ON AN INDEX

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
During rollback of a free page operation DB2 may fail with error 
'SQLI_SMP_ERR' due to unexpectedly finding the page marked as 
used. 
 
The db2diag.log will show following severe error: 
 
2012-11-19-13.41.36.051203+060 I34708856A523      LEVEL: Severe 
PID     : 16515112             TID  : 21817       PROC : db2sysc 
0 
INSTANCE: TESTINST             NODE : 000         DB   : TESTDB 
APPHDL  : 0-38753              APPID: 
53.48.16.60.50795.121119123056 
AUTHID  : DB2ADMIN 
EDUID   : 21817                EDUNAME: db2agent (TESTDB) 0 
FUNCTION: DB2 UDB, index manager, sqliundo, probe:2310 
RETCODE : ZRC=0x87090052=-2029453230=SQLI_SMP_ERR "SMP problems" 
          DIA8573C An invalid space map page was found. 
 
The transaction being rolled back must have performed the 
following in this order: 
- updates or deletes that triggered a page merge or page 
deletion in the index and that were performed with exclusive 
access to the table 
- runstats 
- rollback 
 
The table must have 1 or more indexes that were created when the 
table was empty (or that were rebuilt when the table was empty). 
At least one of the indexes must have had less than 25 distinct 
key values for the life of the index.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.3.                             * 
****************************************************************
Local Fix:
Use db2dart /MI to mark affected indexes bad and have them 
rebuilt upon database restart or first access (based on INDEXREC 
configuration).
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
The problem is first fixed in DB2 version 10.1.0.3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.12.2012
01.10.2013
01.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList