The Dbvisit Standby database repository (DDR) can be queried to obtain information about the standby database process. There are three methods to report on the information contained in the DDR:
...
| Section |
|---|
| Column |
|---|
| | Panel |
|---|
| SELECT datestamp,
oracle_sid,
process,
round(decode(size_in_bytes,-1,size_in_bytes,size_in_bytes/1024/1024),1) Size_MB,
(end_time_date-start_time_date)*246060 duration_seconds seconds
*FROM dbvisit.dbv_transfer_log
ORDER ORDER BYBY
datestamp,
process; |
The column "process" specifies the Dbvisit Standby step. This can be COMPRESS for the log compress step or TRANSFER for the transfer of the log from the primary server to the standby server. If column "size_in_bytes" is -1, then this means this information is not available. |
|
2. The following query will report on the log archive log gap over time. Note that the archive log gap information is only saved if the dbvisit -icommand (inspect) is scheduled on a regular basis:
| Section |
|---|
| Column |
|---|
| | Panel |
|---|
| SELECT oracle_sid,datestamp,archive_log_gap FROM dbvisit.dbv_sequence_log ORDERBY datestamp; |
|
|