cancel
Showing results for 
Search instead for 
Did you mean: 

Missing transaction log(s) in between file

mmangels
Discoverer
0 Kudos

I have upgrade our sql anywhere database from sybase11 to sybase17. For a week there were nog problems. The sync worked perfectly. And now we get the following error:

I. 2019-12-03 10:39:23. Scanning logs starting at offset 04932968435
I. 2019-12-03 10:39:23. Transaction log "D:/DATABASES/Qure/Central/Qure.log" starts at offset 04996889757
I. 2019-12-03 10:39:23. Processing transaction logs from directory "D:\DATABASES\Qure\Central"
I. 2019-12-03 10:39:24. Transaction log "D:\DATABASES\Qure\Central\181214AE.LOG" starts at offset 03786047856
I. 2019-12-03 10:39:24. Processing transactions from transaction log "D:\DATABASES\Qure\Central\181214AE.LOG"
I. 2019-12-03 10:39:24. Transaction log ends at offset 03787075406
E. 2019-12-03 10:39:24. Missing transaction log(s) in between file "D:\DATABASES\Qure\Central\181214AE.LOG" (ending at offset 03787075406) and file "D:\DATABASES\Qure\Central\Qure.olg" (starting at offset 04956865697).
I. 2019-12-03 10:39:24. We are looking for a transaction log file starting at offset 03787075406.

Anybody got any idea on how to fix this? Even if I add log files from backup, he keeps complaining.

former_member194571
Active Participant
0 Kudos

Did you follow the procedure for rebuilding remote databases, particularly the step to adjust the log offset of the rebuilt database (dblog -x ... -z ...)?

HTH

Volker Stöffler
DB-TecKnowledegy

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member186998
Contributor
0 Kudos

Hi Michael,

This problem corresponds to following KBA.

2869504 - dbremote does not find transaction log files

EBF3399 or later is necessary so that you fix this problem.
As for the version 17, EBF5963 is the latest now.

2381119 - About the latest version of SQL Anywhere

Thanks,
Atsushi

mmangels
Discoverer
0 Kudos

It seems it was an issue with an old remote site. After reading in the site's sync files, the offset for the next scan somehow was a lower number. After removing the remote, dbremote was able to complete the synchronization. It was strange, all de old log files were present and yet it couldn't find the correct offset.

It there anyway I can find out which remotes still need to receive data. Because I still have logs that are a year old and delete_old_logs option is set to On, but the files are not getting cleaned up.

VolkerBarth
Active Participant
0 Kudos

You can check that via the sysremoteuser system view.