solidDB Help : Replication : C Replicator : System tables, events, and procedures used by CREP
  
System tables, events, and procedures used by CREP
The following system tables are used by C Replicator (CREP):
SYS_LOG: a virtual table that enables access to the log records for a replication partition in a source database, see SYS_LOG.
SYS_LOGPOS is an internal system table that contains the transaction log position information that is required for catchup, see SYS_LOGPOS.
SYS_REPLICATION_LOGPOS is a system table for storing the replication log positions that are required to restart replication, see SYS_REPLICATION_LOGPOS.
SYS_REPLICATION_CONNECTIONS is a system table for storing replication connections, see SYS_REPLICATION_CONNECTIONS.
SYS_REPLICATION_SUBSCRIPTIONS is a system table for storing replication subscriptions, see SYS_REPLICATION_SUBSCRIPTIONS.
SYS_REPLICATION_ERRORS is a system table for storing replication errors, see SYS_REPLICATION_ERRORS.
SYS_REPLICATION_CONFLICTS is a system table for storing replication conflicts, see SYS_REPLICATION_CONFLICTS.
SYS_UUID is a system table for storing known source database ids in UUID format, see SYS_UUID.
In addition, the following system tables on the source database store Logreader partition information.
SYS_FEDT_DB_PARTITION is a system table that describes Logreader partitions, see SYS_FEDT_DB_PARTITION.
SYS_FEDT_TABLE_PARTITION is a system table that provides a mapping between tables and Logreader partitions, see SYS_FEDT_TABLE_PARTITION.
The following event and procedure are used by C Replicator (CREP):
SYS_EVENT_REPLICATION_STATUS is an event indicates that there is a change in the CREP replicator status, see SYS_EVENT_REPLICATION_STATUS.
SYS_REPLICATION_STATE_WAIT is a procedure waits for events that report CREP replicator status changes, see SYS_REPLICATION_STATE_WAIT.
Go up to
C Replicator