I have two local Sybase DB servers. Server 1 has a Rep Server
installed in it as well. I have checked the logs and windows NT
services to see if it is running properly and it seems to be but there
is discrepency between Server 1 and 2 in the number of records.
Please help.

"Waaghree" <waaghree (AT) yahoo (DOT) com> wrote

Discrepency between 2 ASE servers with replication can be due to a variety
of reasons. Replication may have been turned off for the session (set
replication off) at various times hence no data is replicated, or the
standby has data inserted into it directly. The standby database may have
been built on a dump different to the active (talking warm standby here but
it's the same for full replication). One of our standby databases has 30MB
more free space than the active. I'll be fixing that soon but it's not
causing any problems at present. The key thing is to work out if differences
between server 1 and server 2 is continuing. If so, then can you identify
specific tables or even scripts/users that are turning off replication.

Is this warm standby replication (DDL/DML all replicated) or the full
replication (publications/subscriptions etc).

If warm standby then you want to log into the repserver and run 'admin
who_is_down' to ensure that everything is running ok. In the active
database the repagent should be running (sp_start_rep_agent dbname) and in
the repserver the DSI thread should be running for the connection to the
standby (resume connection to standbyservername.standbydatabase). Then log
into the standby and check that the maint user on the standby,
<dbname>_maint with a likely password of <dbname>_maint_ps, has correct
permissions to update all tables. It's preferable to have a record in
sysalternates to alias the maint user to the dbo.

HTH,
Martin

waaghree (AT) yahoo (DOT) com (Waaghree) wrote in message news:<13a8f9ad.0402190853.2bfecfe9 (AT) posting (DOT) google.com>...
Thanks for the quick reply Martin.. It is a warm standby and when I
check the who_is_down it tells me constantly that DIS EXEC for
DB2.<DBname> is down but when try to resume connection to that db it
says it is not suspended. I have tried shutting down DB2 and also
tried shutting down all servers including Repserver and bringing it
back up but the status of DSI EXEC does not change. Is that a
possible problem and how to resolve it.

Again, thank you for your help.

"Waaghree" <waaghree (AT) yahoo (DOT) com> wrote


Sounds like something could be refusing to replicate to DB2.<DBname>

In the repserver run the command:

sysadmin log_first_tran, DB2, <DBname>

and then in the RSSD database look at the last transaction id in the list
from rs_helpexception.
You can then run 'rs_helpexception tran_id_no, v' and this should tell you
what's refusing to replicate. The details can be a bit hard to interpret
sometimes. Back in the repserver run:
sysadmin log_first_tran, DB2, <DBname> skip transaction
if you're happy to ignore the problem transaction. This can go on for a bit
if you're a number of problem transactions. You may also want to resolve the
problem on the standby database if it turns out your standby database DDLs
are in conflict with your Active.

HTH,
Martin