Results 1 to 4 of 4
  1. #1
    Join Date
    Feb 2004
    Location
    india
    Posts
    45

    Unanswered: creatin replication server setup not working

    Hi
    I am trying to create bi-directional replication setup. I have two servers on same machine and of belong to same sybase version.
    I have replication server SAMPLE_RS and I am trying to do setup with sybase central.
    I am able to do most of the stuff but still replication is not happening.
    I am quite new to rep server. Please help!!.


    My DSI thread is going down repeatedly. I have executed following commands on rep server.

    admin echo, "It is OK"
    echo
    --------
    It is OK

    1> admin quiesce_check
    2> go
    Msg 6138, Level 12, State 0:
    Server 'SAMPLE_RS':
    Can't Quiesce. Queue 125:0 has not been read out. Write=0.2 At least one reader
    is missing


    1> admin health
    Mode Quiesce Status
    ---------------- -------- --------
    NORMAL FALSE SUSPECT

    admin who_is_up
    Spid Name State Info
    ---- ---------- -------------------- ----------------------------------------
    13 DSI EXEC Awaiting Command 101(1) SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD
    9 DSI Awaiting Message 101 SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD
    8 SQM Awaiting Message 101:0 SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD
    28 DSI EXEC Awaiting Command 124(1) S1254B64_STASE.db1
    16 DSI Awaiting Message 124 S1254B64_STASE.db1
    22 DIST Awaiting Wakeup 124 S1254B64_STASE.db1
    19 SQT Awaiting Wakeup 124:1 DIST S1254B64_STASE.db1
    18 SQM Awaiting Message 124:1 S1254B64_STASE.db1
    14 SQM Awaiting Message 124:0 S1254B64_STASE.db1
    43 REP AGENT Awaiting Command S1254B64_STASE.db1
    32 DIST Awaiting Wakeup 125 V1254B64.db1
    33 SQT Awaiting Wakeup 125:1 DIST V1254B64.db1
    31 SQM Awaiting Message 125:1 V1254B64.db1
    29 SQM Awaiting Message 125:0 V1254B64.db1
    51 REP AGENT Awaiting Command V1254B64.db1
    10 dSUB Sleeping
    6 dCM Awaiting Message
    7 dAIO Awaiting Message
    11 dREC Sleeping dREC
    87 USER Awaiting Command sa
    88 USER Active sa
    5 dALARM Awaiting Wakeup
    12 dSYSAM Sleeping


    admin who_is_down
    Spid Name State Info
    ---- ---------- -------------------- ----------------------------------------
    DSI EXEC Down 125(1) V1254B64.db1
    DSI Down 125 V1254B64.db1

    But on server "V1254B64" replication agent is running.

    It is also saying that SAMPLE_RS_ERSSD is down but I am able to connect with command
    isql -USAMPLE_RS_RSSD_prim -PSAMPLE_RS_RSSD_prim_ps -SSAMPLE_RS_ERSSD

    Also can replication cause dumptrdate of a particular database to change which is configured for replication ?
    Can some one guide to me to links which gives clear steps either by sybase central o with manual steps ? I went though some manuals but stpes are quite confusing.

    My ASE is
    Adaptive Server Enterprise/12.5.4/EBF 13381/P/Sun_svr4/OS 5.8/ase1254/2006/64-bit/FBO/Wed May 24 03:14:30 2006

    My rep server is
    Replication Server/15.0/P/Sun_svr4/OS 5.8/1/OPT/Mon Jan 16 21:13:18 2006


    Regards
    Shreedhar

  2. #2
    Join Date
    Sep 2003
    Location
    Switzerland
    Posts
    443
    Quote Originally Posted by shreedhar_tase
    admin who_is_down
    Spid Name State Info
    ---- ---------- -------------------- ----------------------------------------
    DSI EXEC Down 125(1) V1254B64.db1
    DSI Down 125 V1254B64.db1

    But on server "V1254B64" replication agent is running.
    In short,

    Replication Agent - The thread which transfers transactions from primary transaction log to Rep Server.
    DSI - The thread which applies transactions to the target.

    You will see why DSI is down in the Replication Server Error Log. And take appropriate action. If you are not sure about the error, paste it here.

  3. #3
    Join Date
    Feb 2004
    Location
    india
    Posts
    45

    here are repl server log contents

    I. 2008/08/20 11:16:52. Replication Server 'SAMPLE_RS' is started.
    I. 2008/08/20 11:16:52. DIST for 'V1254B64.db1' is Starting
    I. 2008/08/20 11:16:53. The DSI thread for database 'V1254B64.db1' is started.
    I. 2008/08/20 11:16:53. SQM starting: 125:0 V1254B64.db1
    I. 2008/08/20 11:16:53. The DSI thread for database 'SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD' is started.
    I. 2008/08/20 11:16:53. The DSI thread for database 'S1254B64_STASE.db1' is started.
    I. 2008/08/20 11:16:53. SQM starting: 101:0 SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD
    I. 2008/08/20 11:16:53. DIST for 'S1254B64_STASE.db1' is Starting
    I. 2008/08/20 11:16:53. SQM starting: 124:1 S1254B64_STASE.db1
    I. 2008/08/20 11:16:53. SQM starting: 125:1 V1254B64.db1
    I. 2008/08/20 11:16:53. SQM starting: 124:0 S1254B64_STASE.db1
    E. 2008/08/20 11:16:55. ERROR #5152 DSI(125 V1254B64.db1) - dsisched.c(2818)
    There is a system transaction whose state is not known. DSI will be shutdown.
    I. 2008/08/20 11:16:55. The DSI thread for database 'V1254B64.db1' is shutdown.
    I. 2008/08/20 11:17:43. Replication Agent version (600) for 'S1254B64_STASE.db1' does not match the default LTI version for t
    his Replication Server 700 using version 600.
    I. 2008/08/20 11:17:43. Replication Agent for S1254B64_STASE.db1 connected in passthru mode.
    I. 2008/08/20 11:17:44. Replication Agent version (600) for 'V1254B64.db1' does not match the default LTI version for this Re
    plication Server 700 using version 600.
    I. 2008/08/20 11:17:44. Replication Agent for V1254B64.db1 connected in passthru mode.

  4. #4
    Join Date
    Mar 2008
    Posts
    22
    Shree,

    Please use following commands to check the transaction connection
    1> admin show_transactions
    2> go

    and also admin who command this show the the connection in suspended mode.

    Use following command to restart of transaction.
    resume connection to V1254B64.db1 skip transaction

    You shold include the skip transaction or execute transaction clause with resume connection. Otherwise, Replication Server does not reset the secondary_qid correctly.

    As per your rep server error log you are getting.
    " There is a system transaction whose state is not known. DSI will be shutdown."

Posting Permissions

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