solidDB Help : Replication : C Replicator : CREP Monitoring and diagnostics : Replication output files
  
Replication output files
C Replicator (CREP) reports its activities in plain text to the message log on the server (solmsg.out). Fatal errors, such as server failures, are logged to the solidDB error log (solerror.out).
In addition, the replicator trace can be enabled, in which case the trace log is stored in a trace log file, see Generating trace log from the replicator.
Replicator messages contain information about the following events:
▪ Replicator start up and stop operations
▪ Addition and removal of sources
▪ Start and stop of replication
▪ Start and stop of the load operation
Other important system events like replication subscription status changes are also reported.
For example, the following output is an example of message log content in a source server after a START REPLICATION statement is executed in the target server:
2018-04-18 14:26:45.764 User 'fgthw56u4' connected, user id 5, machine id clientHost (10.30.2.1).
2018-04-18 14:26:45.956 Logreader using default transaction batch size 1
2018-04-18 14:26:45.958 Logreader catchup init
2018-04-18 14:26:46.110 Logreader catchup scan open
2018-04-18 14:26:46.114 Logreader catchup active
2018-04-18 14:26:46.130 Logreader catchup completed
2018-04-18 14:26:46.131 Logreader live data
The following output is an example of message log content in a target server after execution of the START REPLICATION statement:
2018-04-18 14:26:45.734 User 'LOCAL REPLICATION' connected, user id 8, machine id not defined.
2018-04-18 14:26:45.752 User 'LOCAL REPLICATION' connected, user id 5, machine id not defined.
2018-04-18 14:26:45.824 Starting replication for subscription 'SUBS' with reload.
2018-04-18 14:26:45.825 New subscription 'SUBS' state is LOAD.
2018-04-18 14:26:45.837 User 'LOCAL REPLICATION' disconnected, user id 8, machine id not defined.
2018-04-18 14:26:45.922 User 'LOCAL REPLICATION' connected, user id 2, machine id not defined.
2018-04-18 14:26:45.935 Load completed loading subscription 'SUBS' at position 000000000000015FFFFFFFFF00000000000006DD00000000000006DD rows count 1.
2018-04-18 14:26:47.147 User 'LOCAL REPLICATION' connected, user id 13, machine id not defined.
2018-04-18 14:26:47.164 New subscription 'SUBS' state is ACTIVE.
2018-04-18 14:26:47.174 User 'LOCAL REPLICATION' disconnected, user id 5, machine id not defined.
The user 'LOCAL REPLICATION' refers to the replicator within the target database server. In the source database, replication connections are shown in the same way as any remote ODBC connection.
Go up to
CREP Monitoring and diagnostics