Log Corruption - V 7.2 on Windows 2000 server - has anyone seen this?
This is a discussion on Log Corruption - V 7.2 on Windows 2000 server - has anyone seen this? within the DB2 forums, part of the Database Server Software category; --> I have fixpack 9 applied. Some of the transaction logs get corrupted, when I try to do a rollforward ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-26-2008, 11:02 AM
| ||||
| ||||
 Log Corruption - V 7.2 on Windows 2000 server - has anyone seen this? I have fixpack 9 applied. Some of the transaction logs get corrupted, when I try to do a rollforward on a standby machine I get the following: 2003-07-17-16.42.49.502000 Instance  B2 Node:000PID:532(db2syscs.exe) TID:1272 Appid:*LOCAL.DB2.030717223120 data_protection sqlpRedoInitReadLog Probe:30 Database:APPDATA DIA3714C Logging can not continue due to an error. ZRC=0xFFFFE50D 2003-07-17-16.42.49.502001 Instance B2 Node:000PID:532(db2syscs.exe) TID:1272 Appid:*LOCAL.DB2.030717223120 data_protection sqlpgrlg Probe:40 Database:APPDATA Error -6899 when reading LSN 0A30 C19C C00C from log file S0393644.LOG 2003-07-17-16.42.49.512000 Instance B2 Node:000PID:532(db2syscs.exe) TID:1272 Appid:*LOCAL.DB2.030717223120 data_protection sqlpgrlg Probe:40 Database:APPDATA DIA3714C Logging can not continue due to an error. ZRC=0xFFFFE50D 2003-07-17-16.42.49.522000 Instance B2 Node:000PID:532(db2syscs.exe) TID:1272 Appid:*LOCAL.DB2.030717223120 recovery_manager sqlpPRecReadLog Probe:50 Database:APPDATA DIA3714C Logging can not continue due to an error. ZRC=0xFFFFE50D 2003-07-17-16.42.49.542000 Instance B2 Node:000PID:532(db2syscs.exe) TID:1312 Appid:*LOCAL.DB2.030717223120 data_protection sqlufrol Probe:1500 Database:APPDATA Roll Forward Error: 0de5 ffff .åÿÿ 2003-07-17-16.42.49.552000 Instance B2 Node:000PID:532(db2syscs.exe) TID:1312 Appid:*LOCAL.DB2.030717223120 data_protection sqlufrol Probe:130 Database:APPDATA Rollforward iteration completed      |
|
02-26-2008, 11:02 AM
| |||
| |||
| Re: Log Corruption - V 7.2 on Windows 2000 server - has anyone seenthis? It looks like that the log files in your source db server is OK. Try to copy the log file - S0393644.LOG to the standby db server and try again. Regards, FRX Ken Light wrote: > I have fixpack 9 applied. > > Some of the transaction logs get corrupted, when I try to do a > rollforward on a standby machine I get the following: > > 2003-07-17-16.42.49.502000 Instance B2 Node:000> PID:532(db2syscs.exe) TID:1272 Appid:*LOCAL.DB2.030717223120 > data_protection sqlpRedoInitReadLog Probe:30 Database:APPDATA > DIA3714C Logging can not continue due to an error. > > ZRC=0xFFFFE50D > > 2003-07-17-16.42.49.502001 Instance B2 Node:000> PID:532(db2syscs.exe) TID:1272 Appid:*LOCAL.DB2.030717223120 > data_protection sqlpgrlg Probe:40 Database:APPDATA > > Error -6899 when reading LSN 0A30 C19C C00C from log file S0393644.LOG > > 2003-07-17-16.42.49.512000 Instance B2 Node:000> PID:532(db2syscs.exe) TID:1272 Appid:*LOCAL.DB2.030717223120 > data_protection sqlpgrlg Probe:40 Database:APPDATA > DIA3714C Logging can not continue due to an error. > > ZRC=0xFFFFE50D > > 2003-07-17-16.42.49.522000 Instance B2 Node:000> PID:532(db2syscs.exe) TID:1272 Appid:*LOCAL.DB2.030717223120 > recovery_manager sqlpPRecReadLog Probe:50 Database:APPDATA > DIA3714C Logging can not continue due to an error. > > ZRC=0xFFFFE50D > > 2003-07-17-16.42.49.542000 Instance B2 Node:000> PID:532(db2syscs.exe) TID:1312 Appid:*LOCAL.DB2.030717223120 > data_protection sqlufrol Probe:1500 Database:APPDATA > > Roll Forward Error: 0de5 ffff .åÿÿ > > 2003-07-17-16.42.49.552000 Instance B2 Node:000> PID:532(db2syscs.exe) TID:1312 Appid:*LOCAL.DB2.030717223120 > data_protection sqlufrol Probe:130 Database:APPDATA > > Rollforward iteration completed |
|
02-26-2008, 11:03 AM
| |||
| |||
| Re: Log Corruption - V 7.2 on Windows 2000 server - has anyone seen this? Fan: Thanks for your help. I transferred the log again, the same problem arose. I restored the backup and rolled forward again, the same problem. I suspect that the log may be corrupt. I cannot find what errorcode -6899 means. Anyone else have any idea? Fan Ruo Xin <fanruox@sbcglobal.net> wrote in message news:<3F1C80A6.64A015D6@sbcglobal.net>... > It looks like that the log files in your source db server is OK. Try to > copy the log file - S0393644.LOG to the standby db server and try again. > Regards, > FRX > |
|
02-26-2008, 11:03 AM
| ||||
| ||||
| Re: Log Corruption - V 7.2 on Windows 2000 server - has anyone seenthis? Ken Light wrote: > Fan: > > Thanks for your help. > I transferred the log again, the same problem arose. I restored the > backup and rolled forward again, the same problem. I suspect that the > log may be corrupt. I cannot find what errorcode -6899 means. > Anyone else have any idea? Troubleshooting Guide Part 3. Appendixes -------------------------------------------------------------------------------- Appendix A. DB2 Internal Return Codes .... E50D -980 13 Bad log file I think the log file got corrupt after this file become archived log files, otherwise you can find information in db2diag.log in source db server. > > > Fan Ruo Xin <fanruox@sbcglobal.net> wrote in message news:<3F1C80A6.64A015D6@sbcglobal.net>... > > It looks like that the log files in your source db server is OK. Try to > > copy the log file - S0393644.LOG to the standby db server and try again. > > Regards, > > FRX > > |
Linear Mode
