Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Yet another Rep Agent that is down...

2 posts in Replication Agent Last posting was on 2003-12-22 04:47:48.0Z
Martin Bergman Posted on 2003-12-04 16:24:25.0Z
From: Martin Bergman <mbergman@dexels.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: sybase.public.rep-agent
Subject: Yet another Rep Agent that is down...
X-Priority: 3)
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 193.172.187.146
X-Original-NNTP-Posting-Host: 193.172.187.146
Message-ID: <3fcf5fb9@forums-1-dub>
Date: 4 Dec 2003 08:24:25 -0800
X-Trace: forums-1-dub 1070555065 193.172.187.146 (4 Dec 2003 08:24:25 -0800)
X-Original-Trace: 4 Dec 2003 08:24:25 -0800, 193.172.187.146
Lines: 65
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-agent:636
Article PK: 862288

Hi,

While trying to set up a table replication something went wrong
that screwed up an existing replication agent connection. The
platforms involved are both Linux running Adaptive Server Enterprise/
12.5.0.3/EBF 10980 ESD#1/P/Linux Intel/Linux 2.4.18-18.7.xsmp i686/...
The replication server is Repserver 12.1, running on a Sun Solaris
machine. The error originated after a call to rs_marker was issued at
the primary database with an incorrect argument (note: the syntax of the
argument was erroneous and not the subid of the table subscription). The
result is dat after restarting the repagent an error occurs as described
below and the repagent is shutting down. When trying to repair the
problem the replication subscription, definition and even the connection
to the replicate database were removed. Also, the replication server was
restarted but without any positive result.

Any idea what to do now?

Thanks in advance,

Martin Bergman
Sportlink/Dexels


Excerpt from the logfile:
00:00000:00027:2003/12/04 16:07:33.88 server Started Rep Agent on
database, 'knvbcode' (dbid = 4).
03:00000:00027:2003/12/04 16:07:33.96 server RepAgent(4): Connecting to
a Replication Server that supports a lower LTL version. Features that
are not supported by the lower LTL version may cause the RepAgent to
shutdown. Set the 'skip unsupported features' configuration option to
prevent shutdown.
03:00000:00027:2003/12/04 16:07:33.96 server RepAgent(4): The
Replication Server LTL version should be at least 400 for full support
of features. (Replication server LTL version 300, Rep Agent LTL version
400).
03:00000:00027:2003/12/04 16:07:34.05 server RepAgent(4): Turning Batch
mode off.
03:00000:00027:2003/12/04 16:07:34.05 server RepAgent(4): Received the
following error message from the Replication Server: Msg 2056. Line 1,
character 382: Incorrect syntax with '0x01000065800000ab'..
03:00000:00027:2003/12/04 16:08:34.03 server RepAgent(4): Connecting to
a Replication Server that supports a lower LTL version. Features that
are not supported by the lower LTL version may cause the RepAgent to
shutdown. Set the 'skip unsupported features' configuration option to
prevent shutdown.
03:00000:00027:2003/12/04 16:08:34.03 server RepAgent(4): The
Replication Server LTL version should be at least 400 for full support
of features. (Replication server LTL version 300, Rep Agent LTL version
400).
03:00000:00027:2003/12/04 16:08:34.06 server RepAgent(4): Error in
passthru packet: '_ds 4
0x000000000170288d0002c6c100140002c6c100120000944500df6ca500000000,6
0x000000000170288d0012436173746f726b6e7662636f6465 0x01000065800000ab '.
03:00000:00027:2003/12/04 16:08:34.06 server RepAgent(4): Received the
following error message from the Replication Server: Msg 2056. Line 1,
character 127: Incorrect syntax with '0x01000065800000ab'..
03:00000:00027:2003/12/04 16:08:34.06 server Error: 9261, Severity: 20,
State: 0
03:00000:00027:2003/12/04 16:08:34.06 server RepAgent(4): This Rep
Agent Thread is aborting due to an unrecoverable communications or
Replication Server error.03:00000:00027:2003/12/04 16:08:34.06 server
Rep Agent Thread for database 'knvbcode' (dbid = 4) terminated
abnormally with error. (major 92, minor 61)


zeroman Posted on 2003-12-22 04:47:48.0Z
Sender: 67ad.3fe670c6.1804289383@sybase.com
From: zeroman
Newsgroups: sybase.public.rep-agent
Subject: Re: Yet another Rep Agent that is down...
X-Mailer: WebNews to Mail Gateway v1.1s
Message-ID: <3fe67774.67be.846930886@sybase.com>
References: <3fcf5fb9@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 21 Dec 2003 20:47:48 -0800
X-Trace: forums-1-dub 1072068468 10.22.241.41 (21 Dec 2003 20:47:48 -0800)
X-Original-Trace: 21 Dec 2003 20:47:48 -0800, 10.22.241.41
Lines: 116
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-agent:639
Article PK: 862291

sybase says...

Reference Case#: 10811184 Product: Replication Server
Open Date: 3/6/02 09:39:36 OS: RedHat 5.2 Linux/Int 6.2
Version/EBF: 1200 Generic Platform: Linux/Intel Generic
Closure Rating: 80

--------------------------------------------------------------------------------


Related Cases: 10798358 Click To View All

Case Description:
Recently upgraded ASE. Getting msgs: 2033 Rep Agent....Tag
'origin_time' is expecting datatype 'datetime' and
"Connecting to a Replication Server that supports a lower
LTL version. Features that are not supported by the lower
LTL version may cause the RepAgent to shutdown.." Rep
Agent keeps disconnecting or shutting down.

Key Words: Agent RAT RepAgent

Tip or Workaround:
Not Available

Resolution:
To fix the the Rep Agent warning message about the
mismatched LTL version:



1. Stop the repagent

sp_stop_rep_agent <dbname>



2. Configure Rep Agent to skip unsupported features

sp_config_rep_agent <dbname> , "skip unsupported features",
true



3. Restart the Rep Agent

sp_start_rep_agent <dbname>





The 2033 error is causing the Rep Agent to go down because
the transaction logs were probably not drained before
upgrade.



(The need to drain the transaction logs is documented in the
ASE Installation Guide for each platform. For ASE 12.5, see
Chapter 8 "Upgrading Sybase Servers", the section entitled
"Preparing to Upgrade Servers with Replicated Databases").



You can fix this by removing the secondary truncation point,
truncating the log, and resetting the secondary trunction
point. (Note: you will need to compare the primary and
replicate tables to determine data was lost).





(in the primary database)

sp_stop _rep_agent <dbanme>

go

dbcc setrunc( 'ltm', 'ignore' )

go

dump tran with_truncate only

go



(in the RSSD database)

rs_zeroltm <dataserver>, <dbname>

go



(in the primary database)

dbcc settrunc(' ltm', 'valid' )

go

sp_start_rep_agent <dbname>

go





Resolutions: CIS configuration upgrade

Other Sources Related to Issue(Type - Location):
Case - 10798358