Results 1 to 5 of 5
  1. #1
    Join Date
    Nov 2003
    Posts
    9

    Unanswered: Rep Agent problem

    Hi,

    ase 11.5.1 solaris
    repserver 11.5.1 solaris

    I have a wam standby replication architeture
    between a primary and a replicate database

    When i try a transaction statement , nothing is replicated

    my replication server status is OK ( healthy )
    my stable queue is empty
    the repdefs are OK
    the sp_setreplicate status is OK for each table
    the rep agent is active
    everything is active, but nothing is replicated

    none errors messages in the logs

    is there a way to check the rep agent activity ??

    regards

  2. #2
    Join Date
    Jun 2002
    Location
    Argentina
    Posts
    78
    Try this (you have to connect to the replication server):

    -- just to see if i'm connected
    admin echo, "It is OK"
    go
    -- to see if there is data to replicate
    admin quiesce_check
    go
    admin health
    go
    admin who_is_up
    go
    -- to see i something is down
    admin who_is_down
    go

    Also It's important wich users you use. Never use a maintusers to run transactions if you want to replicate.

    -- Run in the RSSD
    -- MAINTUSERS LOGIN & PASSWORD
    SELECT *
    FROM RSSD..rs_maintusers
    go

    Good luck

    Sebastian

  3. #3
    Join Date
    Nov 2003
    Posts
    9
    Hi,

    everything is OK in the repserver, repdefs OK

    but when i try to replicate data, nothing is done


    1> admin health
    2> go
    Mode Quiesce Status
    ---------------- -------- --------
    NORMAL TRUE HEALTHY
    1> admin who_is_down
    2> go
    Spid Name State Info
    ---- ---------- -------------------- ----------------------------------------
    1> admin who_is_up
    2> go
    Spid Name State Info
    ---- ---------- -------------------- ----------------------------------------
    15 DIST Active 102 LOGICAL_DS.LOGICAL_DB
    17 SQT Awaiting Wakeup 102:1 DIST LOGICAL_DS.LOGICAL_DB
    10 SQM Awaiting Message 102:1 LOGICAL_DS.LOGICAL_DB
    9 SQM Awaiting Message 102:0 LOGICAL_DS.LOGICAL_DB
    20 DSI EXEC Awaiting Command 105(1) SYBDEV_BATCH.G2R
    11 DSI Awaiting Command 105 SYBDEV_BATCH.G2R
    18 DSI EXEC Awaiting Command 101(1) SYBDEV_BATCH.G2R_REP_RSSD
    12 DSI Awaiting Command 101 SYBDEV_BATCH.G2R_REP_RSSD
    8 SQM Awaiting Message 101:0 SYBDEV_BATCH.G2R_REP_RSSD
    19 DSI EXEC Awaiting Command 104(1) SYBDEV_QUALIF.G2R
    13 DSI Awaiting Command 104 SYBDEV_QUALIF.G2R
    22 REP AGENT Awaiting Command SYBDEV_QUALIF.G2R
    14 dSUB Active
    6 dCM Awaiting Message
    7 dAIO Awaiting Message
    16 dREC Active dREC
    23 USER Active sa
    5 dALARM Awaiting Wakeup

  4. #4
    Join Date
    Nov 2002
    Location
    Switzerland
    Posts
    524

    Re: Rep Agent problem

    You can check the rs_lastcommit table in the standby side.

    Did you execute the sp_reptostandby, "ALL" ?

    Did you check the errorlogs of both ASE + RS ?

  5. #5
    Join Date
    Nov 2003
    Posts
    9
    Well, i have resolved my problem by droping and recreating the RSSD db
    and reconfiguring the replication server

    Thanks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •