The query corresponding to each monitoring element to check the replication information is as follows.
This shows information about the replication sender threads.
| Column | Description |
|---|---|
| REP_NAME | The name of the replication object |
| REMOTE_IP | The IP address of the remote server to be replicated |
| REMOTE_REP_PORT | The replication port number of the remote server that is the replication target is determined by the properties of the remote server |
| STATUS | Sender's current status is 1 to be normal. STOP (0), RUN (1), RETRY (2) |
| REPL_MODE | Sender's current replication mode |
| NETWORK | Whether there is a network error. OK (0), ERROR (1) |
| XSN | The SN (Serial Number / Redo Log Serial Number) that the sender last sent, which is the same as REP_SN in v $ repgap. |
This shows information about the replication receiver threads.
| Column | Description |
|---|---|
| REMOTE_IP | The IP address of the remote server that is the replication target |
| REMOTE_REP_PORT | The port number to which the sender of the remote server, which is the subject of Replication. Because it is not specifically set, it is different from time to time. |
| APPLY_XSN | The SN of the remote server that the receiver is currently reflecting |
This checks the replication gap information.
| Column | Description |
|---|---|
| REP_SN | The last SN sent by the sender, same as XSN of v$repsender |
| REP_LAST_SN | The SN most recently logged by the local server transaction |
| REP_GAP | The degree of asynchronousness at intervals between REP_LAST_SN and REP_SN. (Ie, REP_LAST_SN - REP_SN) |
| READ_FILE_NO | The redo log file number that sender last accessed for replication is not updated when reading the redo log buffer for replication in memory, so the old redo log file number may appear even if there is no replication gap. Therefore, the value of this column is meaningful only when there is a replication gap. |
| START_FLAG | The driving state of replication is generally 0. NORMAL (0), QUICK (1), SYNC (2), SYNC_ONLY (3), SYNC RUN (4), SYNC END (5), RECOVERY (6), OFFLINE (7) |
| Column | Description |
|---|---|
| RESTART_XSN | The SN reflected by the remote server, which is the target of replication, means the retransmission starting point when replication is restarted |
| SENDER | Whether the sender works |
| RECEIVER | Whether the receiver works |
| Column | Description |
|---|---|
| LOGFILE_FOR_REP | When the sender is reading a replication-only redo log buffer, it represents a percentage of "logs to be transferred from a replication-only redo log buffer" and when the sender is reading the redo log file directly, it represents "number of redo log files to be replicated". (MB conversion is possible indirectly depending on the application.) If this value appears only as a percentage, it can be a good thing because the replication is performed only in the redo log buffer for replication (When transmitting very quickly, negative numbers may com out instantaneously, but this can be ignored). However, if the number of redo log files is frequently monitored, increase the size of the redo log buffer dedicated to replication defined by the property REPLICATION_LOG_BUFFER_SIZE to the default value of 30 or more. Or the REPLICATION_PREFETCH_LOGFILE_COUNT property - which means the number of redo log files to be cached in memory for the sender - should be increased in advance. |
This shows the table listed in the replicated object.
| Description | |
|---|---|
| LOCAL_TBL | This is output in the form of 'username.tablename' as the target table of replication of the local server. |
| REMOTE_TBL |