Welcome to the Dbvisit tip of the week.

To find transfer information about the last log that Dbvisit has transferred use the dbv_functions -N command run on the primary server. For example for the w112g primary database run the command as follows:

$ dbv_functions -N w112g
Dbvisit Database configuration (DDC) file dbv_w112g.env.
<<<>>>
oracle_sid             => w112g
sequence#              => 4
thread_num             => 1
log_id                 => 716466692
archive_name           => /oracle/flash_recovery_area/W112G/archivelog/2010_04_18/o1_mf_1_4_5wo
process_id             => 3748
process                => TRANSFER
timestamp              => 201004190307
datestamp              => 2010/04/19:03:07
start_time_date        => 2010/04/19:03:08
end_time_date          => 2010/04/19:03:08
source_host            => dbvisit51
destination_host       => dbvisit52
checksum               => cb3eacfd0be802c5999e9fd682c6c46b50a0ccba
size_in_bytes          => 9660283
size_in_mb             => 9.21
process_completed      => Y

To display information about a specific log file add the sequence number:

$ dbv_functions -N 3 w112g
Dbvisit Database configuration (DDC) file dbv_w112g.env.
<<<>>>
oracle_sid             => w112g
sequence#              => 3
thread_num             => 1
log_id                 => 716466692
archive_name           => /oracle/flash_recovery_area/W112G/archivelog/2010_04_17/o1_mf_1_3_5wl
process_id             => 3748
process                => TRANSFER
timestamp              => 201004190307
datestamp              => 2010/04/19:03:07
start_time_date        => 2010/04/19:03:07
end_time_date          => 2010/04/19:03:08
source_host            => dbvisit51
destination_host       => dbvisit52
checksum               => e6ab447f4c4df5bc64868a6b1baece595a8defbd
size_in_bytes          => 9433837
size_in_mb             => 9
process_completed      => Y

The above displays information about the transfer process. It is also possible to display information about the COMPRESS step:

$ dbv_functions -N 3 w112g COMPRESS
Dbvisit Database configuration (DDC) file dbv_w112g.env.
<<<>>>
oracle_sid             => w112g
sequence#              => 3
thread_num             => 1
log_id                 => 716466692
archive_name           => /oracle/flash_recovery_area/W112G/archivelog/2010_04_17/o1_mf_1_3_5wl
process_id             => 3748
process                => COMPRESS
timestamp              => 201004190307
datestamp              => 2010/04/19:03:07
start_time_date        => 2010/04/19:03:07
end_time_date          => 2010/04/19:03:07
source_host            => dbvisit51
destination_host       => dbvisit52
checksum               => 22e4ece6822f1ef951078992600f00a719de1a43
size_in_bytes          => 42861568
size_in_mb             => 40.88
process_completed      => Y

This shows that for sequence 3, the log file was 40Mb in size, and after compression and during transfer it was only 9Mb in size.