Dbvisit - The ultimate Oracle standby database solution
New features in Dbvisit 5.1 compared to 4.0 for Unix/Linux:
- Graceful Switchover allows for different Database structure between primary and standby database.
- Improved setup and configuration. Dbvisit will supply all recommended values. Quick setup can be done which requires less configuration variables to be set.
- Less configuration files required. The dbv.env file is no longer required.
- Improved User Manual and installation Guide.
- Upgrade process simplified. All settings are in one file (dbv.env file has been deleted, so it does not have to be updated anymore).
- New compression methods. Compression methods can be chosen from the following:
- Dbvisit internal compression (using zlib)
- Ssh compression
- No compression
- External compression like gzip or compress
- Internal Dbvisit email client can be used as well as external email client like sendmail.
- New Dbvisit command to activate the standby database in the event of a disaster.
- Creation of Dbvisit repository is improved. Feedback is improved.
- Dbvisit Database Configuration (DDC) file can be updated through the dbvisit_setup menu as well as manually through a text editor.
- DDC file now contains explanations about that the variables and their meanings.
- DDC file variables does not have the "EXPORT variable" anymore. The structure is much more forgiving.
- Improved mechanism to detect if Dbvisit is already running or not.
- Size of archive log file is now stored in the Dbvisit repository.
- Size of compressed log file is now stored in the Dbvisit repository.
- If Dbvisit detects that a file is locked by an external process, Dbvisit will wait and retry the lock until certain threshold is met.
- Second heartbeat time can be specified.
- Allow for different ssh port to be specified if the default port (22) is not available.
- Different scp options can be set. For example to limit the bandwidth during the transfer.
- Automatic trace file management. Trace files will be deleted according to new Dbvisit Database Configuration (DDC) settings NUM_TRACE_TO_KEEP and DAYS_TO_KEEP_TRACE.
- Dbvisit process on standby server can be initiated from the primary server with new setting INITIATE_DBVISIT_ON_STANDBY = Yes. This will initiate Dbvisit on the standby server as the last step of running Dbvisit on the primary server.
- Added setting ARCHIVE_LOG_GAP_THRESHOLD. Dbvisit will alert if the archive log gap from the Dbvisit archive log gap report (dbvisit -i) exceeds this value.
- Archive log gap report can be included as part of the daily heartbeat email. Set variable SEND_LOG_GAP_WITH_HEARTBEAT = Yes to turn this feature on.
