cancel
Showing results for 
Search instead for 
Did you mean: 

unable to replicate data , admin who_is_down showing two entries

SybDBA
Participant
0 Kudos

Hi All,

Any response will be appreciated....

I am new to replication server and facing a issue like shown in below snap, and I am not able to replicate data

Like it is showing the

32 DSI EXEC   Awaiting Command     104(1) syb157134.pubs2

   23 DSI        Awaiting Message     104 syb157134.pubs2

      REP AGENT  Down                 syb157134.pubs2

      NRM        Down                 syb157134.pubs2

why this happens if everything is fine, if not please suggest me where I am doing wrong....

Thanks & Regards

pankaj

Former Member
0 Kudos

Pankaj,

In addition to Mark's advice, I would suggest:

1. Log into the target (eg. RRS) RS and turn on the following flag:

trace "on", "dsi", "dsi_buf_dump"

go

2. Log into the RRS and resubmit the transaction. Eg

resume connection to RDS.rdb

go

3. Tail the RDS errorlog and view dataserver error messages related to the resubmission in real time.

Regards,

Jean-Pierre

Former Member
0 Kudos

Pankaj,

Obviously, transactions have to make it out of the PDS.pdb before you follow my advice, so first do as Mark suggests. Then if the DSI shutsdown after attempting to deliver the transaction to the RDS.rdb, and rather than extracting it from the exceptions log, try the steps I outlined.

A word of caution. Turn off the flag when you are done troubleshooting because if you leave it on, and have a high volume of transactions going against RDS.rdb then the RDS errorlog size will expand at a rapid rate which may create problems.

Turn of the flag like this:

1. Log into the target (eg. RRS) RS and turn on the following flag:

trace "off", "dsi", "dsi_buf_dump"

go

It may not help you this time, but, trust me, it will in the future.

Regards,

Jean-Pierre

Accepted Solutions (0)

Answers (1)

Answers (1)

SybDBA
Participant
0 Kudos

Hi All,

thanks for your promptness and support

below is the PDS log

00:0002:00000:00027:2016/03/01 09:53:46.79 server  Started Rep Agent on database, 'pubs2' (dbid = 4).

00:0002:00000:00027:2016/03/01 09:53:46.79 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:0002:00000:00027:2016/03/01 09:53:46.79 server  Error: 9214, Severity: 16, State: 0

00:0002:00000:00027:2016/03/01 09:53:46.79 server  RepAgent(4): Failed to connect to Replication Server. Please check the Replication Server, username, and password spe

cified to sp_config_rep_agent. RepSvr = ASEREP_1, user = ASEREP_1_ra).

00:0002:00000:00027:2016/03/01 09:53:46.79 server  Error: 9261, Severity: 20, State: 0

00:0002:00000:00027:2016/03/01 09:53:46.79 server  RepAgent(4): This Rep Agent Thread is aborting due to an unrecoverable communications or Replication Server error.

00:0002:00000:00027:2016/03/01 09:53:46.79 server  Rep Agent Thread for database 'pubs2' (dbid = 4) terminated abnormally with error. (major 92, minor 61)

and here this is the RS log

I. 2016/03/01 09:31:20. Server using Open Server version Sybase Server-Library/15.5/P-EBF17541-17540 ESD #2/DRV.15.5.0/SPARC/Solaris 8 Native Threads/BUILD1550-004/64bi

t/OPT/Fri Jan 29 00:35:07 2010

I. 2016/03/01 09:31:20. Server using Open Client version Sybase Client-Library/15.5/P-EBF17540 ESD #2/DRV.15.5.0/SPARC/Solaris 8 Native Threads/BUILD1550-004/64bit/OPT/

Fri Jan 29 00:33:59 2010

I. 2016/03/01 09:31:20. Server using Express Connect Library version Sybase ExpressConnect-Library/15.5/P/RCI 3.0/Sun_svr4/OS 5.8/1/OPT64/Sat Feb 27 15:29:59 2010

I. 2016/03/01 09:31:20. SySAM: Checked out graced license for 1 REP_HVAR_ASE (2010.0227) will expire Mon Mar 28 17:04:46 2016.

I. 2016/03/01 09:31:20. SySAM: Failed to obtain 1 license(s) for REP_HVAR_ASE feature from license file(s) or server(s).

I. 2016/03/01 09:31:20. SySAM: Cannot find license file.

I. 2016/03/01 09:31:20. SySAM:  The license files (or license server system network addresses) attempted are listed below.

I. 2016/03/01 09:31:20. SySAM: License feature name:  REP_HVAR_ASE

I. 2016/03/01 09:31:20. SySAM: License filename:      /restorevol/SYBASE_NEW/SYBASE_REP_155/SYSAM-2_0/licenses/*.lic

I. 2016/03/01 09:31:20. SySAM: License search path:   /restorevol/SYBASE_NEW/SYBASE_REP_155/SYSAM-2_0/licenses/*.lic:

I. 2016/03/01 09:31:20. SySAM: FLEXnet Licensing error:-1,359.  System Error: 2 "No such file or directory"

I. 2016/03/01 09:31:20. SySAM: For further information, refer to the Sybase Software Asset Management website at http://www.sybase.com/sysam

I. 2016/03/01 09:31:20. SySAM: WARNING: Replication Server functionality that requires the REP_HVAR_ASE license will be disabled on Mon Mar 28 17:04:46 2016, unless a s

uitable REP_HVAR_ASE license is obtained before that date.

I. 2016/03/01 09:31:20. Checked out license REP_HVAR_ASE.

I. 2016/03/01 09:31:20. Checked out license REP_HVAR_ASE as graced.

I. 2016/03/01 09:31:21. Server site id is '16777317'.

I. 2016/03/01 09:31:21. Embedded database id is '101'.

I. 2016/03/01 09:31:21. Open partition '/restorevol/SYBASE_NEW/SYBASE_REP_155/queue/part01.dat' with sqm_write_flush 'on'.

I. 2016/03/01 09:31:22. Replication Server 'ASEREP_1' is started.

I. 2016/03/01 09:31:22. SQM starting: 101:0 ASEREP_1_ERSSD.ASEREP_1_ERSSD

I. 2016/03/01 09:31:22. DIST for 'LASE.pubs2' is Starting

I. 2016/03/01 09:31:22. SQM starting: 103:0 LASE.pubs2

I. 2016/03/01 09:31:22. SQM starting: 103:1 LASE.pubs2

I. 2016/03/01 09:31:22. The DSI thread for database 'syb157134.pubs2' is started.

I. 2016/03/01 09:31:22. The DSI thread for database 'ASEREP_1_ERSSD.ASEREP_1_ERSSD' is started.

W. 2016/03/01 09:31:23. WARNING #13061 DSI(113 syb157134.pubs2) - seful/cm.c(6848)

        Server syb157134 is using 'nocase_iso_1' sort order, which is different from this Replication Server's sort order.

___________________________________________________________________

does these logs saying something which I am not getting. If yes please let me know.

Thanks & Regards

pankaj