Skip to Content
avatar image
Former Member

Assertion failed:Unable to set up replication environment Sybase Replication Server.

I need to install replication server and mention is my system specs

ECC 6.0

EHP 7.0

OS Redhat Linux x86 x64

Sybase ASE 15.7.136


Mention Error Given During Installation Sybase Replication Server


Setup of Replication Environment( Last error reported by the step: Assertion failed: Unable to set up replication environment.

The Replication Management Agent reports the following

Task Name Type Value

SetupReplicationTask Task Name Setup replication

SetupReplicationTask Task State Error

SetupReplicationTask Short Description Setup replication between two Sybase ASE servers.

SetupReplicationTask Long Description Configuring remote replication server.

SetupReplicationTask Current Task Number 3

SetupReplicationTask Total Number of Tasks 5

SetupReplicationTask Hostname

SetupRoutes Task Name Setup Routes

SetupRoutes Task State Error

SetupRoutes Short Description Setup routes between the primary to standby Replication Servers

SetupRoutes Hostname XXXXXX

CreateRoute Task Name Create Route

CreateRoute Task State Error

CreateRoute Short Description Create the route between two Replication Servers.

CreateRoute Long Description Waiting 60 seconds: Continuing to wait for the route from Replication Server 'SID_REP_SiteA' to Replication Server 'SID_REP_SiteB' to become active.

CreateRoute Failing Command rs_helproute SID_REP_SiteA

CreateRoute Failing Command Error Message The route from Replication Server 'SID_REP_SiteA' to Replication Server 'SID_REP_SiteB' did not become active and the setup process has timed out.

CreateRoute Corrective Action The route from Replication Server 'SID_REP_SiteA' to Replication Server 'SID_REP_SiteB' must be active before the setup process can proceed. Use the rs_helproute command to determine the state of the route. Once the route is active, restart the setup process.

CreateRoute Hostname XXXXX

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Aug 02, 2017 at 02:13 PM

    While logged into the repserver:

    - to see the current value: admin config, sub_daemon_sleep_time

    - to change the value to 5 seconds: configure replication server set sub_daemon_sleep_time to '5'

    Add comment
    10|10000 characters needed characters exceeded

    • isql -S <repserver_name> -U <login> -P <password>


      If you continue to have problems getting replication setup for your ECC/EHP environment, I'd recommend opening a ticket with tech support as that will likely be much quicker than using this Q&A medium.

  • Aug 01, 2017 at 02:49 PM

    NOTE: I don't work with SAP applications (eg, ECC, EHP), but I do work with ASE and SRS (repserver), so fwiw ...

    If I'm understanding that snippet of log messages, the setup 'failed' while waiting for a route (between 2x repservers) to complete.


    Some background ...

    - when you create a route between repservers, a subset of data from the upstream repserver's RSSD must be replicated to the downstream repserver's RSSD ...

    - this requires that subscriptions be created and materialized for several tables (between the upstream and downstream RSSDs)

    - repserver typically processes a smallish number of these subscription materializations in batches, with the default setting being to wait ~120 seconds between each batch

    - assuming all default configs/settings in your repservers, it's not unheard of for these RSSD subscriptions to take upwards of 10 minutes to complete materialization

    - a route is not marked complete and active until all of the RSSD subscription materializations have completed

    - route creations can be sped up quite a bit by setting the SRS config 'sub_daemon_sleep_time' to something more reasonable like 5 or 10 seconds (as opposed to the default setting of 120 seconds) [NOTE: requires a repserver bounce, so obviously need to make this config change before issuing a 'create route' command]


    The log snippet mentions waiting 60 seconds for the route to become active.

    If the 60-second countdown begins after issuing the 'create route' command, and 'sub_daemon_sleep_time' = 120 seconds, then the script is likely not waiting long enough for the route creation to complete (ie, not waiting long enough for the RSSD subscription materializations to complete).

    Since SAP tends to script a lot of this type of activity, and most (all?) clients would have this same problem during route creations (if using the default 'sub_daemon_sleep_time' = 120 seconds), I'm wondering if there could have been an earlier problem with the install, eg, an earlier failure in reconfiguring 'sub_daemon_sleep_time'? a failure to bounce the repserver so the new config takes effect?

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 02, 2017 at 11:12 AM

    Dear Mark A Parsons

    Please tell me procedure Access 'sub_daemon_sleep_time' = 120 seconds .



    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 04, 2017 at 05:47 AM

    Anyone can help me Regarding Subject Problem. I am new in that.

    Add comment
    10|10000 characters needed characters exceeded