We have released Dbvisit 5.2.26.

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.

Dbvisit 5.2.26 can be downloaded from our website. Please see the README.txt file included in the download for upgrade instructions.