Replication Server System Tables

Learn about the system tables in the Replication Server System Database (RSSD) or Embedded RSSD (ERSSD). System tables are stored in a dedicated database—Adaptive Server for RSSD or SQL Anywhere ERSSD.

• rs_articles
  Stores information about articles known to this Replication Server.
• rs_asyncfuncs
  Stores information about user-defined functions against replication definitions in Replication Server. The same information is also stored in rs_objfunctions.
• rs_classes
  Stores the names of function-string classes and error classes.
• rs_clsfunctions
  Stores information about class-wide functions.
• rs_columns
  Contains information about the columns of replication definitions.
• rs_config
  Holds a set of default configuration parameter values that you can modify using the configure replication server command. You also can set certain parameters for specific targets using the alter connection, alter logical connection, or alter route command.
• rs_databases
  Stores database names known at a Replication Server site.
• rs_datatype
  Stores attribute information for all user-defined datatypes (UDDs) in a replication definition.
• rs_dbreps
  Stores all information about database replication definitions except name sets. It is replicated to all sites with a version number of 12.6 or later.
• rs_dbsubsets
  Stores the name sets for database replication definitions. It is replicated to all sites with a version number of 12.6 or later.
• rs_diskaffinity
  Stores information about the affinity between disk partition and database connection or route.
• rs_diskpartitions
  Stores information about the disk partitions that Replication Server uses for stable message queues.
• rs_erroractions
  Maps a data server error number to an action to be taken by a Replication Server.
• rs_exceptscmd
  Stores the information used to retrieve the text of transactions from the exceptions log.
• rs_exceptshdr
  Stores information about failed transactions. The source and output commands of the transactions are stored in the system tables rs_exceptscmd and rs_systext. All rows for a transaction in rs_exceptscmd and rs_exceptshdr are identified by the column sys_trans_id.
• rs_exceptslast
  Stores the origin ID, secondary queue ID, and associated information about the last logged transaction written into the exceptions log.
• rs_funcstrings
  Stores the function strings associated with each function.
• rs_functions
  Stores information about Replication Server functions.
• rs_idnames
  Stores the names of Replication Servers and databases known to the ID server. rs_idnames table is relevant only at the ID Server site.
• rs_ids
  Stores the last ID used for various types of objects.
• rs_lastcommit
  Replication Server uses the information in the rs_lastcommit table to find the last transaction committed from each data source.
• rs_locater
  Stores the last locator field received by stable queues from each of their senders.
• rs_maintusers
  Stores the user login names and passwords Replication Server uses to access other Replication Servers and data servers.
• rs_msgs
  Stores the localized error messages used during installation and by some Replication Server stored procedures.
• rs_objects
  Stores replication definitions, one per row.
• rs_objfunctions
  Stores information about user functions for replication definitions.
• rs_oqid
  Stores the last queue ID received from an origin site, and is also used to coordinate the resetting of truncation points.
• rs_profdetail
  Records details associated with a Replication Server profile.
• rs_profile
  Stores currently defined Replication Server profiles.
• rs_publications
  Stores information about publications known to this Replication Server.
• rs_queuemsg
  When you dump Replication Server queues into the RSSD, the queue entries are stored in rs_queuemsg. If rs_queuemsg table already has rows for a segment, those rows are deleted from the table before the latest rows from that segment are dumped.
• rs_queuemsgtxt
  Stores the command or text portion of messages in stable queues. Each stable queue entry is represented by one or more rows in this table. Multiple rows are needed when the length of data in the stable queue entry exceeds the maximum command field length of 255 bytes.
• rs_queues
  Stores information to allow site recovery. Used by the Replication Server stable queue manager and guaranteed delivery system.
• rs_recovery
  Logs actions that must be performed by Replication Server upon recovery, if there is a failure.
• rs_repdbs
  Contains information about all of the databases known by a primary Replication Server. This information is stored when a subscription is entered for a database at a replicate site.
• rs_repobjs
  Stores autocorrection flags for replication definitions at replicate Replication Servers. Set the flag to on or off using the set autocorrection command.
• rs_routes
  Stores routing information about network traffic.
• rs_routeversions
  Stores version information about the Replication Servers on each end of a route.
• rs_rules
  Stores subscription rules. The rs_rules table has one row for each term in a subscription clause.
• rs_schedule
  Stores information about the schedules you create in Replication Server.
• rs_scheduletxt
  Stores the command portion of the schedules you create in Replication Server. Each schedule entry is represented by one or more rows in rs_scheduletxt table. Multiple rows are needed when the command exceeds the maximum command field length of 255 bytes.
• rs_segments
  Holds information about the allocation of each segment. Replication Server uses raw disk space to store message data.
• rs_sites
  Stores the names of Replication Servers known at a site.
• rs_statcounters
  Stores descriptive information about each counter. These values do not change.
• rs_statdetail
  Stores counter metrics that have been flushed to the RSSD.
• rs_statrun
  Stores descriptive information about each observation period or run.
• rs_status
  Stores information about the progress of materialization during Replication Server and Sybase IQ InfoPrimer Integration.
• rs_subscriptions
  Stores information about subscriptions, triggers, and fragments.
• rs_systext
  Stores the text of repeating groups for various other tables such as rs_funcstrings.
• rs_tbconfig
  Replication Server uses the information in the rs_tbconfig table to support referential constraints.
• rs_threads
  Replication Server uses the information in the rs_threads table to detect deadlocks and to perform transaction serialization between parallel DSI threads. An entry is updated in this table each time a transaction is started and more than one DSI thread is defined for a connection.
• rs_ticket_history
  Stores rs_ticket information.
• rs_translation
  Stores information about class-level datatype translations.
• rs_users
  Stores a row for each user with access to the Replication Server.
• rs_version
  Stores version number information for the replication system. At local Replication Servers, only the local version number and the system-wide version number are stored. At the ID Server, version information is stored for all Replication Servers in the replication system.
• rs_whereclauses
  Stores information about where clauses used in articles known to this Replication Server.