Dbvisit 5.2.20
For Linux/Unix and Windows
Readme.txt 
Last Updated: $Date: 2010-01-10 14:52:52 +1300 (Sun, 10 Jan 2010) $
$Rev: 3658 $

www.dbvisit.com
===============
WHAT IS DBVISIT
===============
Dbvisit is a software product that provides Oracle Disaster Recovery.
Dbvisit provides high availability and peace of mind by ensuring that the 
standby database is automatically kept up to date with the primary database.
Dbvisit also creates the standby database.

This software is fully functional commercial software and includes 
a 30-day evaluation license. A license key is needed to activate the software 
to change it from an evaluation version to a fully licensed version. 
To continue using Dbvisit after 30 days please go to www.dbvisit.com to order a
license key. 

This README contains both install and upgrade instructions for Windows, Linux
and UNIX. This software can be used for new installs and upgrades.

================
DBVISIT COMMANDS
================
For help run:
  dbvisit 
or see http://www.dbvisit.com/include/dbvisit_commands_overview.php
for the complete Dbvisit commands overview.

================
DBVISIT MANUAL
================
See http://www.dbvisit.com/docs/Dbvisit_UserGuide5.2.htm
or Dbvisit_UserGuide5.2.pdf
for the Dbvisit Installation Guide and User Manual

=========
WHATS NEW
=========
Please see below in section CHANGES

========================================
WINDOWS - NEW INSTALLATIONS
========================================
1) Unzip the dbvisit5.2.x_win32.zip to a temporary location.
2) Double click the Dbvisit Windows installer: Dbvisit5.2.x-Inst.exe
3) Follow the on-screen instructions OR
   follow the Dbvisit quick installation instructions on:
   - http://www.dbvisit.com/docs/Dbvisit_quick_installation_guide_windows5.2.htm
   OR
   - http://www.dbvisit.com/docs/Dbvisit_UserGuide5.2.htm
   - Dbvisit_UserGuide5.2.pdf
     For the full install instructions.

============================================================
WINDOWS - UPGRADING INSTRUCTIONS FROM VERSION 5.1.x to 5.2.x
                                           or 5.2.x to 5.2.x
============================================================
You do not need to re-configure or uninstall Dbvisit prior to upgrade. 

Make a copy of the current Dbvisit executables for rollback purposes.
Existing 5.2 license keys are automatically applied to the latest software.
Existing 5.1 license keys are NOT valid for 5.2. Contact sales@dbvisit.com
 to obtain 5.2 license keys if you have current Dbvisit support.
 
The following steps only need to be done on the PRIMARY SERVER!
(For RAC the upgrade needs to be done on each primary RAC node)

1) Stop the Dbvisit schedule(s) if a schedule has been setup in
   Windows schedular (recommended but not essential).           
2) Unzip the dbvisit5.2.x_win32.zip to a temporary location.
3) Double click the Dbvisit Windows installer: Dbvisit5.2.x-Inst.exe
4) Choose only the Dbvisit software.
   Unselect the Bitvise WinSSHD and Bitvise Tunnelier component.
   Unselect the Configure SSH2 component.
5) Say Yes to "Do you want to configure and setup Dbvisit now". 
   This ensures all the latest parameters are available in the Dbvisit Database 
   Configuration (DDC) file and that the Dbvisit Database Repository (DDR) 
   is up to date. 
      i) Choose option 6) Update Dbvisit Database Configuration (DDC) file.
     ii) Choose the Database for which to upgrade the DDC file.
    iii) Would you like to review all the variables? <Yes/No> [Yes]: No
     iv) A new copy of the DDC file will be created (backup copy will be made).
      v) Choose option 5) Manage Dbvisit Database repository (DDR).
     vi) Choose option 3) Check version of Dbvisit Database repository (DDR)
         If this indicates that the DDR needs updating, then choose option 1 to
         update DDR. Note: the database needs to be up for this test.
         If the DDR is up to date, nothing needs to be done.
    vii) Repeat steps i-vi for other databases that use Dbvisit on this primary 
         server.
   viii) Exit out of the dbvisit_setup program.
     ix) Follow any special upgrade instructions from dbvisit_setup (if any).
     
6) Start the Dbvisit command console (Start Menu -> Programs -> Dbvisit).
7) Only if upgrading from 5.1. To upgrade license, run command:
      dbvisit -lic <database_name> <license_user>  <5.2_license_key>
   This command is run on the primary server only.
8) Copy over the Dbvisit installation to the standby server with the command:
      dbvisit -c <database_name>
   This command is run on the primary server only.
9) Run Dbvisit manually on the primary and standby server with the command:
      dbvisit <database_name>      
10) Restart the Dbvisit schedule(s) if stopped.

For more information:
Follow the upgrading instructions in the Dbvisit User Guide.
http://www.dbvisit.com/docs/Dbvisit_UserGuide5.2.htm

========================================
========================================
LINUX/UNIX - NEW INSTALLATIONS
========================================
1) Unzip the dbvisit5.2.x_<os>.zip file to a directory
   on your local PC if you have not done so already.
   (where <os> is the Operating System - linux, hpux, aix, solaris etc)
2) Follow the Dbvisit quick installation instructions on:
   - http://www.dbvisit.com/docs/Dbvisit_quick_installation_guide_linux5.2.htm
   OR
   - http://www.dbvisit.com/docs/Dbvisit_UserGuide5.2.htm
   - Dbvisit_UserGuide5.2.pdf
     For the full install instructions.

=======================================================================
LINUX/UNIX - UPGRADING INSTRUCTIONS FROM VERSION 5.1.x to 5.2.x
                                              or 5.2.x to 5.2.x
=======================================================================
You do not need to re-configure or uninstall Dbvisit prior to upgrade. 

Make a copy of the current Dbvisit install directory for rollback purposes.
Existing 5.2 license keys are automatically applied to the latest software.
Existing 5.1 license keys are NOT valid for 5.2. Contact sales@dbvisit.com
 to obtain 5.2 license keys if you have current Dbvisit support.

The following steps only need to be done on the PRIMARY SERVER! 
(For RAC the upgrade needs to be done on each primary RAC node)

1) Unzip the dbvisit5.2.x_<os>.zip file to a directory
   on your local PC if you have not done so already.
   (where <os> is the Operating System - linux, hpux, aix, solaris etc)
2) Copy or ftp the dbvisit5.2.x.tar file to your dbvisit
   directory (ie /usr/local/dbvisit)
   ON YOUR PRIMARY SERVER (or primary RAC node) ONLY. 
3) Stop the automatic Dbvisit schedule in cron or other
   scheduling software.
4) Untar the dbvisit5.2.x.tar file with the command:
      tar xvf dbvisit5.2.x.tar
   This will replace all executables and files
   except your Dbvisit Database Configuration (DDC) file(s) 
   will stay the same. 
5) Ensure all Dbvisit files are executable with the command:
      chmod 750 *
6) To ensure all the latest parameters are available in the Dbvisit Database 
   Configuration (DDC) file and the Dbvisit Database Repository (DDR) is 
   up to date run command (on primary server only):
      ./dbvisit_setup
      i) Choose option 6) Update Dbvisit Database Configuration (DDC) file.
     ii) Choose the Database for which to upgrade the DDC file.
    iii) Would you like to review all the variables? <Yes/No> [Yes]: No
     iv) A new copy of the DDC file will be created (backup copy will be made).
      v) Choose option 5) Manage Dbvisit Database repository (DDR).
     vi) Choose option 3) Check version of Dbvisit Database repository (DDR)
         If this indicates that the DDR needs updating, then choose option 1 to
         update DDR. Note: the database needs to be up for this test.
         If the DDR is up to date, nothing needs to be done.
    vii) Repeat steps i-vi for other databases that use Dbvisit on this primary 
         server.
   viii) Exit out of the dbvisit_setup program.
     ix) Follow any special upgrade instructions from dbvisit_setup (if any).   

7) Only if upgrading from 5.1. To upgrade license, run command:
      dbvisit -lic <database_name> <license_user>  <5.2_license_key>
   This command is run on the primary server only.
8) Copy over the Dbvisit installation to the standby server with the command:
      dbvisit -c <database_name>
      This command is run on the primary server only.
9) Run Dbvisit manually on the primary and standby server with the command:
      dbvisit <database_name>      
10) Restart the Dbvisit schedule(s).

For more information:
Follow the upgrading instructions in the Dbvisit User Guide.
http://www.dbvisit.com/docs/Dbvisit_UserGuide5.2.htm

===================================================================
LINUX/UNIX - UPGRADING INSTRUCTIONS FROM VERSION 4.0 to VERSION 5.2.x
===================================================================
Follow the upgrade instructions in the Dbvisit User Guide.
   http://www.dbvisit.com/docs/Dbvisit_UserGuide5.2.htm
   or Dbvisit_UserGuide5.2.pdf

========================================     
CONTACT INFORMATION
========================================
Web:      http://www.dbvisit.com
Email:    info@dbvisit.com
Support:  support@dbvisit.com
   
Dbvisit is a product of Avisit Solutions Limited.
Dbvisit is a registered trademark of Avisit Solutions Limited.
Oracle is a registered trademark of Oracle Corporation.
Copyright Avisit Solutions Limited 2000-2010

========================================
CHANGES
========================================
5.2.20 (11 January 2010)
  New features:
  1) Add ENCRYPT_PASSWDS variable to specify if all passwords should be stored
     encrypted in the DDC file or not. To change the setting run dbvisit_setup
     and choose option 6.
  2) Add SWITCHOVER_WAIT_IN_SEC to control how long Dbvisit waits between 
     each checkpoint iteration for graceful switchover. 
     Total time Dbvisit waits for each checkpoint is set by 
     SWITCHOVER_TIMEOUT_IN_SEC.
  Fixes:
  1) When standby redo logs are using OMF, graceful switchover may fail. This
     has been fixed.
  2) When log_archive_format on Windows contains %S, the sequence number 
     can be truncated by Oracle. Ensure that Dbvisit also truncates the number 
     the same way.
  3) Running dbvisit_setup: Update Dbvisit Database configuration (DDC) file may
     error for older DDC files.
  4) Improve error message for ORA-27048.
  5) Improve error message for creation of standby when datafile contains spaces.
  6) Improve message for error 5005 when standby controlfile does not contain the 
     archive log sequence.

5.2.19 - Development release
     
5.2.18 (24 November 2009)
  New features:
  1) Allow for multiple archive log destinations in AMM (Archive Management
     Module) processing (AMM_PROCESS_MULTIPLE_ARCH_DEST).
  2) Improve restartability of standby database creation. Standby Database
     is now shutdown after all the standby database parameters are obtained.
  3) Graceful switchover synchronisation process now includes retries if there
     are network issues.
  4) Improve remote checksum processing. If remote checksum process fails,
     then only checksum process is repeated, not the whole transfer process.
  5) Allow for decimal numbers for DAYS_TO_KEEP_ARCHSOURCE and 
     DAYS_TO_KEEP_ARCHDEST. For example 3.5 days.
  6) Detect Oracle XE admin location for Linux.
  7) Check for Standby archive log destination during graceful switchover.
     If location does not exist, then exit as switchover will not be successful.
  8) Reduce number of trace file that Dbvisit keeps on server: 
     NUM_TRACE_TO_KEEP = 100, DAYS_TO_KEEP_TRACE = 10
  9) Check that Database is in archivelog mode.
 10) Allow for Database which has been recovered with point-in-time recovery
     with resetlogs where SCN may be lower than current SCN.  
 11) Allow for "-" in the DDC file. Example: dbv_prod-vm2.env
     
  Fixes:
  1) Improve duplicate archive log handling for OMF files. 
     Include a unique identifier to ensure the same file does not get renamed 
     more than once.
  2) Add check for ORA-00342: archived log does not have expected resetlogs SCN.
  3) If same archive log is needed more than once by standby database for non 
     RAC, ensure archive log can be compressed.
  4) Allow for multiple NLS_LANGUAGE setting during RAC processing.
  5) Add 24hour time clock to trace file.
  6) Fixed calling AMM from dbv_functions -A
  7) Improve error message in Windows if during standby database creation
     the standby database fails to start.
  8) Fixed issue if first_change# is displayed as float, then graceful switchover 
     was not successful. 
  9) Allow for different instance_name to database_name for graceful switchover.
 10) Notify if create standby database process is not able to remove file on 
     standby database.
 11) Allow for %d log_archive_format.
 12) Check and report if "ORA-00332: archived log is too small" is found.
 
5.2.17 - Development release
  
5.2.16 (18 September 2009)
  New features:
  1) Graceful Switchover for ASM and RAC. RAC database will become a single
     instance database during switchover. After switchover database can be
     converted to a RAC database again. 
     The Oracle ASM instance needs to be version 11gR1 or higher. The Oracle 
     RAC database itself can be Oracle 10g or higher.
  2) Upgrade Bitvise WinSSHD to 4.28 and Tunnelier to 4.29 for Windows only. 
  3) Improve error message when standby fails to start during standby database
     creation.
  4) Add message to remove old archives when activating standby database.
  5) Add smtp authentication and other advanced Mail settings. 
        See MAILCFG_AUTH_USE and MAILCFG_AUTH_PASSWD settings.
  6) Attach trace files to email when Dbvisit errors to forward to Dbvisit support.
     Set filesize limit of 768000 bytes for attachments.
  7) Database files are tested for correct location during creation of 
     standby database. If not correct then user is asked to rename them.
  8) Standby redo log names are tested for correct location during graceful 
     switchover.
  9) Add variable SEND_MAIL_FLAG_DR to turn off mailing from standby server.
 10) Add ability to manually email trace files as attachments with option:
        dbv_functions -m <database> tracefilename    

  Fixes:
  1) Check if Oracle database admin directories exists before creating the 
     standby database.
  2) Fixed Dbvisit repository create error in Oracle 8i.
  3) Add check for ORA-00344: unable to re-create online log when activating
     standby database.
    
5.2.15 (20 July 2009)
  Fixes:
  1) Create standby database fix. If the size of the tablespace is displayed
     as a float instead of number, then the insert into the Dbvisit repository 
     fails. This has been fixed.
  2) Improve error message when controlfile is a backup controlfile.
  3) If the word export is used too many times in the DDC file, then assumes 
     the DDC file is from Dbvisit version 3. This has been fixed.
  4) Improve message when standby database has insufficient SGA size.
  
5.2.14 (7 May 2009)
  New features:
  1) Provide the ability to logon with sys user and password. This can be used
     when internal logon cannot be used or when 
     SQLNET.AUTHENTICATION_SERVICES= (NTS) cannot be set.
  2) Improve message for error 837, sqlplus not found.

5.2.13 (3 May 2009)
  Fixes:
  1) Fix issue with removing trace files on standby server. 
     If the ORACLE_SID on the standby is different to the ORACLE_SID on primary 
     primary server then trace files were not removed. This is now fixed.
  2) Graceful Switchover may fail in Oracle 9i with error:
     ORA-00271: there are no logs that need archiving. This has been fixed.
  
5.2.12 (21 April 2009)
  New features:
  1) Provide improved feedback when PATH setting is not correct for Windows.
  Fixes:
  1) Include 5.2 User Manual for Windows Installer.

5.2.11 (6 April 2009) (pre-release)
  New features:
  1) Automatically creates standby database from primary database.
     Standby database can be created from normal file system database, 
     or from ASM or RAC databases. 
     To create standby database run dbvisit_setup and choose option 7.
  2) Automatically run command dbv_oraStartStop update_ddc_file <database>
     after activation of standby database to automatically reverse Dbvisit
     settings to enable instant reversing of the Dbvisit process 
     (after standby database is rebuilt).

5.1.28  (30 March 2009)
  Fixes:
  1) Add specific SP2-0734 error.
  2) Ignore set pause on setting in login.sql.
       
5.1.27  (12 March 2009)
  New features:
  1) Add variable SEND_HEARTBEAT_DR to allow to turn off heartbeat separately 
     for standby server. SEND_HEARTBEAT is used for the primary server.
  2) Display message to add tempfile(s) to database when open in READ ONLY mode
     and after activation of standby database.     
  Fixes:
  1) Dbvisit fails to obtain ASM archive log when ASM flash recovery is used.
  2) Change default srvctl.exe to srvctl.bat for Windows Rac.  
  3) Allow for German language feedback in Oracle RAC.
  4) Graceful switchover, in some cases the new primary database does not
     require recovery although the Oracle feedback specifies that it does
     stopping graceful switchover processing. This has been fixed.
     
5.1.26  (8 December 2008)
  New features:
  1) Add a workaround for Oracle bug "Create Control File fails with ORA-600 
    [kccscf_1]" during graceful switchover. See metalink: 387210.1
  2) Added SUCCESS_MAILTO, to be able to separate the success emails from the
     failure emails. If this is set to an email address, then 
     all successful Dbvisit emails will be sent to this email address.
     Failure or unsuccessful emails will be to the email address specified by
     ADMINS.
  3) Added variables:
        MAILSUBJECT_PREFIX_LOG_GAP_REPORT
        MAILSUBJECT_PREFIX_SUCCESSFUL
        MAILSUBJECT_PREFIX_HEARTBEAT
     These variables can be used to set a prefix for the email subject line. 
     This can then be used to set filtering rules for emails.

  Fixes:
  1) Correctly identify the log file when using ASM and the archive is no 
     longer available through v$archive_log.
  2) Fix undefined subroutine message in dbv_functions.
  3) For Oracle 8i only: Create controlfile may fail under Graceful Switchover.
  
5.1.25  (1 September 2008)
  New features:
  1) Add dbv_function -Q to replace current standby controfiles on standby
     database with new standby controlfile from primary database.
  2) Add graceful switchover check to ensure redo log numbers are the same
     between primary and standby databases.
  3) Add variable ALERT_IF_STDBY_READ_ONLY. This determines whether to
     alert or not if Dbvisit is run on the standby server and standby
     database is in READ ONLY mode.
          
  Fixes:      
   1) Allow for Oracle feedback in German to be interpreted correctly.
   2) Correctly interpret ORA-01115 error (IO error reading block from file).
   3) Fix for RAC TAKEOVER_SID, destination host not correctly obtained in some
      circumstances.
   4) Fix for graceful switchover when data files are in ASM but redo files
      are not. Dbvisit would incorrectly error that redo files are in ASM.

5.1.24  (25 July 2008)
  New features:
   1) Add variable APPLY_DELAY_LAG_MINUTES. This creates a time delay between
      the archiving of a redo log at the primary database and the application
      of the archive log on the standby database. 
      Note that the archive logs are still transferred to the standby server
      as normal without delay.  
   2) Add variabiable TRANSFER_LOG_GAP_THRESHOLD to report on the difference 
      between the last archived sequence on the primary and the last sequence 
      transferred to the standby server.
   3) Add variables AMM_START_AFTER_EACH_APPLY and AMM_START_AFTER_EACH_TRANSFER
      Normally the Archive Management Module (AMM) to manage the archive log
      files is started at the end of Dbvisit processing. These variables allows
      the AMM module to be started during Dbvisit processing. This may be 
      necessary due to space restrictions. Use with caution! Archives may be 
      deleted before being applied.
   4) Add variable AMM_PERC_FULL_WAIT_MILLISEC. This is used in the 
      Archive Management Module (AMM) to ensure that the percentage full disk
      space displays the correct value. For some volume managers it takes a 
      little time to display the correct status after files have been removed.
      This variables ensures there is some delay before Dbvisit calculates the 
      free space again. Default is 250 milliseconds. 
   5) Add variable AUTO_START_STANDBY_DB. Automatically start the standby 
      database if standby database is down and dbvisit -i or dbvisit -R command
      is given on the primary server. These Dbvisit commands require the 
      standby database to be up. 
   
   Fixes:      
   1) Add autoextend settings to creation of OMF tempfile.
   2) Fix upgrade issue from version 4.0. to 5.1.
   3) Fix add datafile issue for Oracle 8 and 9 introduced in 5.1.23.

5.1.23  (18 June 2008)
  New features:
   1) Add new database connection mode which is determined by variables
      DB_CONNECTION_MODE and DB_CONNECTION_MODE_DR.
      The database connection modes are:
     Dedicated: By default Dbvisit connects with the dedicated connection 
      mode. The dedicated connection mode initiates a database connection
      each time information is requested from the database. The connection is 
      closed after each request.
     Shared: A database connection is opened once at the start of Dbvisit.
      This connection is used (shared) for all information requested from the 
      database. At the end of Dbvisit processing, the connection is closed.
   2) Added option LOGGING_LEVEL=important to limit the messages being logged
      to the Dbvisit log file (dbvisit.hist).
   3) Improved the feedback when Dbvisit cannot find the correct archive
      log file to transfer.
   4) Specify that dbv_oraStartStop update_ddc_file <database> command
      should be run after activate standby database command.

  Fixes:      
   1) Fix issue during Graceful Switchover if an OMF tempfile is used. 
      The tempfile is no longer created with storage information.
   2) In rare cases, Dbvisit may wait indefinitely on a archive log file
      that is in use. This has been fixed.
   3) Ensure dbv_functions -N option to display transfer table works correctly
      when using multiple databases.
   4) AMM threshold processing does not stop after reaching specified threshold
      percentage. This has been fixed. Note that Dbvisit will always ensure the
      archive has transferred before deleting. 
   
5.1.22  (10 May 2008)
  New features:
   1) Add CHECKPOINT option of Ignore. This disables checkpoint processing
      completely and will not force the generation of a new archive log file.
   2) Add new method to obtain filesystem disk space information for Unix
      and Linux. The external df command is not longer required. This is only
      used in the Dbvisit archive log management module (AMM).

  Fixes:      
   1) Improved error message for error 460 if no archive log file is found on 
      server.
   
5.1.21  (31 March 2008)
  New features:
   1) Improve error message when an incorrect tablespace is chosen during
      installation.
   2) Do not error when Oracle gives warning message:
      "Error accessing PRODUCT_USER_PROFILE", unless ALERT_ON_WARNING = Yes.
      Default is ALERT_ON_WARNING = No.
   3) Dbvisit log files (dbvisit.hist and arch_management.log) are now managed
      according to LOG_FILE_ROTATE_MAX and LOG_FILE_SIZE_MAX_MB settings.
   4) Use SHA-1 digest algorithm as default for checksum calculation.
   
  Fixes:
   1) Correctly interpret ORA-01122 error.
   2) Fix message: undefined call to apa_add_datafile.
   3) Fix graceful switchover issue when ORACLE_SID on the standby database is
      different to ORACLE_SID on the primary server.
   4) Fix applying one log file at a time for RAC standby database.

5.1.20  (19 February 2008)
  New features:
   1) Allow for a standby database control file which was not created at the 
      same time as the standby database.
   2) Allow for an alternative internal method to find the last archived log.
   3) Allow for tracing of Bitvise sftpc and sexec software (Windows Only).
   4) Improve performance of internal checksum routine.
   5) Allow for external checksum utility for Windows.
   6) Add option to dbvisit_setup to check for repository version.
   7) Enable the use of RESYNCH_SEQ_OFFSET = 0
   8) Add setting MAILCFG_SMTP_SERVER_DR to allow for different smtp server for
      standby server.
   
  Fixes:
   1) dbvisit_setup does not write or update DDC file if option 
      "No review of all variables" is chosen. This is now fixed.
   2) Alert if temp directory does not exist.
   3) Improved error message if ORACLE_HOME is not found on standby server.
   4) Windows 2000 fix for executing Bitvise sftpc copy function.
   5) Fix date stamp in email headers when using internal Dbvisit mail. 
      Date was one day behind server date.
   6) Activate standby database command in batch mode does not activate 
      the standby database, but opens the standby database in READ ONLY 
      mode. The activate command in interactive mode does work. 
      This has been fixed.
   7) Database tempfile does not get applied to the new primary database 
      during switchover in some cases. This has been fixed.
   8) If temp directory contains spaces then graceful switchover will stop
      (Windows only). This has been fixed.
   9) Resolve core dump issue on AIX.

5.1.19  (15 January 2008)
  New features:
   1) 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.
      Default settings are: 
       NUM_TRACE_TO_KEEP=200 and DAYS_TO_KEEP_TRACE=15
      Least restrictive setting applies between DAYS_TO_KEEP_TRACE
      and NUM_TRACE_TO_KEEP. To turn off, set to 0.
   2) Graceful switchover - If standby database redo log name format is in
      OMF format and primary database is non OMF format, then use primary 
      database name redo format.
   3) AMM processing now ignores the following directories:
      lost+found,onlinelog,backupset,autobackup,backuppiece,flashbacklog,
      imagecopy,controlfile,datafile.
   4) Added variable INITIATE_DBVISIT_ON_STANDBY. Default = No.
      Setting this to Yes will initiate Dbvisit on the standby server as the 
      last step of running Dbvisit on the primary server. 
      Setting this to Yes, will mean Dbvisit should no longer be scheduled on 
      the standby server (as it is now initiated from the primary server). 
      Dbvisit will no longer function as two independent processes with 
      independent alerting and a new strategy must be in place to ensure that 
      notification is received in case of a failure. 
      It is therefore recommended to set ARCHIVE_LOG_GAP_THRESHOLD and to 
      schedule the Dbvisit archive log gap report (dbvisit -i) on the 
      primary to alert if the standby database gets too far behind the 
      primary database.
   5) Added variable ARCHIVE_LOG_GAP_THRESHOLD. Default = 0.
      Dbvisit will alert if the archive log gap from the Dbvisit archive log 
      gap report (dbvisit -i) exceeds this value (ARCHIVE_LOG_GAP_THRESHOLD). 
      To turn off alerting, set ARCHIVE_LOG_GAP_THRESHOLD to 0. 
    6) Added variable SEND_LOG_GAP_WITH_HEARTBEAT. Default = No.
       Determines if the Dbvisit archive log gap report will be included in the
       daily heartbeat email.
    7) Unix/Linux only. Add initial network setup test. If remote shell method, 
       or network is not configured correctly, Dbvisit will provide more 
       detailed error message.
  Fixes:
   1) Graceful Switchover processing fix with more than 9 redo log groups. 
      Controlfile was not created correctly.
   2) Allow for ORACLE_SID length > 9 characters.
   3) For some terminal types the enter key had to be pressed before Dbvisit 
      displayed more license information when updating the license.

5.1.18  (23 November 2007)
   1) Add help function to dbv_functions.
   2) Show correct source and destination file name when transferring
      and destination file name is different.
   3) Set default for ZIP_EXTENSION when compress method is Dbvisit.
   4) Windows only - After Graceful switchover between primary and
      first standby database, there is a ssh connection authentication
      issue between the new primary database and the second standby database.
      This has been resolved.
   5) Add wait and retry if Dbvisit cannot stop Oracle Windows service.
   6) Remove the need to run Dbvisit -R after Graceful Switchover.
   7) Fix incorrect disk % full calculation on Unix and Linux.
   8) Graceful Switchover may detect previous lock files and continue
      processing. This has been resolved.   
   9) Report back when an incorrect Oracle password has been specificied
      during the Dbvisit install.
5.1.17  (1 October 2007)
   1) Allow for different log_archive_dest settings between primary and 
      standby database.
   2) Set default of SYNCH_ENV_FILE_ONLY to Yes
   3) Fix issue where Dbvisit does not recognise ASM archive logs.
5.1.16  (11 October 2007)
   1) Allow for database not needing any media recovery during graceful 
      switchover.
   2) Transfer the README file and Dbvisit User Manual (Windows only) 
       with the Dbvisit -c (copy) command. 
   3) Add CP_OPTIONS and RSH_OPTIONS to dbv_ORACLE_SID.env template file.
5.1.15  (4 October 2007)
   1) Add check if compression = ssh, then copy method cannot be rsh 
      (Unix/Linux only).
   2) Ignore quotes (") around compress, uncompress, copy method and rsh 
      method (Unix/Linux only).
5.1.14  (1 October 2007)
   1) Graceful Switchover supported for Windows.
   2) Graceful Switchover allows different structure between primary and 
      standby database.
   3) Upgrade Bitwise Tunnelier to 4.24 for Windows.
   4) Upgrade Bitwise WinSSHD to 4.23 for Windows.
   5) Allow Copy and SSH method to be selected from a list during 
      dbvisit_setup.
   6) Add check for ORA-01124 cannot recover data file 1 - file is in use or 
      recovery.
   7) Allow for +RMAN ASM configuration for RAC and normal standby database.
   8) Fix issue with log_archive_format %R on Windows.
   9) Fix issue with mixed case variables in DDC file.
   10) Add SUCCESMAIL_DR variable for standby server.
   11) Record correct checksum of archive file before compress.
   12) Display timestamp of last Dbvisit transfer in archive log gap report.
   13) Fix issue where Dbvisit on Windows could cause the archive log file 
       to be corrupted. 
   14) Allow for different ssh port to be specified. Setting: SSH_PORT.
5.0.22 (8 August 2007)
   1) If Dbvisit returns with error code 103, then a message is shown to 
      refer to Dbvisit user manual to resolve. 
      Error code 103 is refers to WinSSHD not being correctly configured on
      the standby server.
   2) Update Dbvisit user guide and add section "Resolving Windows SSH 
      configuration issues".
   3) Oracle checkpoint processing is split up so that individual timings
      can be recorded.
5.0.21 (6 August 2007)
   1) Add more comments to the Dbvisit Database Configuration (DDC) file to 
      explain what each variable is used for.
   2) If ORACLE_HOME_DR is not set, then use ORACLE_HOME as default. If no 
      ORACLE_HOME or ORACLE_HOME_DR is given then Dbvisit will try to find
      the ORACLE_HOME.
   3) Add new Compress option (COMPRESS=No). This will transfer (archive) 
      log files uncompressed.
   4) Add new Compress option (COMPRESS=ssh). This will use ssh compression to 
      transfer the (archive) log files.
      Log files will be left uncompressed on file system.
   5) Allow Dbvisit Database Configuration (DDC) file to contain mixed case
      variables.
   6) Fix issue with adding datafile to standby database.
   7) Fix issue with ASM files processing.
5.0.20 (31 July 2007)
   1) Fix issue where Dbvisit only applies one log at a time on standby for 
      some configurations.
   2) Increase wait time in restarting Windows service when stopping and 
      starting databases.
   3) Add process id to Dbvisit header (pid).
   4) dbvisit_setup no longer exists if authentication method is not set 
      correct in database.
5.0.19 (26 July 2007)
   1) Display evaluation time left when Dbvisit is called with the -lic option.
   2) Fix issue with connecting on Oracle 9i as sysdba.
   3) Add messages on how to fix ORA-01031: insufficient privileges on Windows.
   4) Obtain terminal size.
5.0.18 (16 July 2007)
   1) Fix issue with obtaining archive gap.
   2) Add variable SEND_HEARTBEAT2_TIME24 to allow for second heartbeat email 
      to be sent during the day.
   3) Add variable HOSTNAME_CMD to specify an alternative hostname for 
      a virtual cluster.
   4) Improve and standardise menu text items in dbvisit_setup.
   5) Shorten hostname without domain names. 
5.0.17 (9 July 2007)
   1) Add activate standby database option to dbv_oraStartStop. This option 
      activates the standby database to become a primary database in the event
      that the current primary database is no longer available. 
   2) Improve AMM (Archive Management Module) processing to include double 
      check that the (archive) log has been transferred to the standby
      server before deleting. 
   3) Improve check for file locking mechanism. Variables LOCK_MAX_TIME_SEC 
      and a LOCK_RETRY_TIMEOUT can be set. These variables specify 
      respectively the maximum time for which to try, and the maximum number
      of times to try, opening a file.
   4) Update dbvisit_setup menu text to make the distinction between Dbvisit
      install and Dbvisit setup clearer.
5.0.16 (2 July 2007)
   1) New release for Windows.
   2) Allow for the Dbvisit archive Log gap report to be emailed. This is set 
      by the EMAIL_LOG_GAP_REPORT parameter.