Dbvisit 5.1.21 For Linux/Unix and Windows Readme.txt Last Updated: $Date: 2008-03-31 18:37:02 +1300 (Mon, 31 Mar 2008) $ $Rev: 1437 $ www.dbvisit.com =============== WHAT IS DBVISIT =============== Dbvisit is a software product that fully automates the Oracle Standby Database solution. 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 is installed with a 30 day evaluation license and may no be used after 30 days. After 30 days Dbvisit will no longer function. To continue using Dbvisit after 30 days please go to www.dbvisit.com to order a licence key. Dbvisit with the evaluation license is fully functional software. ================ 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.1.htm for the Dbvisit Installation Guide and User Manual. ========= WHATS NEW ========= Please see below in section CHANGES ======================================== WINDOWS - NEW INSTALLATIONS ======================================== 1) Unzip the dbvisit51_win32.zip to a temporary location. 2) Double click the Dbvisit Windows installer: Dbvisit51-Inst.exe 3) Follow the on-screen instructions or follow the install instructions in the Dbvisit User Guide. http://www.dbvisit.com/docs/Dbvisit_UserGuide5.1.htm or Dbvisit_UserGuide5.1.pdf ============================================================ WINDOWS - UPGRADING INSTRUCTIONS FROM VERSION 5.1.x to 5.1.x ============================================================ You do not need to re-configure Dbvisit. You do not need to uninstall Dbvisit. Make a copy of the current Dbvisit executables for rollback purposes. Existing license keys are automatically applied to the latest software. These 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) (recommended but not essential). 2) Unzip the dbvisit51_win32.zip to a temporary location. 3) Double click the Dbvisit Windows installer: Dbvisit51-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 iv) A new copy of the DDC file will created and a 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. If the DDR is up to date, nothing needs to be done. vii) Repeat steps i-vi for other databases that use Dbvisit on the primary server. viii) Exit out of the dbvisit_setup program. 6) Start the Dbvisit command console (Start Menu -> Programs -> Dbvisit). 7) Copy over the Dbvisit installation to the standby server with the command: dbvisit -c This command is run on the primary server only. 8) Run Dbvisit manually on the primary and standby server with the command: dbvisit 9) 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.1.htm ================================================================ WINDOWS - UPGRADING INSTRUCTIONS FROM VERSION 5.0 to VERSION 5.1 ================================================================ 1) Unzip the dbvisit51_win32.zip to a temporary location. 2) Double click the Dbvisit Windows installer: Dbvisit51-Inst.exe 3) Follow the upgrade instructions in the Dbvisit User Guide. http://www.dbvisit.com/docs/Dbvisit_UserGuide5.1.htm or Dbvisit_UserGuide5.1.pdf 4) Existing license keys are automatically applied to the latest software. License keys for version 5.0 are valid for version 5.1 ======================================== ======================================== LINUX/UNIX - NEW INSTALLATIONS ======================================== 1) Unzip the dbvisit51_.zip file to a directory on your local PC if you have not done so already. (where is the Operating System - linux, hpux, aix, solaris etc) 2) Follow the install instructions in the Dbvisit User Guide. http://www.dbvisit.com/docs/Dbvisit_UserGuide5.1.htm or Dbvisit_UserGuide5.1.pdf ======================================================================= LINUX/UNIX - UPGRADING INSTRUCTIONS FROM VERSION 5.1.x to VERSION 5.1.x ======================================================================= You do not need to re-configure Dbvisit. You do not need to uninstall Dbvisit. Make a copy of the current Dbvisit install directory for rollback purposes. Existing license keys are automatically applied to the latest software. This only needs to be done on the PRIMARY SERVER! -------------- (For RAC the upgrade needs to be done on each primary RAC node) 1) Unzip the dbvisit51_.zip file to a directory on your local PC if you have not done so already. (where is the Operating System - linux, hpux, aix, solaris etc) 2) Copy or ftp the dbvisit51.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 that is used. 4) Untar the dbvisit51.tar file with the command: tar xvf dbvisit51.tar This will replace all executables and files except your 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 iv) A new copy of the DDC file will created and a 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. If the DDR is up to date, nothing needs to be done. vii) Repeat steps i-vi for other databases that use Dbvisit on the primary server. viii) Exit out of the dbvisit_setup program. 7) Copy over the Dbvisit installation to the standby server with the command: dbvisit -c This command is run on the primary server only. 8) Run Dbvisit manually on the primary and standby server with the command: dbvisit 9) Restart the Dbvisit schedule(s). =================================================================== LINUX/UNIX - UPGRADING INSTRUCTIONS FROM VERSION 4.0 to VERSION 5.1 =================================================================== These steps only need to be done on the PRIMARY SERVER! -------------- 1) Unzip the dbvisit51_.zip file to a directory on your local PC if you have not done so already. (where is the Operating System - linux, hpux, aix, solaris etc) 2) Copy or ftp the dbvisit51.tar file to your dbvisit directory (ie /usr/local/dbvisit) ON YOUR PRIMARY SERVER ONLY. 3) Follow the upgrade instructions in the Dbvisit User Guide. http://www.dbvisit.com/docs/Dbvisit_UserGuide5.1.htm or Dbvisit_UserGuide5.1.pdf 4) Existing license keys are automatically applied to the latest software. License keys for version 4.0 are valid for version 5.1 ======================================== 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-2008 ======================================== CHANGES ======================================== 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.