DB2 - Problem description
| Problem IC94033 | Status: Closed |
ROLLFORWARD FOLLOWING RESTORE FROM ONLINE BACKUP IMAGE FAILS WITH BAD PAGE AND SQL1271W IN DB2 PURESCALE ENVIRONMENT | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
A rollforward operation following a database restore from an
online backup image taken in DB2 pureScale environment fails
with a bad page error followed by SQL1271W (one or more table
spaces offline) if another member was running an uncommitted
CREATE TABLESPACE statement while the online backup was in
progress.
Steps to reproduce:
member 0: db2 +c create tablespace ts1
member 1: db2 backup db sample online
member 0: db2 terminate
member 1: db2 restore db sample replace existing without
prompting
member 1: db2 rollforward db sample to end of logs and stop
Screenshot of the last step:
rollforward db sample to end of logs and stop
SQL1271W Database "SAMPLE" is recovered but one or more table
spaces are
offline on members or nodes "0".
DB2 diagnostic log:
2013-06-28-16.32.09.800563-240 I3309685E4681 LEVEL:
Severe
PID : 6471 TID : 46914317838656 KTID :
32122
PROC : db2sysc 1
INSTANCE: db2inst1 NODE : 001 DB :
SAMPLE
APPHDL : 1-75 APPID: *N1.db2inst1.130628203203
AUTHID : DB2INST1 HOSTNAME: myhost
EDUID : 230 EDUNAME: db2redow (SAMPLE) 1
FUNCTION: DB2 UDB, buffer pool services, sqlb_verify_page,
probe:3
MESSAGE : ZRC=0x86020001=-2046689279=SQLB_BADP "page is bad"
DIA8400C A bad page was encountered.
DATA #1 : String, 64 bytes
Error encountered trying to read a page - information follows :
DATA #2 : String, 23 bytes
Page verification error
DATA #3 : Page ID, PD_TYPE_SQLB_PAGE_ID, 4 bytes
1
DATA #4 : Object descriptor, PD_TYPE_SQLB_OBJECT_DESC, 96 bytes
Obj: {pool:3;obj:65535;type:64} Parent={3;65535}
<...skipping...>
DATA #6 : Page header, PD_TYPE_SQLB_PAGE_HEAD, 48 bytes
pageHead: {tbspSeed:3402287818;obj:51914;type:202}
PPNum:3402287818 OPNum:3402287818
begoff: 51914
datlen: 51914
pagebinx: 3402287818
revnum: 51914
pagelsn: CACACACACACACACA
flag: ca
future32: 3402287818
cbits1to31: cacacaca
cbits32to63: cacacaca
<...skipping...>
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] pdLog + 0x230
[1] sqlbLogReadAttemptFailure + 0x1FC
[2] sqlb_verify_page + 0x1061
[3] sqlbReadPage + 0xBAB
[4] sqlbGetPageFromDisk + 0x13DE
[5] sqlbfix + 0x4B70
[6] sqlbFixPage + 0x33A
[7] /home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0x28BE754
[8] sqlbRedo + 0xBBF
[9] sqldmrdo + 0xD22
<...skipping...>
2013-06-28-16.32.09.847165-240 E3314367E1028 LEVEL:
Critical
PID : 6471 TID : 46914317838656 KTID :
32122
PROC : db2sysc 1
INSTANCE: db2inst1 NODE : 001 DB :
SAMPLE
APPHDL : 1-75 APPID: *N1.db2inst1.130628203203
AUTHID : DB2INST1 HOSTNAME: myhost
EDUID : 230 EDUNAME: db2redow (SAMPLE) 1
FUNCTION: DB2 UDB, buffer pool services,
sqlbLogReadAttemptFailure, probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred: "BadPage".
The instance may have been shutdown as a result.
"Automatic" FODC
(First Occurrence Data Capture) has been invoked
<...skipping...>
2013-06-28-16.32.22.342210-240 I3388865E728 LEVEL:
Warning
PID : 6471 TID : 46913088907584 KTID :
29947
PROC : db2sysc 1
INSTANCE: db2inst1 NODE : 001 DB :
SAMPLE
APPHDL : 1-75 APPID: *N1.db2inst1.130628203203
AUTHID : DB2INST1 HOSTNAME: myhost
EDUID : 91 EDUNAME: db2agent (SAMPLE) 1
FUNCTION: DB2 UDB, recovery manager, sqlpCheckTablespaces,
probe:350
MESSAGE : ZRC=0x801000AB=-2146434901=SQLP_TRCVIOERR
"Recovery completed with I/O errors."
DIA8178E During forward recovery one or more of the
tablespaces
received an error.
DATA #1 : <preformatted>
Rollforward failed for tablespace 3.
2013-06-28-16.32.22.359315-240 I3389594E552 LEVEL: Info
PID : 6471 TID : 46913088907584 KTID :
29947
PROC : db2sysc 1
INSTANCE: db2inst1 NODE : 001 DB :
SAMPLE
APPHDL : 1-75 APPID: *N1.db2inst1.130628203203
AUTHID : DB2INST1 HOSTNAME: myhost
EDUID : 91 EDUNAME: db2agent (SAMPLE) 1
FUNCTION: DB2 UDB, data protection services, sqlufrol,
probe:1289
MESSAGE : logErrorStreamId was not set in dbcb
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
1271 | |
| Problem Summary: | |
See Problem Description | |
| Local Fix: | |
Ensure that all CREATE TABLESPACE statements have been committed before starting an online database backup | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
Problem first fixed in IBM DB2 10.1 for Linux, UNIX, and Windows Fix Pack 3 | |
| Workaround | |
See Problem Description | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.07.2013 21.10.2013 21.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 |
|
| 10.1.0.3 |
|