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.

Setup warm standby between ASE 12.5.4 & ASE 15.7 using RS 12.6

6 posts in General Discussion Last posting was on 2013-01-23 08:13:24.0Z
Jack Posted on 2013-01-20 08:28:27.0Z
Sender: e5c.50fba95c.1804289383@sybase.com
From: Jack
Newsgroups: sybase.public.rep-server
Subject: Setup warm standby between ASE 12.5.4 & ASE 15.7 using RS 12.6
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <50fbaaaa.ece.1681692777@sybase.com>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 20 Jan 2013 00:28:27 -0800
X-Trace: forums-1-dub 1358670507 172.20.134.41 (20 Jan 2013 00:28:27 -0800)
X-Original-Trace: 20 Jan 2013 00:28:27 -0800, 172.20.134.41
Lines: 8
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9297
Article PK: 1159164

Hi,

Is it possible to setup warm standby between ASE 12.5.4 &
ASE 15.7 using RS 12.6 ?

If yes, please share the details.

Thank You


"Mark A. Parsons" <iron_horse Posted on 2013-01-20 16:43:25.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.rep-server
Subject: Re: Setup warm standby between ASE 12.5.4 & ASE 15.7 using RS 12.6
References: <50fbaaaa.ece.1681692777@sybase.com>
In-Reply-To: <50fbaaaa.ece.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 130112-1, 01/12/2013), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <50fc1ead$1@forums-1-dub>
Date: 20 Jan 2013 08:43:25 -0800
X-Trace: forums-1-dub 1358700205 172.20.134.152 (20 Jan 2013 08:43:25 -0800)
X-Original-Trace: 20 Jan 2013 08:43:25 -0800, vip152.sybase.com
Lines: 22
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9298
Article PK: 1159169

Is it possible? Yes.

The details? It's the same as any other warm standby setup, with the understanding that you'll have a lot of problems
if/when you do a switch active and find the 15.7 dataserver acting as the PDS (eg, you won't be able to dump-n-load to
resync ASE 12.5.4 from ASE 15.7, no ASE 15.x features will replicate to ASE 12.5.4, etc).

If you're having specific issues then you'll need to provide more details of your setup and the actual issue(s) you're
having. It would also be helpful to know why you're configuring warm standby between disparate ASE versions (eg, is
this part of a solution to minimize downtime when upgrading from ASE 12.5.4 to ASE 15.7).

If you have all the software but haven't tried this configuration then ... when in doubt, try it out!

On 01/20/2013 01:28, Jack wrote:
> Hi,
>
> Is it possible to setup warm standby between ASE 12.5.4&
> ASE 15.7 using RS 12.6 ?
>
> If yes, please share the details.
>
> Thank You


Jack Posted on 2013-01-21 05:54:30.0Z
Sender: 1d97.50fbd3f4.1804289383@sybase.com
From: Jack
Newsgroups: sybase.public.rep-server
Subject: Re: Setup warm standby between ASE 12.5.4 & ASE 15.7 using RS 12.6
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <50fcd816.179c.1681692777@sybase.com>
References: <50fc1ead$1@forums-1-dub>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 20 Jan 2013 21:54:30 -0800
X-Trace: forums-1-dub 1358747670 172.20.134.41 (20 Jan 2013 21:54:30 -0800)
X-Original-Trace: 20 Jan 2013 21:54:30 -0800, 172.20.134.41
Lines: 406
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9299
Article PK: 1159177

Yes Mark,this part of a solution to minimize downtime for
PDS when upgrading from ASE 12.5.4 to ASE 15.7.

Here the details,

PDS version: Adaptive Server Enterprise/12.5.4/EBF
13381/P/Sun_svr4/OS 5.8/ase1254/2006/64-bit/FBO

RDS version: Adaptive Server Enterprise/15.7.0/EBF 19497 SMP
/P/Sun_svr4/OS 5.10/ase157/2820/64-bit/FBO/

DRS version: Replication Server/12.6/EBF 14703
ESD#9/Sun_svr4/OS 5.8/1/OPT

admin who result from repserver: shows repagent down

Spid Name State Info
---- ---------- --------------------
----------------------------------------
30 DIST Awaiting Wakeup 102 LDS.gfs
35 SQT Awaiting Wakeup 102:1 DIST LDS.gfs
21 SQM Awaiting Message 102:1 LDS.gfs
20 SQM Awaiting Message 102:0 LDS.gfs
38 DSI EXEC Awaiting Command 101(1) PDS.DRS01_RSSD
25 DSI Awaiting Message 101 PDS.DRS01_RSSD
19 SQM Awaiting Message 101:0 PDS.DRS01_RSSD
34 DSI EXEC Awaiting Command 103(1) PDS.gfs
26 DSI Awaiting Message 103 PDS.gfs
REP AGENT Down PDS.gfs
36 DSI EXEC Awaiting Command 104(1) RDS01.gfs
27 DSI Awaiting Message 104 RDS01.gfs
28 dSUB Sleeping
15 dCM Awaiting Message
17 dAIO Awaiting Message
31 dREC Sleeping dREC
32 dSTATS Sleeping
40 USER Active sa
14 dALARM Awaiting Wakeup
1>

error in reported PDS errorlog:

00:00000:00133:2013/01/20 13:38:44.14 server Started Rep
Agent on database, 'gfs' (dbid = 9).
00:00000:00133:2013/01/20 13:38:44.14 server RepAgent(9):
Received the following communications error message: Msg
05030504: ct_connect(): network packet layer: internal net
library error: There was an error encountered while
establishing the connection..
00:00000:00133:2013/01/20 13:38:44.14 server RepAgent(9):
The Rep Agent Thread will retry the connection to the
Replication Server every 30 second(s). (RepSvr = DRS01).


1> sp_config_rep_agent gfs
2> go
Parameter Name Default
Config Value Run Value
------------------------------
------------------------------
------------------------------
------------------------------
trace flags 0
0 0
scan timeout 15
15 15
send buffer size 2k
16k 16k
scan batch size 1000
20000 20000
schema cache growth factor 1
3 3
retry timeout 60
30 30
priority 5
4 4
rs servername n/a
DRS01 DRS01
msg confidentiality false
false false
msg integrity false
false false
msg origin check false
false false
msg out-of-sequence check false
false false
msg replay detection false
false false
mutual authentication false
false false
send maint xacts to replicate false
false false
unified login false
false false
connect database gfs
gfs gfs
rs username n/a
gfs_repagent gfs_repagent
security mechanism n/a
n/a n/a
trace log file n/a
n/a n/a
connect dataserver phxtst
phxtst phxtst
data limits filter mode stop
stop stop
send structured oqids false
true true
send warm standby xacts false
true true
short ltl keywords false
true true
skip ltl errors false
true true
skip unsupported features false
true true
batch ltl true
true true
ha failover true
true true

(29 rows affected)
(return status = 0)



1> rs_configure
2> go

Config Name Config Value Run Value
-------------------------- ----------------------
--------------------------
byte_order 256 256
cm_fadeout_time 300 300
cm_max_connections 128 128
current_rssd_version 1260 1260
dsi_commit_check_locks_int 1000 1000
dsi_commit_check_locks_log 200 200
dsi_commit_check_locks_max 400 400
dsi_commit_control on on
dsi_exec_request_sproc on on
dsi_exec_request_sproc on on
dsi_ignore_underscore_name on on
dsi_ignore_underscore_name on on
dsi_max_xacts_in_group 20 20
dsi_max_xacts_in_group 60 60
dsi_partitioning_rule none none
dsi_partitioning_rule none none
dsi_rs_ticket_report off off
dsi_text_convert_multiplie 1.0 1.0
dsi_text_convert_multiplie 1.0 1.0
exec_cmds_per_timeslice 100000 100000
exec_cmds_per_timeslice 100000 100000
exec_sqm_write_request_lim 983040 983040
exec_sqm_write_request_lim 983040 983040
ha_failover off off
id_msg_confidentiality not_required
not_required
id_msg_integrity not_required
not_required
id_msg_origin_check not_required
not_required
id_msg_replay_detection not_required
not_required
id_msg_sequence_check not_required
not_required
id_mutual_auth not_required
not_required
id_security_mechanism
id_server DRS01 DRS01
id_unified_login not_required
not_required
init_sqm_write_delay 1000 1000
init_sqm_write_max_delay 10000 10000
md_source_memory_pool 100000 100000
md_sqm_write_request_limit 100000 100000
md_sqm_write_request_limit 983040 983040
memory_limit 2000 2000
memory_max 3 3
minimum_rssd_version 1260 1260
msg_confidentiality not_required
not_required
msg_integrity not_required
not_required
msg_origin_check not_required
not_required
msg_replay_detection not_required
not_required
msg_sequence_check not_required
not_required
mutual_auth not_required
not_required
num_client_connections 100 100
num_concurrent_subs 100 100
num_msgqueues 250 250
num_msgs 204800 204800
num_mutexes 1500 1500
num_stable_queues 32 32
num_threads 250 250
oserver DRS01 DRS01
password_encryption 0 0
queue_dump_buffer_size 1000 1000
rec_daemon_sleep_time 120 120
rep_as_standby off off
rsm_proc_compat_version 1260 1260
rssd_error_class rs_sqlserver_error_cla
rs_sqlserver_error_class
security_mechanism
security_services off off
send_truncate_table on on
smp_enable on on
sqm_recover_segs 1 1
sqm_warning_thr_ind 70 70
sqm_warning_thr1 75 75
sqm_warning_thr2 90 90
sqm_write_flush on on
sqt_init_read_delay 2000 2000
sqt_max_cache_size 67108864 67108864
sqt_max_prs_size 262144 262144
sqt_max_read_delay 10000 10000
sre_reserve 0 0
stats_daemon_sleep_time 600 600
stats_flush_rssd on on
stats_reset_afterflush on on
stats_sampling on on
sts_cachesize 1000000 1000000
sts_full_cache_rs_articles on on
sts_full_cache_rs_classes on on
sts_full_cache_rs_columns on on
sts_full_cache_rs_config on on
sts_full_cache_rs_database on on
sts_full_cache_rs_datatype on on
sts_full_cache_rs_diskaffi on on
sts_full_cache_rs_diskpart off off
sts_full_cache_rs_erroract off off
sts_full_cache_rs_exceptsc off off
sts_full_cache_rs_exceptsh off off
sts_full_cache_rs_exceptsl off off
sts_full_cache_rs_funcstri off off
sts_full_cache_rs_function off off
sts_full_cache_rs_idnames off off
sts_full_cache_rs_ids off off
sts_full_cache_rs_maintuse off off
sts_full_cache_rs_objects off off
sts_full_cache_rs_oqid on on
sts_full_cache_rs_publicat off off
sts_full_cache_rs_queuemsg off off
sts_full_cache_rs_queuemsg off off
sts_full_cache_rs_queues off off
sts_full_cache_rs_recovery off off
sts_full_cache_rs_repdbs off off
sts_full_cache_rs_repobjs on on
sts_full_cache_rs_routes off off
sts_full_cache_rs_routever off off
sts_full_cache_rs_rules on on
sts_full_cache_rs_segments on on
sts_full_cache_rs_sites off off
sts_full_cache_rs_statcoun off off
sts_full_cache_rs_statdeta off off
sts_full_cache_rs_statrun off off
sts_full_cache_rs_subscrip off off
sts_full_cache_rs_systext off off
sts_full_cache_rs_translat off off
sts_full_cache_rs_users on on
sts_full_cache_rs_version off off
sts_full_cache_rs_wherecla off off
sub_daemon_sleep_time 10000 10000
sub_sqm_write_request_limi 983040 983040
sub_sqm_write_request_limi 983040 983040
unified_login not_required
not_required
use_security_services off off
use_ssl off off
varchar_truncation off off
(return status = 0)
1>

Not sure why repagent is showing down in repserver, on PDS
it's running.


1> sp_help_rep_agent gfs
2> go
Replication Agent Recovery status
dbname connect dataserver
connect database status
rs servername rs username
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
gfs phxtst
gfs not active
DRS01 gfs_repagent
Replication Agent Process status
dbname spid sleep status
retry count last error
------------------------------ -----------
------------------------------ ----------- -----------
gfs 133 connect retry
0 0
Replication Agent Scan status
dbname start marker
end marker current marker
log recs scanned oldest transaction
------------------------------
------------------------------
------------------------------
------------------------------ ----------------
------------------------------
gfs (0,0)
(0,0) (0,0)
0 (0,0)
Replication Agent Configuration
dbname auto start
rs servername rs username
connect dataserver connect database
scan batch size scan timeout retry timeout skip ltl
errors batch ltl send
warm standby xacts send maint xacts to replicate ha
failover skip unsupported features
short ltl keywords send buffer size
priority send structured oqids
data limits filter mode schema cache growth factor
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------ --------------- ------------
------------- ------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
gfs true
DRS01 gfs_repagent
phxtst gfs
20000 15 30 true
true true
false true
true true
16k 4
true stop
3
Replication Agent Security Configuration
dbname security mechanism
unified login msg confidentiality
msg integrity msg replay detection
msg origin check msg out-of-sequence check
mutual authentication
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
------------------------------
gfs n/a
false false
false false
false false
false
(return status = 0)
1>

> Is it possible? Yes.
>
> The details? It's the same as any other warm standby
> setup, with the understanding that you'll have a lot of
> problems if/when you do a switch active and find the 15.7
> dataserver acting as the PDS (eg, you won't be able to
> dump-n-load to resync ASE 12.5.4 from ASE 15.7, no ASE
> 15.x features will replicate to ASE 12.5.4, etc).
>
> If you're having specific issues then you'll need to
> provide more details of your setup and the actual issue(s)
> you're having. It would also be helpful to know why
> you're configuring warm standby between disparate ASE
> versions (eg, is this part of a solution to minimize
> downtime when upgrading from ASE 12.5.4 to ASE 15.7).
>
> If you have all the software but haven't tried this
> configuration then ... when in doubt, try it out!
>
>
> On 01/20/2013 01:28, Jack wrote:
> > Hi,
> >
> > Is it possible to setup warm standby between ASE 12.5.4&
> > ASE 15.7 using RS 12.6 ?
> >
> > If yes, please share the details.
> >
> > Thank You


"Mark A. Parsons" <iron_horse Posted on 2013-01-21 14:18:01.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.rep-server
Subject: Re: Setup warm standby between ASE 12.5.4 & ASE 15.7 using RS 12.6
References: <50fc1ead$1@forums-1-dub> <50fcd816.179c.1681692777@sybase.com>
In-Reply-To: <50fcd816.179c.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 130112-1, 01/12/2013), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <50fd4e19@forums-1-dub>
Date: 21 Jan 2013 06:18:01 -0800
X-Trace: forums-1-dub 1358777881 172.20.134.152 (21 Jan 2013 06:18:01 -0800)
X-Original-Trace: 21 Jan 2013 06:18:01 -0800, vip152.sybase.com
Lines: 197
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9300
Article PK: 1159192

The PDS repagent status output shows "connect retry" which means the repagent is still trying to connect to the repserver.

I would double check the login/password being used by the repagent to log into the repserver (eg, can you use isql and
the same login/password to log into the repserver?).

I would also double check the repserver entry in the PDS' interfaces file (eg, does the PDS' interfaces entry for the
repserver match the RS' interfaces entry?).

On 01/20/2013 22:54, Jack wrote:
> Yes Mark,this part of a solution to minimize downtime for
> PDS when upgrading from ASE 12.5.4 to ASE 15.7.
>
> Here the details,
>
> PDS version: Adaptive Server Enterprise/12.5.4/EBF
> 13381/P/Sun_svr4/OS 5.8/ase1254/2006/64-bit/FBO
>
> RDS version: Adaptive Server Enterprise/15.7.0/EBF 19497 SMP
> /P/Sun_svr4/OS 5.10/ase157/2820/64-bit/FBO/
>
> DRS version: Replication Server/12.6/EBF 14703
> ESD#9/Sun_svr4/OS 5.8/1/OPT
>
> admin who result from repserver: shows repagent down
>
> Spid Name State Info
> ---- ---------- --------------------
> ----------------------------------------
> 30 DIST Awaiting Wakeup 102 LDS.gfs
> 35 SQT Awaiting Wakeup 102:1 DIST LDS.gfs
> 21 SQM Awaiting Message 102:1 LDS.gfs
> 20 SQM Awaiting Message 102:0 LDS.gfs
> 38 DSI EXEC Awaiting Command 101(1) PDS.DRS01_RSSD
> 25 DSI Awaiting Message 101 PDS.DRS01_RSSD
> 19 SQM Awaiting Message 101:0 PDS.DRS01_RSSD
> 34 DSI EXEC Awaiting Command 103(1) PDS.gfs
> 26 DSI Awaiting Message 103 PDS.gfs
> REP AGENT Down PDS.gfs
> 36 DSI EXEC Awaiting Command 104(1) RDS01.gfs
> 27 DSI Awaiting Message 104 RDS01.gfs
> 28 dSUB Sleeping
> 15 dCM Awaiting Message
> 17 dAIO Awaiting Message
> 31 dREC Sleeping dREC
> 32 dSTATS Sleeping
> 40 USER Active sa
> 14 dALARM Awaiting Wakeup
> 1>
>
> error in reported PDS errorlog:
>
> 00:00000:00133:2013/01/20 13:38:44.14 server Started Rep
> Agent on database, 'gfs' (dbid = 9).
> 00:00000:00133:2013/01/20 13:38:44.14 server RepAgent(9):
> Received the following communications error message: Msg
> 05030504: ct_connect(): network packet layer: internal net
> library error: There was an error encountered while
> establishing the connection..
> 00:00000:00133:2013/01/20 13:38:44.14 server RepAgent(9):
> The Rep Agent Thread will retry the connection to the
> Replication Server every 30 second(s). (RepSvr = DRS01).
>
>
> 1> sp_config_rep_agent gfs
> 2> go
... snip ...
> 1>
>
> Not sure why repagent is showing down in repserver, on PDS
> it's running.
>
>
> 1> sp_help_rep_agent gfs
> 2> go
> Replication Agent Recovery status
> dbname connect dataserver
> connect database status
> rs servername rs username
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> gfs phxtst
> gfs not active
> DRS01 gfs_repagent
> Replication Agent Process status
> dbname spid sleep status
> retry count last error
> ------------------------------ -----------
> ------------------------------ ----------- -----------
> gfs 133 connect retry
> 0 0
> Replication Agent Scan status
> dbname start marker
> end marker current marker
> log recs scanned oldest transaction
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------ ----------------
> ------------------------------
> gfs (0,0)
> (0,0) (0,0)
> 0 (0,0)
> Replication Agent Configuration
> dbname auto start
> rs servername rs username
> connect dataserver connect database
> scan batch size scan timeout retry timeout skip ltl
> errors batch ltl send
> warm standby xacts send maint xacts to replicate ha
> failover skip unsupported features
> short ltl keywords send buffer size
> priority send structured oqids
> data limits filter mode schema cache growth factor
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------ --------------- ------------
> ------------- ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> gfs true
> DRS01 gfs_repagent
> phxtst gfs
> 20000 15 30 true
> true true
> false true
> true true
> 16k 4
> true stop
> 3
> Replication Agent Security Configuration
> dbname security mechanism
> unified login msg confidentiality
> msg integrity msg replay detection
> msg origin check msg out-of-sequence check
> mutual authentication
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> ------------------------------
> gfs n/a
> false false
> false false
> false false
> false
> (return status = 0)
> 1>
>
>> Is it possible? Yes.
>>
>> The details? It's the same as any other warm standby
>> setup, with the understanding that you'll have a lot of
>> problems if/when you do a switch active and find the 15.7
>> dataserver acting as the PDS (eg, you won't be able to
>> dump-n-load to resync ASE 12.5.4 from ASE 15.7, no ASE
>> 15.x features will replicate to ASE 12.5.4, etc).
>>
>> If you're having specific issues then you'll need to
>> provide more details of your setup and the actual issue(s)
>> you're having. It would also be helpful to know why
>> you're configuring warm standby between disparate ASE
>> versions (eg, is this part of a solution to minimize
>> downtime when upgrading from ASE 12.5.4 to ASE 15.7).
>>
>> If you have all the software but haven't tried this
>> configuration then ... when in doubt, try it out!
>>
>>
>> On 01/20/2013 01:28, Jack wrote:
>>> Hi,
>>>
>>> Is it possible to setup warm standby between ASE 12.5.4&
>>> ASE 15.7 using RS 12.6 ?
>>>
>>> If yes, please share the details.
>>>
>>> Thank You


"Mark A. Parsons" <iron_horse Posted on 2013-01-21 14:24:54.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.rep-server
Subject: Re: Setup warm standby between ASE 12.5.4 & ASE 15.7 using RS 12.6
References: <50fc1ead$1@forums-1-dub> <50fcd816.179c.1681692777@sybase.com>
In-Reply-To: <50fcd816.179c.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 130112-1, 01/12/2013), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <50fd4fb6$1@forums-1-dub>
Date: 21 Jan 2013 06:24:54 -0800
X-Trace: forums-1-dub 1358778294 172.20.134.152 (21 Jan 2013 06:24:54 -0800)
X-Original-Trace: 21 Jan 2013 06:24:54 -0800, vip152.sybase.com
Lines: 17
X-Authenticated-User: TeamSybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9301
Article PK: 1159194

Also, are there any messages in the repserver errorlog that could indicate an issue with the repagent?

On 01/20/2013 22:54, Jack wrote:
..snip ...
> error in reported PDS errorlog:
>
> 00:00000:00133:2013/01/20 13:38:44.14 server Started Rep
> Agent on database, 'gfs' (dbid = 9).
> 00:00000:00133:2013/01/20 13:38:44.14 server RepAgent(9):
> Received the following communications error message: Msg
> 05030504: ct_connect(): network packet layer: internal net
> library error: There was an error encountered while
> establishing the connection..
> 00:00000:00133:2013/01/20 13:38:44.14 server RepAgent(9):
> The Rep Agent Thread will retry the connection to the
> Replication Server every 30 second(s). (RepSvr = DRS01).

... snip ...


Jack Posted on 2013-01-23 08:13:24.0Z
Sender: b8b.50ff90ce.1804289383@sybase.com
From: Jack
Newsgroups: sybase.public.rep-server
Subject: Re: Setup warm standby between ASE 12.5.4 & ASE 15.7 using RS 12.6
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <50ff9ba4.fc7.1681692777@sybase.com>
References: <50fd4fb6$1@forums-1-dub>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 23 Jan 2013 00:13:24 -0800
X-Trace: forums-1-dub 1358928804 172.20.134.41 (23 Jan 2013 00:13:24 -0800)
X-Original-Trace: 23 Jan 2013 00:13:24 -0800, 172.20.134.41
Lines: 22
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9306
Article PK: 1159248

All configuration is right, interfaces entry was
wrong..silly mistake...it's working fine..thanks for your
inputs.

> Also, are there any messages in the repserver errorlog
> that could indicate an issue with the repagent?
>
> On 01/20/2013 22:54, Jack wrote:
> ..snip ...
> > error in reported PDS errorlog:
> >
> > 00:00000:00133:2013/01/20 13:38:44.14 server Started
> > Rep Agent on database, 'gfs' (dbid = 9).
> > 00:00000:00133:2013/01/20 13:38:44.14 server
> > RepAgent(9): Received the following communications error
> > message: Msg 05030504: ct_connect(): network packet
> > layer: internal net library error: There was an error
> > encountered while establishing the connection..
> > 00:00000:00133:2013/01/20 13:38:44.14 server
> > RepAgent(9): The Rep Agent Thread will retry the
> > connection to the Replication Server every 30 second(s).
> (RepSvr = DRS01). .... snip ...