Troubleshooting
Problem
ROLLFORWARD ASKS FOR MORE LOGS THAT ARE NOT INCLUDED IN THE ONLINE BACKUP IMAGE
Symptom
Restore of an online backup with includes logs (using logtarget) requires more logs during rollforward phase.
First log archive method (LOGARCHMETH1) = TSM
The specific error is as following :
on source
db2 backup db XXXX online to . compress
(backup image included only log file S0000769.LOG and S0000770.LOG)
on target:
$ db2 restore db XXXX from . taken at 20160719201529 on
/data/db2/data/vol1,
/data/db2/data/vol2/
dbpath on /data/db2/dbpath
logtarget /data/db2/logs
newlogpath /data/db2/logs/
SQL2539W The specified name of the backup image to restore is
the same as the name of the target database. Restoring to an
existing database that is the same as the backup image database
will cause the current database to be overwritten by the backup
version.
Do you want to continue ? (y/n) y
DB20000I The RESTORE DATABASE command completed successfully.
$ db2 rollforward db XXXX to end of backup and complete
overflow log path "(/data/db2/logs/EBU500)"
SQL1268N Rollforward recovery processing has stopped because
of error "SQL2033" while retrieving log file "S0000771.LOG" for
database "XXXX" on database partition "0" and log stream "0".
(RF requires additional "S0000771.LOG" )
First log archive method (LOGARCHMETH1) = TSM
The specific error is as following :
on source
db2 backup db XXXX online to . compress
(backup image included only log file S0000769.LOG and S0000770.LOG)
on target:
$ db2 restore db XXXX from . taken at 20160719201529 on
/data/db2/data/vol1,
/data/db2/data/vol2/
dbpath on /data/db2/dbpath
logtarget /data/db2/logs
newlogpath /data/db2/logs/
SQL2539W The specified name of the backup image to restore is
the same as the name of the target database. Restoring to an
existing database that is the same as the backup image database
will cause the current database to be overwritten by the backup
version.
Do you want to continue ? (y/n) y
DB20000I The RESTORE DATABASE command completed successfully.
$ db2 rollforward db XXXX to end of backup and complete
overflow log path "(/data/db2/logs/EBU500)"
SQL1268N Rollforward recovery processing has stopped because
of error "SQL2033" while retrieving log file "S0000771.LOG" for
database "XXXX" on database partition "0" and log stream "0".
(RF requires additional "S0000771.LOG" )
Cause
In db2diag.log , we had problem initialising the vendor device which resulted the code ZRC=0x82100016=-2112880618=SQLPLFR_RC_RETRIEVE_FAILED gets returned , and finally we would fail the rollforward.
2016-07-25-07.49.12.810413+120 E46601A935 LEVEL: Error
PID : 32533 TID : 17590587945440 PROC :
db2sysc 0
INSTANCE: ***** NODE : 000 DB :xxxxx
HOSTNAME: xxxx.xxxx
EDUID : 781 EDUNAME: db2logmgr (xxxxx) 0
FUNCTION: DB2 UDB, data protection services,
sqlpInitVendorDevice, probe:1030
MESSAGE : ZRC=0x86100025=-2045771739=SQLP_MEDIA_VENDOR_DEV_ERR
"A vendor device reported a media error."
DATA #1 : String, 29 bytes
Init failed! Vendor rc info:
DATA #2 : Vendor RC, PD_DB2_TYPE_VENDOR_RC, 4 bytes
Vendor RC=0x0000000B=11 -- see DB2 API Guide for meaning.
DATA #3 : Hexdump, 48 bytes
0x00000FFC46DB5A90 : 0000 0196 3238 3520 3430 3600 0000 0000
....285 406.....
2016-07-25-07.49.13.453323+120 I49214A516 LEVEL:
Warning
PID : 32533 TID : 17590571168224 PROC :
db2sysc 0
INSTANCE: ***** NODE : 000 DB :xxxx
HOSTNAME: xxxxx.xxxxxx
EDUID : 784 EDUNAME: db2lfr.0 (****) 0
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMReadLog,
probe:5120
DATA #1 : <preformatted>
LFR Scan Num = 3
LFR Scan Caller's EDUID = 799
Return code for LFR opening file S0000771.LOG was -2112880618
2016-07-25-07.49.13.453433+120 I49731A981 LEVEL: Info
PID : 32533 TID : 17590592139744 PROC :
db2sysc 0
INSTANCE: ***** NODE : 000 DB :xxxx
APPHDL : 0-12846 APPID:*LOCAL.******.160725054826
AUTHID : ***** HOSTNAME:xxxxx.xxxxxx
EDUID : 799 EDUNAME: db2shred (****) 0
FUNCTION: DB2 UDB, recovery manager, sqlpshrEdu, probe:9999
MESSAGE : ZRC=0x82100016=-2112880618=SQLPLFR_RC_RETRIEVE_FAILED
"Log could not be retrieved"
DATA #1 : String, 25 bytes
Shredder worker finished.
DATA #2 : db2LogStreamIDType, PD_TYPE_DB2_LOG_STREAM_ID, 2 bytes
0
DATA #3 : unsigned integer, 8 bytes
31756233038
DATA #4 : unsigned integer, 8 bytes
31774604737
DATA #5 : LFS/LSN, PD_TYPE_SQLP_LFS_LSN_PAIR, 16 bytes
7173613/000000000965D4A8
DATA #6 : LFS/LSN, PD_TYPE_SQLP_LFS_LSN_PAIR, 16 bytes
0/0000000000000000
DATA #7 : Hex integer, 8 bytes
0x0000000000000040
2016-07-25-07.49.12.810413+120 E46601A935 LEVEL: Error
PID : 32533 TID : 17590587945440 PROC :
db2sysc 0
INSTANCE: ***** NODE : 000 DB :xxxxx
HOSTNAME: xxxx.xxxx
EDUID : 781 EDUNAME: db2logmgr (xxxxx) 0
FUNCTION: DB2 UDB, data protection services,
sqlpInitVendorDevice, probe:1030
MESSAGE : ZRC=0x86100025=-2045771739=SQLP_MEDIA_VENDOR_DEV_ERR
"A vendor device reported a media error."
DATA #1 : String, 29 bytes
Init failed! Vendor rc info:
DATA #2 : Vendor RC, PD_DB2_TYPE_VENDOR_RC, 4 bytes
Vendor RC=0x0000000B=11 -- see DB2 API Guide for meaning.
DATA #3 : Hexdump, 48 bytes
0x00000FFC46DB5A90 : 0000 0196 3238 3520 3430 3600 0000 0000
....285 406.....
2016-07-25-07.49.13.453323+120 I49214A516 LEVEL:
Warning
PID : 32533 TID : 17590571168224 PROC :
db2sysc 0
INSTANCE: ***** NODE : 000 DB :xxxx
HOSTNAME: xxxxx.xxxxxx
EDUID : 784 EDUNAME: db2lfr.0 (****) 0
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMReadLog,
probe:5120
DATA #1 : <preformatted>
LFR Scan Num = 3
LFR Scan Caller's EDUID = 799
Return code for LFR opening file S0000771.LOG was -2112880618
2016-07-25-07.49.13.453433+120 I49731A981 LEVEL: Info
PID : 32533 TID : 17590592139744 PROC :
db2sysc 0
INSTANCE: ***** NODE : 000 DB :xxxx
APPHDL : 0-12846 APPID:*LOCAL.******.160725054826
AUTHID : ***** HOSTNAME:xxxxx.xxxxxx
EDUID : 799 EDUNAME: db2shred (****) 0
FUNCTION: DB2 UDB, recovery manager, sqlpshrEdu, probe:9999
MESSAGE : ZRC=0x82100016=-2112880618=SQLPLFR_RC_RETRIEVE_FAILED
"Log could not be retrieved"
DATA #1 : String, 25 bytes
Shredder worker finished.
DATA #2 : db2LogStreamIDType, PD_TYPE_DB2_LOG_STREAM_ID, 2 bytes
0
DATA #3 : unsigned integer, 8 bytes
31756233038
DATA #4 : unsigned integer, 8 bytes
31774604737
DATA #5 : LFS/LSN, PD_TYPE_SQLP_LFS_LSN_PAIR, 16 bytes
7173613/000000000965D4A8
DATA #6 : LFS/LSN, PD_TYPE_SQLP_LFS_LSN_PAIR, 16 bytes
0/0000000000000000
DATA #7 : Hex integer, 8 bytes
0x0000000000000040
Resolving The Problem
db2 rollforward stop
[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Recovery - Rollforward","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.8;9.7;10.1;10.5;11.1","Edition":"Advanced Enterprise Server;Advanced Workgroup Server;Enterprise Server","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
08 December 2022
UID
swg21989608