Replication Intrusions and Impacts on SAP HANA Database

rs_info, which contains information about the sort order and character set used by the replicate database. The replicate database sort order and character set must be recorded in the rs_info table.

The Replication Server rs_get_charset and rs_get_sortorder functions retrieve the character set and sort order from the rs_info table in the replicate database.

rs_lastcommit, a table that contains information about replicated transactions applied to the replicate database. Each row in rs_lastcommit identifies the most recent committed transaction that was distributed to the replicate database from a primary database. Replication Server uses this information to ensure that all transactions are distributed.

The Replication Server rs_get_lastcommit function retrieves information about the last transaction committed in the replicate database. For non-ASE replicate databases, the rs_get_lastcommit function is replaced in the database-specific function string class by the query required to access the rs_lastcommit table in the replicate database.

rs_ticket_history, which contains the execution results of Replication Server command rs_ticket. Replication Server creates a sequence named rs_ticket_seq by which Replication Server provides a unique row ID for rs_ticket_history. The rs_ticket command can be issued for the primary database to measure the amount of time it takes for a command to move from the primary database to the replicate database. You can use this information to monitor Replication Server performance, module heartbeat, replication health, and table-level quiesce. The results of each execution of rs_ticket is stored in a single row of the rs_ticket_history table in the replicate database. You can query each row of the rs_ticket_history table to obtain results of individual rs_ticket executions, or to compare the results from different rows. The data may be manually truncated.