Skip to Content
0

Ase to Ase Replication Problem

Feb 01, 2017 at 12:33 AM

117

avatar image
Former Member

im-log.pngHello,

We have a scenario about Ase to Ase Replication.

OS: Windows 2012 R2

DB version: Sybase Ase 15.7.0.137

Replication Server version: 15.7.1.137 (ebf25866)

Our problem's log is as shown below;

00:0002:00000:00042:2017/02/01 03:18:03.69 server The configuration option 'enable rep agent threads' has been changed by 'DR_admin' from '0' to '1'.

00:0015:00000:00034:2017/02/01 03:18:05.38 server Started Rep Agent on database, 'master' (dbid = 1).

00:0015:00000:00034:2017/02/01 03:18:05.40 server RepAgent(1): Received the following communications error message: Msg 06080503: ct_connect(): directory service layer: internal directory control layer error: Requested server name not found..

00:0015:00000:00034:2017/02/01 03:18:05.40 server Error: 9214, Severity: 16, State: 0

00:0015:00000:00034:2017/02/01 03:18:05.40 server RepAgent(1): Failed to connect to Replication Server. Please check the Replication Server, username, and password specified to sp_config_rep_agent. RepSvr = SEQ_REP_SiteB, user = SEQ_RA_SiteB).

00:0015:00000:00034:2017/02/01 03:18:05.40 server Error: 9261, Severity: 20, State: 0

00:0015:00000:00034:2017/02/01 03:18:05.40 server RepAgent(1): This Rep Agent Thread is aborting due to an unrecoverable communications or Replication Server error.

00:0015:00000:00034:2017/02/01 03:18:05.47 server Rep Agent Thread for database 'master' (dbid = 1) terminated abnormally with error. (major 92, minor 61)

00:0002:00000:00050:2017/02/01 03:18:24.04 server Started Rep Agent on database, 'master' (dbid = 1).

00:0002:00000:00031:2017/02/01 03:18:34.96 server Process id 50 killed by Hostname SAPECCQADB1, Host process id 6100.

00:0002:00000:00050:2017/02/01 03:18:34.97 server Shutting down Rep Agent for database, 'master' (dbid = 1).

00:0010:00000:00065:2017/02/01 03:19:25.08 server Started Rep Agent on database, 'SEQ' (dbid = 4).

00:0010:00000:00065:2017/02/01 03:19:25.08 server RepAgent(4): Received the following communications error message: Msg 06080503: ct_connect(): directory service layer: internal directory control layer error: Requested server name not found..

00:0010:00000:00065:2017/02/01 03:19:25.08 server Error: 9214, Severity: 16, State: 0

00:0010:00000:00065:2017/02/01 03:19:25.08 server RepAgent(4): Failed to connect to Replication Server. Please check the Replication Server, username, and password specified to sp_config_rep_agent. RepSvr = SEQ_REP_SiteB, user = SEQ_RA_SiteB).

00:0010:00000:00065:2017/02/01 03:19:25.08 server Error: 9261, Severity: 20, State: 0

00:0010:00000:00065:2017/02/01 03:19:25.08 server RepAgent(4): This Rep Agent Thread is aborting due to an unrecoverable communications or Replication Server error.

00:0010:00000:00065:2017/02/01 03:19:25.08 server Rep Agent Thread for database 'SEQ' (dbid = 4) terminated abnormally with error. (major 92, minor 61)

Thanks for help,

BR

im-log.png (49.5 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Mark A Parsons Feb 01, 2017 at 01:24 AM
0

NOTE: While I work with ASE and SRS, I do not work with SAP applications [that use ASE/SRS], so fwiw ...

----------

Key issue: Requested server name not found

In order to connect to the repserver, the ASE repagent thread needs to know the network address for the repserver (SEQ_REP_SiteB). The network address (for the repserver) is obtained from the ASE dataserver's interfaces file.

I'm guessing that either a) an entry for the repserver (SEQ_REP_SiteB) hasn't been added to the ASE dataserver's interfaces file or b) an entry for the repserver has been added to the ASE dataservers's interfaces file but the information is incorrect.

I'd suggest you get the repservers network address from the repserver's interfaces file, copy this info to the ASE dataserver's interfaces file, and then try to start the repagents again.

----------

Since this is part of a SAP Business Suite setup/configuration I'm guessing that somewhere along the line someone/something failed to add the repserver's network address to the ASE dataserver's interfaces file ...

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Feb 01, 2017 at 07:15 AM
0

Hi,

We checked all ports via telnet and all of them is ok. Could you please send a check list to control the files.

Share
10 |10000 characters needed characters left characters exceeded
Mark A Parsons Feb 01, 2017 at 01:31 PM
0

Verifying your ports does no good if the ASE dataserver doesn't know which port to connect to.

Did you verify the same entries in both interfaces files?

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

Go to your ASE dataservers interfaces file, find the entry for SEQ_REP_SiteB.

Go to your repserver's interfaces file, find the entry for SEQ_REP_SiteB.

Are the 2 entries the same? If not, update the ASE dataserver's interfaces file to match what's in the repserver's interfaces file.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Just noticed that you're running on Windows.

  • "interfaces" is the name of the file (of interest) on Unix/Linux.
  • "sql.ini" is the name of the file (of interest) on Windows.

Sooo, on a Windows system you're looking for the file named "sql.ini".

0