| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC67505 | Status: Closed |
TABLESPACE MARKED OFFLINE DURING DATABASE ACTIVATION | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
The problem is whenever there is inconsistency between the
on-disk tablespace data (pool page 0) and the size of the
tablespace, the tablespace will be marked OFFLINE during
database activation. The purpose of the APAR is to improve the
fault tolerance of the database activation codepath by for
example checking whether the inconsistency can be detected and
amended and let database activation continues.
Customers will see the following db2diag.log messages if the
problem happens:
2010-01-18-21.12.39.714506+060 I96871481A799 LEVEL: Severe
PID : 15982 TID : 25 PROC : db2sysc
0
INSTANCE: db2pc1 NODE : 000 DB : PC1
APPHDL : 0-52 APPID: *LOCAL.db2pc1.100118201138
AUTHID : DB2PC1
EDUID : 25 EDUNAME: db2agent (PC1) 0
FUNCTION: DB2 UDB, buffer pool services,
sqlbFindNewHighWaterMark, probe:20
MESSAGE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not
exist"
DIA8506C Unexpected end of file was reached.
DATA #1 : Page ID, PD_TYPE_SQLB_PAGE_ID, 4 bytes
2144001
DATA #2 : Pool ID, PD_TYPE_SQLB_POOL_ID, 2 bytes
50
DATA #3 : Page ID, PD_TYPE_SQLB_PAGE_ID, 4 bytes
2144001
DATA #4 : Page ID, PD_TYPE_SQLB_PAGE_ID, 4 bytes
2144000
DATA #5 : Codepath, 8 bytes
1:3:4:60:64
2010-01-18-21.12.39.714936+060 I96872281A529 LEVEL: Error
PID : 15982 TID : 25 PROC : db2sysc
0
INSTANCE: db2pc1 NODE : 000 DB : PC1
APPHDL : 0-52 APPID: *LOCAL.db2pc1.100118201138
AUTHID : DB2PC1
EDUID : 25 EDUNAME: db2agent (PC1) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbDMSStartPool,
probe:7107
MESSAGE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not
exist"
DIA8506C Unexpected end of file was reached. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * Failure to activate database when there is a minor * * inconsistency in tablespace data. * **************************************************************** * RECOMMENDATION: * * Upgrade the database server to V9.7 Fixpack 4 * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
| Solution | |
This apar was first fixed in V9.7 Fixpak 4 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.03.2010 19.05.2011 19.05.2011 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7., 9.7.FP4 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.4 |
|