SQL Anywhere database replication - Still more replication problems

Author

Still more replication problems

Edgard L. Riba

2006-01-04, 8:23 pm

Hi,
I'm having a hard time with replication :-(

I have a 3 site SQL Remote system using ASA 9. One of the problems I'm
having is that the TCP/IP network which ties the 3 sites together becomes
unavailable at times. If the network is unavailable for some time, the SQL
Remote agent crashes.

The problem is that my users are the ones noticing when the agent crashes,
and they are not happy.

How can I be alerted when the SQL remote agent crashes, or better still, can
the agent be set up so that it restarts (say 10 minutes) after execution is
halted?

THanks,
Edgard L. Riba

Jim Diaz

2006-01-05, 8:24 pm

One way to approach this problem is to reduce dbRemote's dependency on
resources which are external to the database server it is replicating to and
from. For example for file based you can provide local directories then
create an application or scheduled task which moves these files to the final
destination directory.

Good Lock

Jim

"Edgard L. Riba" <elriba at rimith dot com> wrote in message
news:43bc3b7f$1@foru
ms-1-dub...
> Hi,
> I'm having a hard time with replication :-(
>
> I have a 3 site SQL Remote system using ASA 9. One of the problems I'm
> having is that the TCP/IP network which ties the 3 sites together becomes
> unavailable at times. If the network is unavailable for some time, the
> SQL Remote agent crashes.
>
> The problem is that my users are the ones noticing when the agent crashes,
> and they are not happy.
>
> How can I be alerted when the SQL remote agent crashes, or better still,
> can the agent be set up so that it restarts (say 10 minutes) after
> execution is halted?
>
> THanks,
> Edgard L. Riba
>
>

Rob Waywell

2006-01-06, 8:23 pm

First let me clarify the wording. Are you seeing an actual crash, or are you
seeing that SQL Remote shuts down cleanly when the message system is
unavailable? I assume that it is the second, but if you are seeing a crash
as in an application execution error then you should definitely be
submitting the case to Tech Support.

As for SQL Remote shutting down when the message system is unavailable, this
is the current expected behaviour and I do not know of any plans to change
this. I agree with Jim that the addition of retry logic is a reasonable
enhancement request.

One common approach to handling this is to run dbremote from a batch file
rather than as a service and to use the -k switch on the dbremote command
line. The batch file can be as simple as:

:starthere
start /wait dbremote -c "..." -k -v -o cons.out \\share\old\logs\dir
ectory
goto :starthere

The -k switch tells dbremote to "close window on completion" which is
important since without it, the process will remain active waiting for the
administrator to close it.

--
-----------------------------------------------
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

"Edgard L. Riba" <elriba at rimith dot com> wrote in message
news:43bc3b7f$1@foru
ms-1-dub...
> Hi,
> I'm having a hard time with replication :-(
>
> I have a 3 site SQL Remote system using ASA 9. One of the problems I'm
> having is that the TCP/IP network which ties the 3 sites together becomes
> unavailable at times. If the network is unavailable for some time, the
> SQL Remote agent crashes.
>
> The problem is that my users are the ones noticing when the agent crashes,
> and they are not happy.
>
> How can I be alerted when the SQL remote agent crashes, or better still,
> can the agent be set up so that it restarts (say 10 minutes) after
> execution is halted?
>
> THanks,
> Edgard L. Riba
>
>

Sponsored Links