SQL Anywhere database replication - Error writing to transaction log file

Author

Error writing to transaction log file

Brian Greiman

2005-08-05, 11:23 am

ASA 9.01.1964

The other day, we received a error message "Error writing to transaction log
file" with dbremote. We have seen several of these in the past as well. We
have found that we immediately need to re-start database at this point or
transactions will not get written to log files, replicated, and so on.

Here are excerpts from the dbremote runs. It looks like the rename of the
log files worked fine (we use -x parameter with dbremote):

I. 08/02 15:08:43. Processing transaction logs from directory
"\\csr01\f\bersys"
I. 08/02 15:08:52. Transaction log " \\csr01\f\bersys\050
802AZ.LOG" starts at
offset 0591103572529
I. 08/02 15:08:52. Processing transactions from transaction log
" \\csr01\f\bersys\050
802AZ.LOG"
I. 08/02 15:08:54. Transaction log ends at offset 0591107416366
I. 08/02 15:08:54. Processing transactions from active transaction log
I. 08/02 15:08:54. Sending message to "dbo"
(17-0591107416226-0591107452521-0)
I. 08/02 15:08:58. Sending message to "dbo"
(17-0591107452521-0591114772398-0)
I. 08/02 15:09:19. Sending message to "dbo"
(17-0591114772398-0591139916566-0)
I. 08/02 15:09:24. Sending message to "dbo"
(17-0591139916566-0591145633012-0)
I. 08/02 15:09:37. Transaction log renamed to: f:\bersys\050802BA.LOG
I. 08/02 15:09:37. Sending message to "dbo"
(17-0591145633012-0591159841423-0)
I. 08/02 15:09:39. Execution completed

I. 08/02 15:10:26. Scanning logs starting at offset 0591159841423
I. 08/02 15:10:26. Processing transaction logs from directory
"\\csr01\f\bersys"
I. 08/02 15:10:35. Processing transactions from active transaction log
E. 08/02 15:10:36. Error writing to transaction log file
E. 08/02 15:10:36. Sending messages failed
I. 08/02 15:10:36. Execution completed

Can anybody give me any insight on what might be going wrong and causing
this error? We would like to prevent any data loss in the future.

Thanks,
Brian Greiman

Reg Domaratzki $iAnywhere Solutions$

2005-08-05, 11:23 am

You might be running into the bug fixed in QTS 398132. The bug fix was put
into v803.5277, v901.2049 and v902.3157. A version 901 build 2052 for
windows EBF was just posted yesterday, so the fix should be available for
you.

Customer Description:
If a backup of the database was being performed and the transaction log was
either being renamed or truncated, if the database engine was unable to open
a new transaction log ( or transaction log mirror ) after deleting or
renaming, an error would be returned to the backup process, but it was
possible that the engine would continue to apply operations without logging
them to the transaction log. The engine will now throw an assertion when it
cannot open the new transaction log ( or mirror ) after the truncation or
rename, as this should be a fatal error for the database engine.

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL

"Brian Greiman" <bgreiman@bernicks.com> wrote in message
news:42f3769c$1@foru
ms-2-dub...
> ASA 9.01.1964
>
> The other day, we received a error message "Error writing to transaction
log
> file" with dbremote. We have seen several of these in the past as well.
We
> have found that we immediately need to re-start database at this point or
> transactions will not get written to log files, replicated, and so on.
>
> Here are excerpts from the dbremote runs. It looks like the rename of the
> log files worked fine (we use -x parameter with dbremote):
>
> I. 08/02 15:08:43. Processing transaction logs from directory
> "\\csr01\f\bersys"
> I. 08/02 15:08:52. Transaction log " \\csr01\f\bersys\050
802AZ.LOG" starts
at
> offset 0591103572529
> I. 08/02 15:08:52. Processing transactions from transaction log
> " \\csr01\f\bersys\050
802AZ.LOG"
> I. 08/02 15:08:54. Transaction log ends at offset 0591107416366
> I. 08/02 15:08:54. Processing transactions from active transaction log
> I. 08/02 15:08:54. Sending message to "dbo"
> (17-0591107416226-0591107452521-0)
> I. 08/02 15:08:58. Sending message to "dbo"
> (17-0591107452521-0591114772398-0)
> I. 08/02 15:09:19. Sending message to "dbo"
> (17-0591114772398-0591139916566-0)
> I. 08/02 15:09:24. Sending message to "dbo"
> (17-0591139916566-0591145633012-0)
> I. 08/02 15:09:37. Transaction log renamed to: f:\bersys\050802BA.LOG
> I. 08/02 15:09:37. Sending message to "dbo"
> (17-0591145633012-0591159841423-0)
> I. 08/02 15:09:39. Execution completed
>
>
> I. 08/02 15:10:26. Scanning logs starting at offset 0591159841423
> I. 08/02 15:10:26. Processing transaction logs from directory
> "\\csr01\f\bersys"
> I. 08/02 15:10:35. Processing transactions from active transaction log
> E. 08/02 15:10:36. Error writing to transaction log file
> E. 08/02 15:10:36. Sending messages failed
> I. 08/02 15:10:36. Execution completed
>
> Can anybody give me any insight on what might be going wrong and causing
> this error? We would like to prevent any data loss in the future.
>
> Thanks,
> Brian Greiman
>
>
>
>

Sponsored Links