Get free Dbvisit trial version.

Dbvisit - The ultimate Oracle Standby Database solution

Dbvisit Changes

5.2.14 (12 June 2009)

New features:

1. Provide the ability to logon with sys user and password. This can be used when sysdba logon without password cannot be used or when SQLNET.AUTHENTICATION_SERVICES= (NTS) cannot be set.
2. Improve message for error 837, sqlplus not found.
3. Improve message for ORA-01031: insufficient privileges.

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.

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 rebuild).

5.1.28 (6 April 2009)

Fixes:

1. Add specific SP2-0734 error.
2. Ignore set pause on setting in login.sql.

5.1.27 (20 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.

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.

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 (28 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 (19 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 (Internal release)

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 (3 April 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.

• Simple to install and configure.
• Completely hands-off Oracle Standby Database management.
• Database does not need to be shutdown or restarted to install Dbvisit.
• No extra init.ora or spfile parameters needed.
• Precise Control over updates (snapshots).
• Dbvisit will automatically recover from database and network failures.
• Database role switching.

• Oracle databases running with Dbvisit are fully supported by Oracle.
• Full technical support and updates are provided for Dbvisit.