These are examples of the messages that Replication Server writes while creating the physical connection for a standby database:
I. 95/11/01 17:47:50. Create starting : SYDNEY_DS.pubs2 I. 95/11/01 17:47:58. Placing marker in TOKYO_DS.pubs2 log I. 95/11/01 17:47:59. Create completed : SYDNEY_DS.pubs2
In these examples, SYDNEY_DS is the standby data server and TOKYO_DS is the active data server.
When you create the physical connection for the standby database, Replication Server writes an “enable replication” marker in the active database transaction log. The standby DSI ignores all transactions until it has received this marker. If, however, you chose the “dump marker” option, the standby DSI continues to ignore messages until it encounters the next dump marker in the log.
When the appropriate marker arrives at the standby database from the active database RepAgent, the standby DSI writes a message in the Replication Server log file and then begins executing subsequent transactions in the standby database.
In the example messages above, Replication Server has created the connection for the standby database, SYDNEY_DS.pubs2, and suspended its DSI thread. At this point, the Database Administrator dumps the contents of the active database, TOKYO_DS.pubs2, and loads it into the standby database.
