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 IC78122 Status: Closed

SSHSCANSTOPPAGE >= SQLDLASTOBJPAGE2SCANPREWRAP ERROR IN DB2DIAG.LOG

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When online reorg is in truncate phase, a simultaneous query 
using scan sharing could fail and return a SQL0901N error. The 
timing window for this error is small and this problem is not 
likely to occur. In the db2diag.log, an error message similar to 
the following will appear: 
 
2011-07-25-06.23.52.246691-240 I28169292E2704      LEVEL: Severe 
PID    : 8690                TID  : 140733533120256PROC : 
db2sysc 
INSTANCE: svtdbm2              NODE : 000          DB  : HADR975 
APPHDL  : 0-33180              APPID: 
*LOCAL.svtdbm2.110725181848 
AUTHID  : SVTDBM2 
EDUID  : 1613                EDUNAME: db2agent (HADR975) 
FUNCTION: DB2 UDB, data management, sqldFetch, probe:7848 
MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR 
          "non-severe dms programming error" 
          DIA8532C An internal processing error has occurred. 
DATA #1 : String, 46 bytes 
sshScanStopPage >= sqldLastObjPage2ScanPreWrap 
DATA #2 : String, 9 bytes 
sqldfrd.C 
CALLSTCK: 
  [0] 0x00007FFFF13415FA pdLog + 0x18C 
  [1] 0x00007FFFF52708E1 sqlzSetAndLog901 + 0x395 
  [2] 0x00007FFFF19FB668 _Z7sqldfrdP13SQLD_DFM_WORK + 0x2084 
...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A scan sharing query could fail with SQL0901N when online    * 
* reorg is in truncate phase.                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack 5.                              * 
****************************************************************
Local Fix:
Re-run the query when online reorg is not in truncate phase.
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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

Solution
This problem was first fixed in DB2 V9.7 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.08.2011
23.12.2011
23.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList