Skip to main content

Sybase Replication server Internal

Rplication server internals
-------------------------------

Functioning of all threads
-------------------------------

1> Rep Agent
---------------
a> Scans transaction log PDB
b> Converts log records to log transfer language and send to Inbound queues
c> moves the secondary truncation point
d> verifies correct object schema

2> Stable queue manager
-----------------------
a> Used to manage process of reading/writing/deleting messages on stable device

3> stable queue transaction
---------------------------
a> Passes stable device messages to clients in commit order
* Client includes DIST and DSI threads


* SQT cache size
----------------
a> Each IBQ consumes sqt_max_cache_size
b> Each DSI also takes sqt_max_cache_size


4> distributor (DIST)
---------------------
a> Calls SQT and SQM to read the IBQ in commit order
b> Destination will be an OBQ
c> Makes calls to 3 libraries
1> Subscription resolution engine
2> Transaction delivery (packs commands)
3> Message delivery - It groups messages for different subscribers over a comman route.


5> Data server interface
------------------------
Composed of DSI scheduler thread and DSI executor threads
a> Schedular is queue manager
1> Reads transactions from outbound queue
2> Sorts them into commit order using SQL library
3> Decides the grouping,batching of transactions
b> Executor delivers to the RDS
1> Reads transactions from DSI SQT cache
2> Maps function strings
3> Handles error actions (error checks before sending commit)


6> Groupmg logic
----------------
a> Transaction may be grouped if they
1> are in memory (SQT closed)
2> are from same origin
3> have the same username and password
b> Groups are up to dsi_xact_group_size
bytes (default 64 K)
c> Sent in batches of dsi_cmd_batch_size
bytes



* Replication server users
--------------------------
1> Maintainance user
Used by replication server to make changes in replicate databases.

2> Repagent user
Used by repagents to log into replication server

3> Primary RSSD user
Used by replication server to make changes to its own RSSD

Comments

Post a Comment

Popular posts from this blog

Replication Server Quick Ref Guide

Replication Server Guide : • Replication Server Commands • ASE commands and system stored procedures • ASE RSSD stored procedures • RSSD tables • Replication Server System Functions • Troubleshooting Tips Abbreviations Some abbreviations which are used in this Quick Reference Guide: ASE Adaptive Server Enterprise DSI DataServer Interface - RS thread for a connection to a replicate database DIST Distributor - RS thread per primary database LTM Log Transfer Manager; synonym for RepAgent RS, RepServer Replication Server RepAgent Replication Agent (in primary dataserver) RepDef Replication Definition RSI Replication Server Interface - RS thread related to a route to another RepServer RSM Replication Server Manager (a DBA tool normally used in combination with Sybase Central) RSSD Replication Server System Database SQM Stable Queue Manager - RS thread managing a queue SQT Stable Queue Manager - RS thread assembling transactions Replication Server Commands The following commands can only be ...
Post a Comment
Read more

Sybase IQ material - Quick Ref

Contents IQ 12.6 Commands IQ 12.6 Datatypes IQ 12.6 Functions IQ 12.6 System Procedures IQ 12.6 Catalogue Procedures IQ 12.6 Multiplex System Procedures IQ 12.6 ASE Compatibility System Procedures IQ 12.6 ASE Compatibility Catalogue Procedures IQ 12.6 Extended Procedures IQ 12.6 General Database Options IQ 12.6 T-SQL Compatibility Options IQ 12.6 DBISL Options IQ 12.6 Server Properties IQ 12.6 Database Properties IQ 12.6 Commands Two styles of commenting; the same as in ASE :- /* a comment between delimiters on one or more lines */ -- a comment until the end of this line ALLOCATE DESCRIPTOR descriptor-name [ WITH MAX { integer | host-variable } ] ^ALTER DBSPACE dbspace-name { READWRITE | READONLY | RELOCATE | SIZE dbspace-size [ KB | MB | GB | TB | PAGES ] | ADD dbspace-size [ KB | MB | GB | TB | PAGES ] } ALTER EVENT event-name [ DELETE TYPE | TYPE event-type ] { WHERE { trigger-condition | NULL } | { ADD | [ MODIFY ] | DELETE } SCHEDULE schedule-spec } [ ENABLE | DISABLE ] [ [ MODIFY...
Post a Comment
Read more

Interesting Notes on ASE

Some hidden things about ASE Different States of SLEEP When all processes are shown as SLEEPING by sp_who except the one, which issued the sp_who command, how can a user tell the difference between hangings versus running processes? Definitions In pre-4.9.2 SQL Servers, the output of sp_who could be difficult to interpret. Processes showed only one type of SLEEP status, "sleeping". In System 10, and 4.9.2 Rollup 2115 and above, sp_who shows four types of sleep along with the other possible statuses: Value Meaning Infected The server erred with a stack trace, and the process got an error that would normally kill it. The process is infected instead of killed. Background This process is in the background recv sleep The process is waiting for input from the client Send sleep The process is waiting for a write to the client to complete alarm sleep The process is waiting for an alarm (usually means the process is waiting for a wait for command to complete). Lock sleep The process i...
Post a Comment
Read more