We're here to help!

Dbvisit Standby version 6.0.60 (24 April 2014) released

Follow

Dbvisit Standby Latest Changes Listing 

For full detail history listing, please see http://www.dbvisit.com/products/standby_latest_changes_v6/

 

6.0.60 - (24 April 2014)

Fixes:

  1. Minor internal improvement on obtaining sequence# and SCN numbers from standby database when Oracle 8.1.7 is used
  2. Minor internal improvements regarding OMF redo log management on standby databases, to ensure redo logs are multiplexed on completion of Graceful Switchover
  3. Minor improvements when obtaining required SCN and sequence numbers remotely from standby
  4. Dbvisist fails to detect another dbvisit process is already running on Windows when Dbvisit is scheduled using a full path to an executable - fixed

 

6.0.58 - (26 February 2014)
Fixes:

  1. Improve internal Dbvisit Standby Repository (DDR) cleanup procedure on the DBV_TRANSFER_LOG table when Multiple Threads (RAC) are used
  2. Internal improvement when using multiple threads in Graceful Switchover and one instance is shutdown (thread not active or closed)

 

6.0.56 - (31 January 2014)
Fixes:

  1. Update Graceful Switchover (GS) internal checks when primary is ASM and the standby database is not making use of ASM
  2. Update internal checks where Oracle Managed Files (OMF) is used, taking into account OMF files in uppercase on Windows platforms
  3. Minor fix implemented in Web Based interface when running commands against a database not currently running
  4. Improve backup function, detecting if existing datafiles are in already in backup mode
  5. Improve adding of OMF datafiles to standby database when db_file_name_convert parameter is set

 

6.0.54 - (17 December 2013)
Fixes:

  1. Implement change to cater for Windows OracleASMService+ASM service
  2. Added new variables ARCHIVED_WAIT_RETRY_SEC and ARCHIVED_WAIT_MAX_SEC to address a delay with an archived log to appear in v$archived_log
  3. Fix minor issue with Dbvserver (GUI) closed socket handling
  4. Minor improvment when last archived sequence cannot be obtained

 

6.0.52 - (13 September 2013)
Fixes:

  1. Allow primary database to be in restricted mode when Graceful Switchover is started
  2. Improvements to internal function ora_recovery_scn to check for missing datafiles
  3. Disable disk space check for Archivelog Management Module (AMM) when THRESHOLD_ARCHSOURCE=0 or THRESHOLD_ARCHDEST=0
  4. Implement fix to resolve "Can't locate object method" error when the dbvisit standby shared connection is used
  5. Various improvements when Dbvisit Standby shared connections are used.  During normal send operation two sessions will be noticed, one for sysdba connections and one for normal connections

 

6.0.50 - (20 July 2013)
Fixes:

  1. Fixed file and directory browser in GUI (Dbvserver) (Setup => New)
  2. Extended logging and wait interval when Windows Oracle Database service cannot be obtained
  3. Update licence agreement text and Windows Installer Signed Certificate
  4. Improve add datafile function when datafiles are added to the SYSTEM tablespace
  5. Delay lag will be ignored when running the Synchronize Standby database option.  Added additional warning message to be displayed in command line interface if this option is executed with the delay lag set
  6. Added an additional check to review if the standby is behind current time prior to running a recovery session if delay lag is specified.
  7. Improve compression mechanism when "dbvisit" and "gzip" compression is used for archive log management and transfer between primary and standby databases.  These new improvements will also avoid potential issues when compression is used with multiple standby databases as well as ensuring archive log compression does not impact potential RMAN backups running at the same time.  As of version 6.0.50 it is recommended to set the following value in the Dbvisit Database Configuration (DDC) file: "KEEP_ORIG_FILE_BEFORE_COMPRESS=Y".  For new installations the default value for this parameter will be "Y". This new change will also provide a minor performance improvement.
  8. Add additional step to truncate the dbv_register table on a new standby on completion of a Graceful Switchover (GS) otherwise the Archive log Management Module (AMM) might produce wrong results
  9. Improve functionality to maintain Oracle Windows Service and detect a non-existing service

 

Note:  Full listing is available here: http://www.dbvisit.com/products/standby_latest_changes/

 

 

Have more questions? Submit a request

Comments