|
Problem IC98024
|
Status: Closed |
IN PURESCALE ENV ROLLFORWARD ON MEMBER X WON'T FETCH LOGS FROM TSM FOR OTHER MEMBERS WHEN RESTORING TO NEW DATABASE NAME |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
After a restore using INTO clause for new database name,
rollforward from member X will fetch logs from TSM that
belong to members X only. This happens even when utilizing the
--DBNAME option in the LOGARCHOPT1 database configuration
parameter. eg.) update db cfg for <newDBname> using LOGARCHOPT1
"--DBNAME=<oldDBname>"'.
You will see the following error when performing rollforward
from member 0:
----------------------------------------------------------------
---------------------------------------------------------
When issued from the member 0, we can not find the logs for
member 1
----------------------------------------------------------------
----------------------------------------------------------
==> db2 rollforward db testdb to '2013-10-03-08.48.00' using
local time and stop
SQL1273N An operation reading the logs on database "TESTDB"
cannot continue
because of a missing log file "S0000041.LOG" on database
partition "0" and log
stream "1".
----------------------------
db2diag.log message:
----------------------------
2013-10-09-14.04.40.818273-300 E420156A681 LEVEL: Error
PID : 36307116 TID : 135631 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
TESTDB
APPHDL : 0-55362 APPID: *N0.db2dsg01.131009190212
AUTHID : DB2INST1 HOSTNAME: testserv
EDUID : 135631 EDUNAME: db2redom (TESTDB) 0
FUNCTION: DB2 UDB, data protection services,
sqlpEnsureShredderIsProcessingCorrectExtent, probe:200
MESSAGE : ADM1601E A recovery or rollforward operation on
database "TESTDB"
cannot continue because of a missing log file
"S0000041.LOG" on
database partition "0" and log stream "1".
2013-10-09-14.04.40.837851-300 I420838A2221 LEVEL:
Severe
PID : 36307116 TID : 135631 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
TESTDB
APPHDL : 0-55362 APPID: *N0.db2dsg01.131009190212
AUTHID : DB2INST1 HOSTNAME: testserv
EDUID : 135631 EDUNAME: db2redom (TESTDB) 0
FUNCTION: DB2 UDB, data protection services,
sqlpEnsureShredderIsProcessingCorrectExtent, probe:200
DATA #1 : <preformatted>
Missing log detected on log stream 1.
Missing log file is S0000041.LOG. The log stream and LSO which
detected the problem will be logged by one of the
calling functions who has access to the log record we are
processing (which should be sqlpPerformMissingLogDetection).
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x09000000321552FC pdLogPrintf + 0x28
[1] 0x0900000033BBE280
sqlpEnsureShredderIsProcessingCorrectExtent__FP14sqlpMasterDbcbP
17SQLPSHR_MASTER_CBUsUiCUl + 0x29C
[2] 0x0900000033BBD2AC
sqlpVerifyGFA__FP14sqlpMasterDbcbP17SQLPSHR_MASTER_CBP17SQLPSHR_
WORKER_CBP8SQLP_GFACbCUlT6 + 0x178
[3] 0x0900000033BBF87C
sqlpVerifyGFALogRecord__FP14sqlpMasterDbcbP17SQLPSHR_MASTER_CBP1
7SQLPSHR_WORKER_CBP16SQLPR_LOGREC_DISCbCUl + 0xD0
[4] 0x0900000033BBFA98
sqlpPerformMissingLogDetection__FP14sqlpMasterDbcbP17SQLPSHR_MAS
TER_CBP17SQLPSHR_WORKER_CBP16SQLPR_LOGREC_DISUl + 0xE4
[5] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF
[6] 0x09000000307069B0
sqlpshrScanNext__FPvP8sqeAgentUlPP16SQLPR_LOGREC_DISPUl + 0x4D50
[7] 0x0900000030702A28
sqlpshrScanNext__FPvP8sqeAgentUlPP16SQLPR_LOGREC_DISPUl + 0xDC8
[8] 0x09000000306CC0A4
sqlpshrScanNext__FPvP8sqeAgentUlPP16SQLPR_LOGREC_DISPUl + 0x1CEC
[9] 0x0900000033546800
sqlpPRecReadLog__FP8sqeAgentP8SQLP_ACBP14sqlpMasterDbcb + 0x1AF0
[10] 0x0900000031422FC0 RunEDU__8sqeAgentFv + 0xF380
[11] 0x090000003141F63C RunEDU__8sqeAgentFv + 0xB9FC
[12] 0x09000000313A2624 RunEDU__8sqeAgentFv + 0xD8
[13] 0x090000003214F10C EDUDriver__9sqzEDUObjFv + 0x110
[14] 0x09000000313CEC78 sqloEDUEntry + 0x38C
[15] 0x09000000004D4D90 _pthread_body + 0xF0
[16] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 fp4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.1 fp 4. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC99065
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.11.2013
25.08.2014
25.08.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
