dsmserv restore db ANR2970E

Status
Not open for further replies.
G

grax88

ADSM.ORG Member
Joined
Nov 24, 2008
Messages
12
Reaction score
0
Points
0
Location
Czech Republic
Hello, I have problem with one old (TSM 6.1 on windows 2008) installation. Database is corrupted and I am not able to recover it. I unfortunately don't have sufficient knowledge of DB2. If I put command for restore: dsmserv restore db (doesn't matter of restore timestamp), I get:
Code: 
ANR1365I Volume G:\TSM\DBBACKUP\64102980.DBV closed (end reached).
ANR4912I Database  full restore in progress and DB transaction log bytes
transferred  956,555,275.
ANR1364I Input volume G:\TSM\DBBACKUP\64102980.DBV closed.
ANR0514I Session 4 closed volume G:\TSM\DBBACKUP\64102980.DBV.
ANR0403I Session 4 ended for node $$_TSMDBMGR_$$ (DB2/NT64).
ANR0406I Session 5 started for node $$_TSMDBMGR_$$ (DB2/NT64) (Tcp/Ip
backup.dgscz.local(58260)).
ANR0403I Session 5 ended for node $$_TSMDBMGR_$$ (DB2/NT64).
ANR0498W Session 6 refused for BACKUP because restore DB is in progress.
ANR0498W Session 7 refused for FILE because restore DB is in progress.
ANR2970E Database rollforward terminated - DB2 sqlcode -1042 sqlerrmc TSMDB1
In db2diag log:
Code: 
2013-03-27-10.52.27.463000+060 I2139081051F393    LEVEL: Severe
PID     : 4624                 TID  : 4520        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000
EDUID   : 4520                 EDUNAME: db2lfr (TSMDB1)
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMReadLog, probe:5250
DATA #1 : <preformatted>
Both log paths seem to be bad, try path1. lfrCurExtNum = 24612
2013-03-27-10.52.27.479000+060 I2139081446F393    LEVEL: Severe
PID     : 4624                 TID  : 4520        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000
EDUID   : 4520                 EDUNAME: db2lfr (TSMDB1)
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMReadLog, probe:5250
DATA #1 : <preformatted>
Both log paths seem to be bad, try path1. lfrCurExtNum = 24612
2013-03-27-10.52.27.479000+060 E2139081841F450    LEVEL: Error
PID     : 4624                 TID  : 4520        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000
EDUID   : 4520                 EDUNAME: db2lfr (TSMDB1)
FUNCTION: DB2 UDB, data protection services, sqlpSearchForLogArchiveOnDisk, probe:4000
MESSAGE : ZRC=0x870F0011=-2029060079=SQLO_PATH "an invalid path"
          DIA8514C An invalid file path, "", was specified.
2013-03-27-10.52.44.499000+060 I2139082293F415    LEVEL: Info
PID     : 4624                 TID  : 5008        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000
EDUID   : 5008                 EDUNAME: db2loggr (TSMDB1)
FUNCTION: DB2 UDB, recovery manager, sqlpgSwitchFromRedoToUndo, probe:3220
DATA #1 : <preformatted>
nextLsn 00000C04A140000C at the start of log page, extent header state is 1
2013-03-27-10.52.44.499000+060 I2139082710F533    LEVEL: Info
PID     : 4624                 TID  : 4284        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000         DB   : TSMDB1
APPHDL  : 0-23                 APPID: *LOCAL.SERVER1.130327095101
AUTHID  : ADMINISTRATOR
EDUID   : 4284                 EDUNAME: db2redom (TSMDB1)
FUNCTION: DB2 UDB, recovery manager, sqlpPRecReadLog, probe:4630
DATA #1 : <preformatted>
nextLsn 00000C04A140000C rfwd_ReadLsn 00000C04A13FFFFB ExtNum 24613 firstlsn 0C04A1400000
2013-03-27-10.53.18.928000+060 I2139083245F475    LEVEL: Warning
PID     : 4624                 TID  : 4512        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000         DB   : TSMDB1
APPHDL  : 0-23                 APPID: *LOCAL.SERVER1.130327095101
AUTHID  : ADMINISTRATOR
EDUID   : 4512                 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, recovery manager, sqlpForwardRecovery, probe:1990
DATA #1 : <preformatted>
nextLsn 00000C04A140000C
2013-03-27-10.53.19.021000+060 E2139083722F519    LEVEL: Info
PID     : 4624                 TID  : 4512        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000         DB   : TSMDB1
APPHDL  : 0-23                 APPID: *LOCAL.SERVER1.130327095101
AUTHID  : ADMINISTRATOR
EDUID   : 4512                 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:2120
MESSAGE : ADM1605I  DB2 is invoking the backward phase of database rollforward 
          recovery.
2013-03-27-10.53.19.021000+060 I2139084243F525    LEVEL: Warning
PID     : 4624                 TID  : 4512        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000         DB   : TSMDB1
APPHDL  : 0-23                 APPID: *LOCAL.SERVER1.130327095101
AUTHID  : ADMINISTRATOR
EDUID   : 4512                 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, recovery manager, sqlpForwardRecovery, probe:2210
DATA #1 : <preformatted>
Invoking database rollforward backward recovery, nextLsn: 00000C04A140000C
2013-03-27-10.53.19.037000+060 I2139084770F517    LEVEL: Info
PID     : 4624                 TID  : 4512        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000         DB   : TSMDB1
APPHDL  : 0-23                 APPID: *LOCAL.SERVER1.130327095101
AUTHID  : ADMINISTRATOR
EDUID   : 4512                 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, recovery manager, sqlpForwardRecovery, probe:2350
MESSAGE : Rollforward is completing.  New log chain is:
DATA #1 : unsigned integer, 4 bytes
4
2013-03-27-10.55.04.805000+060 I2139085289F355    LEVEL: Error
PID     : 4624                 TID  : 5008        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000
EDUID   : 5008                 EDUNAME: db2loggr (TSMDB1)
FUNCTION: DB2 UDB, data protection services, sqlpgarl, probe:2160
MESSAGE : Log 24612 seems to be bad on both paths
2013-03-27-10.55.04.852000+060 I2139085646F490    LEVEL: Error
PID     : 4624                 TID  : 4512        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000         DB   : TSMDB1
APPHDL  : 0-23                 APPID: *LOCAL.SERVER1.130327095101
AUTHID  : ADMINISTRATOR
EDUID   : 4512                 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, data protection services, sqlpgPostLoggrWithoutLatching, probe:930
MESSAGE : db2logger: rc=-2028994531 sem rc=0 type=6
2013-03-27-10.55.04.852000+060 I2139086138F182    LEVEL: Error
PID:4624 TID:4512 NODE:000 Title: SQLP_DBCB
Dump File:C:\ProgramData\IBM\DB2\DB2TSM1\SERVER1\4624.4512.000.dump.bin
2013-03-27-10.55.04.883000+060 I2139086322F569    LEVEL: Severe
PID     : 4624                 TID  : 4512        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000         DB   : TSMDB1
APPHDL  : 0-23                 APPID: *LOCAL.SERVER1.130327095101
AUTHID  : ADMINISTRATOR
EDUID   : 4512                 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, data protection services, sqlpgrlg, probe:2320
DATA #1 : <preformatted>
Error -2028994531 when reading LSN 00000C0499004A50 from log file S0024612.LOG tellMe 0 dpsAcbFlags 400 setSkipOutputBuf 1
2013-03-27-10.55.04.883000+060 I2139086893F558    LEVEL: Error
PID     : 4624                 TID  : 4512        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000         DB   : TSMDB1
APPHDL  : 0-23                 APPID: *LOCAL.SERVER1.130327095101
AUTHID  : ADMINISTRATOR
EDUID   : 4512                 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, data protection services, sqlpgrlg, probe:2320
RETCODE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic Error"
          DIA8526C A fatal error occurred in data protection services.
2013-03-27-10.55.04.899000+060 I2139087453F558    LEVEL: Error
PID     : 4624                 TID  : 4512        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000         DB   : TSMDB1
APPHDL  : 0-23                 APPID: *LOCAL.SERVER1.130327095101
AUTHID  : ADMINISTRATOR
EDUID   : 4512                 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, data protection services, sqlptudo, probe:1010
RETCODE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic Error"
          DIA8526C A fatal error occurred in data protection services.
2013-03-27-10.55.04.899000+060 I2139088013F552    LEVEL: Warning
PID     : 4624                 TID  : 4512        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000         DB   : TSMDB1
APPHDL  : 0-23                 APPID: *LOCAL.SERVER1.130327095101
AUTHID  : ADMINISTRATOR
EDUID   : 4512                 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, data protection services, sqlptudo, probe:4350
MESSAGE : LSN being undone: 
DATA #1 : Hexdump, 8 bytes
0x000007FFA5591EC0 : 0000 0C04 9900 4A50                        ......JP
2013-03-27-10.55.04.899000+060 I2139088567F184    LEVEL: Error
PID:4624 TID:4512 NODE:000 Title: SQLP_TENTRY
Dump File:C:\ProgramData\IBM\DB2\DB2TSM1\SERVER1\4624.4512.000.dump.bin
2013-03-27-10.55.04.899000+060 I2139088753F181    LEVEL: Error
PID:4624 TID:4512 NODE:000 Title: sqeAgent
Dump File:C:\ProgramData\IBM\DB2\DB2TSM1\SERVER1\4624.4512.000.dump.bin
2013-03-27-10.55.04.899000+060 I2139088936F182    LEVEL: Error
PID:4624 TID:4512 NODE:000 Title: SQLP_DBCB
Dump File:C:\ProgramData\IBM\DB2\DB2TSM1\SERVER1\4624.4512.000.dump.bin
2013-03-27-10.55.04.899000+060 I2139089120F181    LEVEL: Error
PID:4624 TID:4512 NODE:000 Title: SQLP_ACB
Dump File:C:\ProgramData\IBM\DB2\DB2TSM1\SERVER1\4624.4512.000.dump.bin
2013-03-27-10.55.04.899000+060 E2139089303F548    LEVEL: Error
PID     : 4624                 TID  : 4512        PROC : db2syscs.exe
INSTANCE: SERVER1              NODE : 000         DB   : TSMDB1
APPHDL  : 0-23                 APPID: *LOCAL.SERVER1.130327095101
AUTHID  : ADMINISTRATOR
EDUID   : 4512                 EDUNAME: db2agent (TSMDB1)
FUNCTION: DB2 UDB, recovery manager, sqlprudm, probe:40
RETCODE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic Error"
          DIA8526C A fatal error occurred in data protection services.
It seems that some log file is corrupted? Am I able to restore db without it? Thank you
 
I suggest get someone experienced with TSM do do this. You need to;
Identify the latest DB backup volume from the volume history file
remove the existing tsmdb2 database prior to restore.
dsmserv removedb tsmdb1
(cleanup the old archlog and log database dirs)
Then try restore again
 
tsm_dude said:
I suggest get someone experienced with TSM do do this. You need to;
Identify the latest DB backup volume from the volume history file
remove the existing tsmdb2 database prior to restore.
dsmserv removedb tsmdb1
(cleanup the old archlog and log database dirs)
Then try restore again
Click to expand...

Thank you, I've solved it by restoring database to date one day before crash. Then I must audit all volumes to sync it with db content.
 
Status
Not open for further replies.

Data Privacy Impact Assessment

Compliance Assurance in Every Byte: Discover the Impact of Our DPIA Services.

Sponsor ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

Navigation Menu

Forums
   IBM TSM
   EMC Backup and Recovery
   Symantec NetBackup  
   SAN  
   NAS
   Platforms / OS
Mailing List Archives
   ADSM-L
User Groups

NordVPN 3 Months FREE

Help Support ADSM.ORG and Get NordVPN with 64% Off and 3 Months FREE.

NordVPN with 64% off + 3 months FREE

Forum statistics

Threads
31,974
Messages
135,448
Members
21,953
Latest member
jrogers
Back
Top