SQL Anywhere database replication - No log operation ...

Author

No log operation ...

Mars

2005-11-17, 9:23 am

ASA 9.0.2.3198
Two DB in replication, Win2000/2003. dbRemote run in bacth mode on even
minute on one side and uneven on another.
On remote DB, SQLRemote stop sending messages with error:
E. 11/17 11:06:04. No log operation at offset of 0031167204 in the current
transaction log
E. 11/17 11:06:04. Sending messages failed

In translated log file:
--COMMIT-1039-0031167203 //not 0031167204
COMMIT WORK

I change offset via CALL SYS.sa_setremoteuser( 149, 31167203, 31167203, ....
on each DB. Hereon dbRemote has continued work.
This was approximately 5 times.
What can I do to prevent this error?
Thanks
(sorry for my english)

PS:
SQL Remote options:
-b
-c " dsn=xxx;uid=dba;pwd=
xxx"
-m 10M
-o ...\dbremote.log
-os 1M
-k
-q
-x 20M
E:\data\

create DB:
dbinit -i -s -p 8192 -z 1251CYR xxx.db

Rob Waywell

2005-11-17, 9:23 am

1) Don't break the offsets by changing them yourself. We can't help you at
that point.

2) The next time it happens, submit the reproducible case to Tech Support so
that we can investigate and verify if the log is corrupt and if so try to
determine both the cause of the corruption and whether dbremote can handle
the issue more gracefully.

--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional

Sybase's iAnywhere Solutions

Please respond ONLY to newsgroup

EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all

To Submit Bug Reports:
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug

SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288

"Mars" <nospam_zmars@zmail.ru> wrote in message
news:437c5f8c@forums
-2-dub...
> ASA 9.0.2.3198
> Two DB in replication, Win2000/2003. dbRemote run in bacth mode on even
> minute on one side and uneven on another.
> On remote DB, SQLRemote stop sending messages with error:
> E. 11/17 11:06:04. No log operation at offset of 0031167204 in the current
> transaction log
> E. 11/17 11:06:04. Sending messages failed
>
> In translated log file:
> --COMMIT-1039-0031167203 //not 0031167204
> COMMIT WORK
>
> I change offset via CALL SYS.sa_setremoteuser( 149, 31167203, 31167203,
> ....
> on each DB. Hereon dbRemote has continued work.
> This was approximately 5 times.
> What can I do to prevent this error?
> Thanks
> (sorry for my english)
>
> PS:
> SQL Remote options:
> -b
> -c " dsn=xxx;uid=dba;pwd=
xxx"
> -m 10M
> -o ...\dbremote.log
> -os 1M
> -k
> -q
> -x 20M
> E:\data\
>
> create DB:
> dbinit -i -s -p 8192 -z 1251CYR xxx.db
>
>

Reg Domaratzki \(iAnywhere Solutions\)

2005-11-17, 1:23 pm

Do you have checksums enabled on the database? We made a fix in 902.3173
that was incomplete to address problems with log scanning transaction logs
with checksums enabled. It was later fixed for good in v902.3218, so if you
enabled checksums when you initialized the database, you might just need to
upgrade to the next v902 EBF that we post, since build 3218 is not yet
available.

--
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 filter to "Display ALL platforms IN ALL MONTHS"

"Mars" <nospam_zmars@zmail.ru> wrote in message
news:437c5f8c@forums
-2-dub...
> ASA 9.0.2.3198
> Two DB in replication, Win2000/2003. dbRemote run in bacth mode on even
> minute on one side and uneven on another.
> On remote DB, SQLRemote stop sending messages with error:
> E. 11/17 11:06:04. No log operation at offset of 0031167204 in the current
> transaction log
> E. 11/17 11:06:04. Sending messages failed
>
> In translated log file:
> --COMMIT-1039-0031167203 //not 0031167204
> COMMIT WORK
>
> I change offset via CALL SYS. please_dont_post_thi
s( 149, 31167203,
31167203, ....
> on each DB. Hereon dbRemote has continued work.
> This was approximately 5 times.
> What can I do to prevent this error?
> Thanks
> (sorry for my english)
>
> PS:
> SQL Remote options:
> -b
> -c " dsn=xxx;uid=dba;pwd=
xxx"
> -m 10M
> -o ...\dbremote.log
> -os 1M
> -k
> -q
> -x 20M
> E:\data\
>
> create DB:
> dbinit -i -s -p 8192 -z 1251CYR xxx.db
>
>

Sponsored Links