Dbvisit 6.0.28 For Linux/Unix and Windows Readme.txt Last Updated: $Date: 2012-04-18 11:36:18 +1200 (Wed, 18 Apr 2012) $ $Rev: 8801 $ www.dbvisit.com ======================= WHAT IS DBVISIT STANDBY ======================= Dbvisit Standby was previously called Dbvisit. Dbvisit Standby is a software product that provides Oracle Disaster Recovery. Dbvisit Standby provides high availability and peace of mind by ensuring that the standby database is automatically kept up to date with the primary database. Dbvisit Standby also creates the standby database. "Dbvisit Standby" is the name of this software product. 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 Standby 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. Resources and User Guides: http://www.dbvisit.com/support/resources/ ======================== DBVISIT STANDBY COMMANDS ======================== Dbvisit Standby can be be run through: - traditional command line interface (CLI) or, - graphical user interface (GUI) through browser. To connect to Dbvisit Standby (GUI) in the browser specify the IP of the server and default port 8081 and 8443 for https. Example: http://210.34.87.344:8081 https://210.34.87.344:8443 For help on the command line interface (CLI) run: dbvisit ================ FAILOVER NOTICE ================ To activate or failover the standby database to a primary database in the event of a disaster or failure run command: dbv_oraStartStop activate ORACLE_SID More information is available in Dbvisit help: dbvisit -? =========================== DBVISIT STANDBY USERS GUIDE =========================== See http://www.dbvisit.com/content/online/dbvisit_standby_userguide for the Dbvisit Standby Installation Guide and User Manual ========= WHATS NEW ========= Please see below in section CHANGES ======================================== ======================================== WINDOWS - NEW INSTALLATIONS ======================================== 1) Unzip the dbvisit-standby6.0.x_win32.zip to a temporary location. 2) Double click the Dbvisit Windows installer: dbvisit-standby6.0.x-Inst.exe 3) Follow the on-screen instructions OR See http://www.dbvisit.com/content/online/dbvisit_standby_userguide under "Dbvisit Standby for Windows" for the full install instructions. OR Dbvisit Standby Quick Installation Guide http://www.dbvisit.com/docs/Dbvisit_Standby_Quick_Installation_Guide_Windows =============================================================== WINDOWS - UPGRADING INSTRUCTIONS FROM VERSION 5.x.x to 6.0.x or 6.0.x to 6.0.x =============================================================== You do not need to re-configure or uninstall Dbvisit prior to upgrade. Make a copy of the current Dbvisit Standby executables for rollback purposes. Existing 6.0 license keys are automatically applied to the latest software. Existing 5.3, 5.1 and 5.2 license keys are NOT valid for 6.0. Contact www.dbvisit.com to obtain 6.0 license keys if you have current Dbvisit support. For full step by step upgrade instructions please see http://www.dbvisit.com/content/online/dbvisit_standby_userguide under "Dbvisit Standby for Windows > Upgrading - Windows". The following steps needs to be done on Primary and Standby Servers. (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 scheduler (recommended but not essential). 2) Unzip the dbvisit-standby6.0.x_win32.zip to a temporary location. 3) Double click the Dbvisit Windows installer: Dbvisit6.0.x-Inst.exe 4) To only upgrade the Dbvisit software select "Dbvisit Standby" and "Dbvisit Dbvserver" in the components list. Unselect the Bitvise WinSSHD and Bitvise Tunnelier component. Unselect the Configure SSH2 and System Readiness component. 5) Follow the on-screen instructions. You will be prompted for the installation location for all components. Please ensure it is the same location as where it is currently installed for the component you are upgrading. For the other components this can be ignored. The following steps are for the command line version (CLI) only. 6) On PRIMARY Server ONLY: 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 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 Standby on this primary server. viii) Exit out of the dbvisit_setup program. ix) Follow any special upgrade instructions from dbvisit_setup (if any). 7) Start the Dbvisit command console (Start Menu -> Programs -> Dbvisit). 8) Only if upgrading from 5.1, 5.2 or 5.3. To upgrade license, run command: dbvisit -lic <6.0_license_key> This command is run on the primary server only. 9) Run Dbvisit manually on the primary and standby server with the command: dbvisit 10) Restart the Dbvisit schedule(s) if stopped. ======================================== ======================================== LINUX/UNIX - NEW INSTALLATIONS ======================================== 1) Ensure the following prerequisites are met: i) Oracle software is installed on both primary and standby servers. ii) ssh is setup without a password or passphrase between the primary and standby servers. For information on how to do this please see: http://www.dbvisit.com/content/freeTechGuides/Setup_ssh_without_passphrase.pdf 2) Unzip the dbvisit-standby6.0.x_.zip file to a temp directory on your local PC if you have not done so already. (where is the Operating System - linux, hpux, aix, solaris etc) 3) Copy or ftp the dbvisit-standby6.0.x.tar file to a temporary location on your server (example /usr/tmp). 4) Untar the dbvisit-standby6.0.x.tar file with the command: tar xvf dbvisit-standby6.0.x.tar This will create the "dbvisit" directory and extract the Dbvisit Standby software into this dbvisit directory in the temporary location. 5) cd into the "dbvisit" directory. 6) Ensure dbvisit_install permissions is set to executable with the command: chmod 750 dbvisit_install 7) Run dbvisit_install with command: ./dbvisit_install 8) Follow the dbvisit_install menu to install both Dbvisit Standby software and Dbvisit Web interface. NOTE: The default Dbvisit Standby software location is now: /usr/local/dbvisit/standby/ For more information about the installation please see See http://www.dbvisit.com/content/online/dbvisit_standby_userguide under "Dbvisit Standby for Linux/Unix" for the full install instructions. OR Dbvisit Standby Quick Installation Guide http://www.dbvisit.com/docs/Dbvisit_Standby_Quick_Installation_Guide_Linux =============================================================== LINUX/UNIX - UPGRADING INSTRUCTIONS FROM VERSION 5.x.x to 6.0.x or 6.0.x to 6.0.x =============================================================== You do not need to re-configure or uninstall Dbvisit prior to upgrade. Make a copy of the current Dbvisit Standby executables for rollback purposes. Existing 6.0 license keys are automatically applied to the latest software. Existing 5.3, 5.1 and 5.2 license keys are NOT valid for 6.0. Contact www.dbvisit.com to obtain 6.0 license keys if you have current Dbvisit support. For full step by step upgrade instructions please see http://www.dbvisit.com/content/online/dbvisit_standby_userguide under "Dbvisit Standby for Linux/Unix > Upgrading Linux/Unix". The following steps needs to be done on Primary and Standby Servers. (For RAC the upgrade needs to be done on each primary RAC node) 1) Unzip the dbvisit-standby6.0.x_.zip file to a temp 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 dbvisit-standby6.0.x.tar file to a temporary location on your server (example /usr/tmp). 3) Stop the automatic Dbvisit schedule (recommended but not required). 4) Untar the dbvisit-standby6.0.x.tar file with the command: tar xvf dbvisit-standby6.0.x.tar This will create the "dbvisit" directory and extract the Dbvisit Standby software into this dbvisit directory in the temporary location. 5) cd into the "dbvisit" directory. 6) Ensure dbvisit_install permissions is set to executable with the command: chmod 750 dbvisit_install 7) Run dbvisit_install with command: ./dbvisit_install 8) Follow the dbvisit_install menu to install both Dbvisit Standby software and Dbvisit Web interface. NOTE: The default Dbvisit Standby software location is now: /usr/local/dbvisit/standby/ Any previously Dbvisit installation will be migrated to the new subdirectory "standby". 9) On PRIMARY Server ONLY: 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: cd to Dbvisit Standby installation location (eg /usr/local/dbvisit/standby) and run command: ./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 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 Standby on this primary server. viii) Exit out of the dbvisit_setup program. ix) Follow any special upgrade instructions from dbvisit_setup (if any). 10) Only if upgrading from 5.1, 5.2 or 5.3. To upgrade license, run command: dbvisit -lic <6.0_license_key> This command is run on the primary server only. 11) Repeat above steps for ALL servers that will be running Dbvisit Standby. This includes the primary and standby (or secondary) servers. (For RAC the upgrade needs to be done on each primary RAC node). 12) Run Dbvisit Standby manually on the primary and standby servers to ensure it is functioning correctly. Dbvisit Standby can be manually run through a browser or through the command line. i) Through the browser: http://servername:80801 ii) Through the command line: cd /usr/local/dbvisit/standby ./dbvisit 13) Restart the Dbvisit schedule(s) if they were stopped. 14) Update any paths that reference Dbvisit Standby programs. These can be: - /etc/init.d files - contab entries - etc ======================================== CONTACT INFORMATION ======================================== Web: http://www.dbvisit.com Support: http://www.dbvisit.com/support/service_desk/ Resources: http://www.dbvisit.com/support/resources/ Dbvisit Standby is a product of Dbvisit Software Limited and Avisit Solutions Limited. Dbvisit is a registered trademark of Avisit Solutions Limited. Oracle is a registered trademark of Oracle Corporation. Copyright Avisit Solutions Limited and Dbvisit Software Limited 2012. Except as specifically set out the Dbvisit Standby license agreement, nothing in this Documentation constitutes a warranty as to the operation of the Dbvisit software. ======================================== CHANGES ======================================== 6.0.28 - (18 April 2012) New features: 1) Create standby database (CSD) through the web browser has been enhanced to provide greater stability, flexibility and robustness. 2) SQL*Plus command can be run through the web browser under Run commands. 3) Recreation of the standby control file functions through the dbv_functions -Q command has been extended to be able to handle ASM, OMF, regular file system and different primary and standby database layouts. 4) CSD has been enhanced to further handle different primary and standby database layouts. For example an ASM primary database with a non ASM standby database. 5) Added more options to find the Oracle alert log in the web interface. 6) Add "AS COMPRESSED BACKUPSET" to take compressed backup of datafiles during creation of standby database (CSD). 6.0.26 - (30 March 2012) New features: 1) Enable Dbvisit Standby to be installed with a Windows Domain account. Workaround using a local account is no longer needed. 2) Add check owner function for resolving "Check owner" issues. Run: dbv_functions -a check_owner 3) Allow for unattended install for setting Dbvisit Standby license. 4) Gracefull Switchover will attempt to reset Oracle parameters db_file_name_convert and log_file_name_convert to default values. 5) Use ssh compression during CSD instead of file compression. Fixes: 1) Dbvisit Standby can now be installed in non default location in Windows. 2) Fix for Spanish language setting and RAC. 3) Fix for CSD (create standby database) stop point through web browser. 4) Fix for connectivity between primary and standby scheduler for Windows domain accounts. 6.0.24 - (14 March 2012) Fixes: 1) Scheduler message error (dbv_functions: not found) on the standby server when Dbvisit Standby is installed in a different location to the primary server. 2) Improved Scheduler messaging. 3) Activation of standby database through web interface did not update the DDC file - fixed. 6.0.22 - (5 March 2012) Fixes: 1) Fixed ORA- error handling code bug introduced in 6.0.20. If running Dbvisit Standby 6.0.20, please upgrade as version 6.0.20 may not detect Oracle errors correctly. This only affects version 6.0.20. 2) System_readiness test did not work on Windows if Dbvisit was not installed in standard location - fixed. 3) Check CSD (create standby database) did not skip checking of duplicates in ASM OMF tempfiles - fixed. 4) Scheduler message error (dbv_functions: not found) on the standby server when Dbvisit Standby is installed in a different location to the primary server. 5) Improved Scheduler messaging. 6.0.20 - (27 February 2012) New features: 1) Scheduler stagger option. This allows the standby database schedule to be behind the primary schedule. 2) Added setting SSH_RETURN_CODE to allow for non zero return code of ssh connection. Return code of 1 can be valid for older versions of ssh. 3) Removed limitation for Create Standby Database (CSD) through web interface on Windows 2008 R2 64bit. Fixes: 1) Fix for CSD (create standby database) and Win2K8R2. 2) Grid infrastructure permission fix. 3) No call to ddr_repos_upgrade_60() when upgrading from early versions of dbvisit, fixed. 4) Fix for CSD when REMOTE_LISTENER parameter contains the word "ora". 5) Create Standby Database using Transportable Media check for local files instead of remote files - fixed. 6) Check for "invalid instance name" in RAC_TAKEOVER_SID. 7) Line breaks in CSD output now working for Internet Explorer 8. 8) Redesigned IE 7 warning, and allowed for suppression of this warning. 6.0.18 - (13 February 2012) New features: 1) Improve add datafile functionality. Removed limitations of adding only one datafile at a time. Dbvisit Standby will add all new datafiles to the standby database that are added to the primary database. All datafiles are supported including ASM andf OMF. Notes: i - For RAC USE_LONG_SERVER_NAME must be set to the same value on all primary nodes to function. ii - The standby controlfile is recreated to add the datafiles and so the standby database will be restarted during this operation. 2) Improve dbv_functions -Q option to recreate a standby controlfile. This function can be used on all types of standby databases and also when the standby database has a different structure to the primary database. 3) Validate standby datafiles after recreating a controlfile. 4) Obtain default ASM database name during dbvisit setup (UNIX). 5) Validate the DDC file on standby as part of pre-checks for CSD. 6) Extend template validation to a) pick up datafiles added since the template has been created b) detect duplicate standby database filenames 7) Added HTTPS support for Linux and Windows. Fixes: 1) Add ORACLE_SID_ASM and ORACLE_SID_ASM_DEST to quick setup. 2) ORACLE_ASM_SID and ORACLE_ASM_SID_DEST recorded in a DDC file twice under Primary and Advanced catagories - fixed 3) The name of a DDC file supplied by user not passed to function calls when using option 1) New Dbvisit Database setup (combines options 2,3,4) of dbvisit_setup - fixed 4) Remove ASM databases from a list of databases available on primary server for dbvisit setup. 5) Fixed GUI scheduler issues. 6) Screen and display clarifications in the Dbvisit Standby - Setup GUI process. 7) Reverse values of ORACLE_HOME_ASM and ORACLE_HOME_ASM_DEST after switchover. 8) Ensure redo logs that have to be copied from/to ASM during switchover have write group permissions to be managed by both Dbvisit and grid owner. 9) Various small GUI fixes. Current limitation: 1) Create Standby Database through web interface is not supported for Windows 2008 R2 64bit. Create Standby Database can be created through the Command Line Wizard. This limitation will be resolved in near future. 6.0.16 - (09 January 2012) New features: 1) New Create Standby Database (CSD) functionality which improves the overall ability to create different standby databases configurations. CSD now makes use of the following parameters: - db_file_name_convert - log_file_name_convert 2) Improved graceful switchover functionality. Existing controlfile is re-used for primary database and is no longer rebuild. Graceful switchover allows for more differences between primary and standby database. 3) Provide silent or unattended install for dbvisit_install. This installs product with all default values accepted. Type "dbvisit_install -?" for details. 4) Non existent directories on the standby server are automatically created as much as possible by Dbvisit Standby during creation of the standby database. Fixes: 1) Issue with adding own ORACLE_SID and ORACLE_HOME in web interface - fixed. 2) Dbvisit temp p2x-* directories not cleaned up for HP-UX and AIX - fixed. 3) Improve locking mechanism in rare cases when archive log file just arrives at the standby server and is 0 size and is picked up by Dbvisit Standby on the standby server. 4) Improved tracing of Dbvserver. 5) Obtain ORACLE_HOME and ORACLE_SID from registry for Windows 2008R2. 6.0.14 - (10 November 2011) New features: 1) Display the Windows domain name during setting up of SSH configuration. 2) Improve next steps output of dbvisit_install. 3) Improve error message for error code 447 on RAC. Fixes: 1) Scheduler was not able to be set on remote server - fixed. 2) On Windows, after creation of standby database the dbvserverd process may utilise too much CPU - fixed. 3) Fix small issues during setup with web interface. 3) Capture Oracle message: ORA-28002: the password will expire within x days. 4) Fixed issues related to obtaining ORACLE_HOME for ASM instance on windows. 5) Suppress displaying DBPASSWD in trace files. 6.0.12 - (27 October 2011) New features: 1) Improved overall stability of Dbvserver, the web-server for Dbvisit Standby. 2) Removed reference to STANDBY_FILE_MANAGEMENT parameter. 3) Add variable ORACLE_HOME_ASM_DEST incase ASM location is different on standby server. Fixes: 1) Number of fixes in usability of Dbvserver, the web-based interface to Dbvisit Standby, including the setup and creation of standby databases and the scheduler. 6.0.10 - (18 September 2011) New features: 1) Remove dependance on asmcmd to allow for separate Grid install. 2) Graceful Switchover on Windows with ASM now supported. 3) New END-USER LICENSE AGREEMENT. 4) New Dbvisit Logo. Fixes: 1) In case FRA enabled Dbvisit only searched for an archive to transfer under date subdirectories but not directly under ARCHSOURCEn directories - fixed 2) Attached incorrect PDF User manual - fixed. 3) Remove PFILE setting. This is now obsolete. 4) Display a warning message for Graceful Switchover on Windows to configure Windows service with STARTMODE=MANUAL. 5) Fix minor bugs in functions to stop and start primary and standby databases. 6) Fixed issue with Graceful Switchover and RAC introduced with version 6.0.08 to deal with issue when threads are closed. 7) In some cases Graceful Switchover with RAC may want to transfer compressed archives and this fails - fixed. 8) Scheduler displayed wrong timestamp in email - fixed. 9) Dbvisit does not cope with commas in oracle parameter values when creating a standby database - fixed. 10) CSD: When bytes return empty results from dba_data_files, set to 0. 6.0.08 - (9 August 2011) New features: 1) Extend Dbvisit functionality to cope with closed threads in RAC environment. 2) AMM module is now called regardless of the fact some archive logs reside in ASM on the source, to process multiple archive destinations. ASM archive locations are skipped. 3) If log archive destination is not set up for the database, use default values of ORACLE_HOME/dbs/arch or ORACLE_HOME\rdbms, for versions 10.2+. 4) Separate checkpoint and log switch; Dbvisit now does not perform checkpoint during normal processing, only a log switch (if required). Fixes: 1) Global FLASH_DIR_NUM default value changed from 40 to 7. 2) When parsing a value for log_archive_dest*, check if extra attributes like MANDATORY etc are separated not only by a space but by a comma. 6.0.7 - Development release 6.0.06 - (15 July 2011) New features: 1) CSD now compares dbvisit installation between primary and standby and copies executables from primary if different. 2) Improved algorithm of searching for ASM archive logs in multiple locations, and under FRA-style date directories, to be shipped to the standby. 3) Allow one-way communication of Dbvisit Standby from primary to standby for ultra secure configurations which only allow one-way traffic. Set BLIND=Y to enforce this, but there is reduced Dbvisit Standby functionality (no checkums, no log gap reporting, no Resync and no creation of standby database options available). Fixes: 1) Dbvisit could not cope with Oracle reserved words used for tablespace names in SQL statements (like INDEX) - fixed. 2) Dbvisit restarted a database in restricted mode during shutdown that potentially lead to generating extra archive logs and issues during graceful switchover - fixed. 3) Global variable LOGDIR set to value of LOGDIR_DR on the standby server. 4) Queries of dictionary tables called by ora_list_dictionary function altered to format the display of checkpoint_change#. 5) Dbvserver scheduler was leaving behind zombie processes - fixed. 6.0.05 - Development release 6.0.04 - (9 June 2011) New features: 1) Variable SEND_HEARTBEAT2_TIME24 made redundant. Multiple times to send a heartbeat message separated by colon can be specified by variable SEND_HEARTBEAT_TIME24 2) Provide user feedback that Dbvisit is running the silent archive log gap report. 3) Release for all platforms. Fixes: 1) Dbvisit could not locate trace files while running AMM module in windows environment - fixed 2) When running -R, do not run silent inspect (RUN_INSPECT=Yes) as this meant Dbvisit is contacting the standby database twice. 3) Compatibility with IE9 resolved. 6.0.02 - (23 May 2011) "Dbvisit" is now renamed to "Dbvisit Standby". New features: 1) Web-based interface using build in web-server named Dbvserver. Dbvisit Standby can be now be run through: - traditional command line interface (CLI) or - graphical user interface (GUI) through browser. Dbvserver needs to be started to enable the Dbvisit Standby interface through the browser. On Linux/Unix type dbvserverd to start Dbvserver. On Windows start the Dbvserver Windows service to start Dbvserver. 2) Dbvserver includes a full scheduler to be able to schedule Dbvisit Standby. An external scheduler such as cron are no longer required. 3) Dbvisit is now installed into a new subdirectory called "standby" under the main "dbvisit" directory. 4) Full web-based access to the Dbvisit logs on the primary and standby server. Full access to the Oracle alert log throug the web browser. 5) Graphical reports showing key information about the standby database process such as lag, compression ratio, size of transfer, time taken for transfers, total redo per day, and total transfers per day. 5.3.12 - (5 May 2011) New features: 1) Automatically run Dbvisit archive log gap (dbvisit -i) when Dbvisit is run on the primary server. Can be turned off with variable RUN_INSPECT. 2) Remove temporary Dbvisit files and closing shared database session after creation of standby database. 3) Archive management log name can now be set in DDC file with ARCHSOURCE_LOG and ARCHDEST_LOG. If not set then default value is _arch_management.log 4) Global RECOVERY_PARALLELISM introduced to control parallelism for database recovery. Fixes: 1) Misleading message regarding the DDC file name when BINDIR set to wrong location - fixed. 2) Extra comma removed from an sql query to obtain DDR version. 3) Dbvisit errors when the last non archived sequence cannot be obtained from data dictionary on the primary - fixed by setting sequence as max archived sequence +1. 4) Improved locking introduced to control locking when previous version of dbvisit executable is still running. 5) Do not send log gap report when TRANSFER_LOG table empty or with -R option - this disables copying installation to the standby. 6) Global RECOVER_NOPARALLEL11 made redundant and removed. 7) A query to obtain log_archive_dest for Oracle 8/9 changed to accommodate various values that optimizer_mode can be set to. 8) Global variables related to a server role (primary or standby) rather than a server name, are now not reversed after Graceful Switchover (GS). 9) Dbvisit does not handle creating standby database with filesystem OMF files using transportable media - fixed. Now uses RMAN COPY command instead of operating system COPY command. 10) Bug with with managing trace file. Managing archives and traces should be separate and should not interfere or be dependent upon each other - fixed. 5.3.11 - Development release 5.3.10 - (17 March 2011) New features: 1) Introduced new variable ARCHTMP to enable temporary location of ASM archives on primary server before transport. This is different from the location specified by ARCHDEST. 2) Increased searchability for Dbvisit to find archive log files in ASM. 3) Improved performance for validating files by checking unique paths only during creation of standby database. 4) Improved algorithm of recovering new primary database during last stage of graceful switchover. Allows primary database archive logs with a different format from the standby archive logs. This is usually the case when log_archive_dest on primary points to a name of an ASM diskgroup. 5) Support of %%ORACLE_SID%% variable in log_archive_format for Windows. 6) Improved algorithm of finding archive log destinations on the primary server. Fixes: 1) When ARCH_ALT_LOCATION is set to a valid directory on the primary server, Dbvisit should only check this directory for archives to transfer to the standby server - fixed. 2) Dbvisit failed to manage trace files on Windows platform - fixed. 3) Reverse variables ORACLE_SID_ASM and ORACLE_SID_ASM_DEST after Graceful Switchover. 4) During graceful switchover in RAC, Dbvisit may not ship all subsequent archives after RAC instance shutdown - fixed. 5) Avoid shipping duplicate archive during graceful switchover - fixed. 6) Record thread# into Dbvisit repository table for single thread databases. 7) Dbvisit no longer does multiple log switches on the RAC instance during graceful switchover when RAC_TAKEOVER=Y and one RAC node is down. 8) Allow for mixed language messages generated by Oracle server during standby database recovery. 10) Recover standby database with a APPLY_DELAY_LAG_MINUTES clause issue - fixed. 11) Verify directory existence on remote server issue - fixed. 13) Issue with WIN_SERVICE_WAIT for Windows that resulted in reducing the WIN_SERVICE_WAIT value by 5 seconds automatically - fixed. 5.3.09 - Development release 5.3.08 - (29 January 2011) New features: 1) Drop tempfiles on standby on completion of graceful switchover for oracle versions 11.2+. As a workaround for Oracle bug: 10292173: "This bug causes rman backups to fail if the tempfiles on the standby are more recent than on the primary". Fixes: 1) Use db_unique_name instead of ORACLE_SID to access subdirectories under flash recovery area. 2) Allow for different syntax of the asmcmd command to obtain asmcmd version. Previously caused Dbvisit call to asmcmd to hang. 3) Improved logging for a remote execution of starting the standby database from the primary server. 4) Make sure datafiles are given unique names when copied to/from temp location during CSD (Creation of Standby Database). Previously datafiles with different paths but same basenames overwrote each other. 5) Ensure archive log gap report and heartbeat messages are sent to SUCCESS_MAILTO address if SUCCESS_MAILTO is set, not to ADMINS. 6) Improve the graceful switchover option for RAC. Previously the log gap would not always be 0 to initiate the switchover. This is because the ALTER SYSTEM ARCHIVE LOG was done on the database level and not on the instance. Setting INSTANCE_CLAUSE_FOR_ARCHIVE_LOG_CURRENT = Y will add the optional INSTANCE clause to the ALTER SYSTEM ARCHIVE LOG command. 7) Fix issue in AMM where it did not delete archives when number of archives reached the number specified by NUM_ARCHSOURCE_TO_KEEP. 8) Fix issue in AMM where under some circumstances it deleted newer archives first. 5.3.07 - Development release 5.3.06 - (17 December 2010) New features: 1) Change the name pattern for dbvisit trace files to use DDC rather than ORACLE_SID. 2) Check if primary database is in hot backup mode before starting CSD. (Create standby database). 3) Support function to collect and mail standby database trace files. Usage: dbv_functions -a DDC get_stdby_traces primary_trace_name:[offset] 4) Improve tracing information for dbv_functions. Now displays the switch in the trace file. 5) Added a global USE_LONG_SERVER_NAME to allow the use of long server names. Example: server names db1.atlas.domain.com and db1.zeus.domain.com can now be used. Previously Dbvisit would only use the shortname which would be db1 in both cases. 6) Dbvisit heartbeat file dbv_heartbeat_DDC.lck introduced to improve the logging and tracing of the heartbeat functionality. 7) Set standby_file_management=auto on standby database creation completion. 8) Added global ARCHSOURCE_BACKUP_COUNT for the AMM module. When this is set > 0, Dbvisit will only remove the archive log file on the primary server if it has been backed up by RMAN. The count refers to the number of times it has to be backed up by RMAN before being removed by Dbvisit. 9) Changed default value for JOBHIST and JOBHIST_DR to dbvisit_DDC.hist. 10) Added setting to ignore certain ORA error codes if required. 11) Improvements to the way Oracle databases are started and stopped. A further check is now made after stopping to ensure the correct status of the database. 12) More Oracle database dictionary information is listed in the trace file for the standby database. Fixes: 1) _INIT_ORA_REMOVE was defined as a list of two strings instead of one - fixed. 2) Dbvisit shuts down primary database using "shutdown normal" - changed to "shutdown immediate". 3) Globals $SEQ_LENGTH_FORCE and $THREAD_LENGTH_FORCE introduced to overwrite $SEQ_LENGTH and $THREAD_LENGTH values. SEQ_LENGTH is reset to 5 only for oracle version < 11.2 (windows). 4) Removed \ at the end of a certain paths to improve verification. 5) Improved ability to deal with ASM filenames. 6) Replaced checksum verification for datafiles with file size verification for creating standby db when files are copied directly to the standby server. 7) Replaced exit code 768 with 770 to fix child exit code issue. 8) Provide fix for ORA-10878: parallel recovery slave died unexpectedly for Oracle 11 by adding the clause "noparallel". 9) Bug fixed for Oracle RAC when RAC has more than 2 nodes. 10) Ignore Oracle log_archive which are set to REMOTE destinations. 11) Do not allow the user to change the value of parameter db_name (in CSD). 12) Remove PFILE global from documentation, this is no longer needed. 5.3.05 - Development release 5.3.04 (14 September 2010) New features: 1) Allow setting the ASM instance name to non-default value during Dbvisit DDC setup. 2) Confirm user choice in case the user chooses to terminate dbvisit setup when creating a standby database. 3) Add a "bulk rename" functionality to the standby creation wizard to allow renaming standby database files automatically. 4) Improve screen prompts by adding extra information (suggest running dbvisit to complete creating standby database, and adding tempfiles to a database after activation of a standby database). 5) New dbv_function display_datafile_header is introduced to display information about datafiles that need recovery. 6) Added functionality for Dbvisit to create a datafile in the OMF-enabled standby database when a datafile is created in the primary database. Fixes: 1) Extend the list of Oracle database parameters to be set to default values when creating a standby database using Dbvisit. 2) Extend Dbvisit documentation to cover specifics of creating a standby database for ASM and OMF. 3) Dbvisit created repository tables under the SYS schema if FORCE_SYSDBA was set to Yes - fixed. 4) During creation of standby database Dbvisit could not handle Oracle database parameters values that contained single or double quotes - fixed. 5) Issues when creating an ASM standby database version 10.1, as asmcmd 10.1 does not display error codes - fixed. 6) When running Dbvisit for multiple DDC configurations on the same primary server, under certain circumstances dbvisit processes related to different DDC configurations can interfere with each other while compressing archive logs to be sent to standby servers - fixed. 7) In some environments output of SELECT statement is not formatted as expected when using to_char SQL function - fixed. 8) A criteria to establish if a database file is OMF was not clearly specified - fixed, based on Oracle definition of an OMF file. 5.3.03 - Development release 5.3.02 (16 August 2010) New features: 1) ASM support. The standby database can now be created in ASM as well, the Oracle proprietary file system format. This completes the types of standby databases that can be created with Dbvisit. 2) Templates. To make the disaster recovery process simpler, faster and more convenient for DBAs the Dbvisit standby database creation wizard now includes the option to create a template. This template stores all the information on how the standby database was created. When the standby database needs to be recreated, for example after a failover situation, this template can be used for fast and simple recreation. 3) Transportable Media support. Some databases are too large to transfer across the network. Now the Dbvisit standby database creation process includes an option to interface with a local removable disk. This disk can then be manually transported to the remote site where the creation of the standby database can be restarted and completed. 4) Ability to customize the standby pfile/spfile settings before creation of the standby database. These settings will be saved in the template for easy recreation of the standby database. 5) Dbvisit installation, upgrades and creation of standby databases can now be scripted to run in batchmode for simple and efficient deployment. 6) Rsync transfer method. DBAs now have the ability to use Rsync as the data transportation mechanism on Linux and Unix, facilitating efficient restarts when there are network issues or large file transfers. 7) Oracle database parameters for the standby database can now be customized and saved in the template. Fixes: 1) Dbvisit now recognises special characters @(ORACLE_SID) and ?(ORACLE_HOME) in database files names. 2) Improved algorithm of parsing of SQL commands output to detect errors. 5.2.30 (27 July 2010) New features: 1) Allow the use of other external non sendmail clients on Linux/Unix. Use MAILCFG_SENDMAIL_CLIENT to set the full path of the client. 2) Update Dbvisit man pages. Fixes: 1) Correct default Oracle password file for Windows. 2) In some cases, Oracle SID information was not obtained from registry in Windows 64bit. 3) Improve error message when Oracle Windows service cannot be stopped or started. 4) Improve locking mechanism on Windows. In some cases the pid lock file does not get removed after successfully running Dbvisit. 5) Activation of standby database may not update the Dbvisit repository correctly. Initiating a Graceful Switchover after failover may result in error: ORA-00001: unique constraint (DBVISIT.DBV_TRANSFER_LOG_PK) violated This has been fixed. 6) Change creation of tempfile from bytes to Mb. If the file is too big then error "ORA-02237: invalid file size" may result. This has been fixed. 7) If SOURCE or DESTINATION host names are set to long names, then Dbvisit does not use the correct starting sequence after graceful switchover. 5.2.29 - Development release 5.2.28 (18 June 2010) New features: 1) Allow for Data Guard configurations to co-exists with Dbvisit. - Allow for VALID_FOR parameter. - Ignore standby redo log files in controlfile creation. Fixes: 1) Remove a prompt for pfile name if PFILE is not found on the server during creation of standby database. 2) Set SOURCE and DESTINATION variables to short server names. 3) Change variables _SEQUENCE_LANG_NAME and _ASM_EXCLUDE to quoted strings instead of lists. 4) Change the query to obtain archive log names to ignore log archive destinations pointing to standby locations (used by Data Guard). 5) Oracle 8i may contain incorrect location in v$archive_dest - Fixed. 6) Does not use the correct SQL statement to obtain the standby database sequence for Oracle 8 and 9 - Fixed. 7) Ignore dynamic memory location parameters and parameters related to other instances in spfile/pfile when creating standby database. 8) When LOGDIR_DR is not set correctly there was an error message about incorrect mail settings - Fixed. 5.2.27 - Development release 5.2.26 (5 May 2010) New features: 1) SOURCE and DESTINATION host name variables are now not case sensitive for Windows. 2) Display a message "please wait" to the user to indicate that Dbvisit may take some time to delete old archive files when running AMM (Archive Management Module) on the primary server. 3) Improve the ability to obtain the standby database sequence when the standby database sequence is 1. 4) Add message to SUCCESSMAIL emails on how to turn off success mails and only email on alerts. 5) Add option to use existing pfile/spfile on standby database during standby database creation. Fixes: 1) Capture more information when another instance of Dbvisit is running on Windows to ensure it can be started or not. 2) During creation of standby database on Windows, Dbvisit may error when COMPRESS variable is set to ssh in a DDC file - Fixed 3) Dbvisit may error with the primary and the standby databases having redo logs with the same names under different logfile group numbers during Graceful Switchover - Fixed 4) In rare cases Dbvisit may error when trying to clean up trace files if a file has already been deleted by another dbvisit process running at the same time - Fixed. 5) When the user renames oracle init parameters while creating standby database, Dbvisit edits both standby pfile and spfile. If the standby database uses spfile, only spfile should be edited not pfile - Fixed. 6) Dbvisit does not capture ORA-12638 error message - Fixed. 7) Make the global variable PFILE non case sensitive for Windows while creating a standby database 8) While checking oracle database parameters pointing to ASM locations on primary when creating a standby database, dbvisit considers all parameters values that contain symbol + to be ASM locations which is not always the case - Fixed 9) In some cases fuser incorrectly reports file in use on HP-UX. 10) Remove REMOTE_LISTENER parameter from init.ora when creating standby database. 5.2.25 - Development release 5.2.24 (22 March 2010) New features: 1) If SUCCESS_MAILTO is set, then the Dbvisit daily heartbeat emails go to this email address instead of ADMINS. Fixes: 1) Dbvisit does not pick up the correct pfile to transfer to the remote server while creating standby database when the primary database does not use an spfile. 5.2.23 - Development release 5.2.22 (12 March 2010) New features: 1) Dbvisit now allows the Oracle admin directories on standby to be different from the primary database during creation of the Standby Database. Fixes: 1) Dbvisit does not pick up the correct sequence for RAC on the standby when NLS is set to Spanish. 2) Fix issue with quotes around multiple email addresses: can't extract address at .. 3) Improve obtaining asmcmd version for Windows. 4) Dbvisit does not pick up the archive log destination when NLS is set to Spanish during graceful switchover. 5) Create standby database may fail in Oracle 8i due to long tablespace names. This has been fixed. 6) Update check and add more tracing to determine if previous Dbvisit process is still running. 7) Update dbvisit help text. 8) If Dbvisit is unable to create Windows Oracle service during creation of standby database, Dbvisit will suggest to create the service manually. 9) Ignore the following SQLPLUS error message when creating Dbvisit repository using dbvisit_setup: Error accessing PRODUCT_USER_PROFILE Warning: Product user profile information not loaded! You may need to run PUPBLD.SQL as SYSTEM 10) Dbvisit will detect if ORACLE_HOME_DR is set to a non-existing or not valid directory on the standby server when creating a standby database and display a warning. 11) Dbvisit may not correctly detect the creation of Oracle Windows service in other languages during creation of standby database. This has been fixed. 5.2.21 - Development release 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 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 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 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 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.