VENDOR UPDATE | 12 November 2017
Dbvisit Standby Version 8 Latest Updates
Dbvisit Standby supported platforms
Latest release 8.0.16 (9 November 2017)
Linux | - Linux 64bit (OEL (5,6,7), RHEL (5,6,7) and SLES (11,12) |
Windows | - MS Windows 64bit (MS Windows 2008 and above) |
Supports Oracle 11.2 and above |
Standby Version 8 Latest Changes
8.0.16 (9 November 2017) Changes:
- DS-460: Allow Synchronize Standby Database (SYNC) option to be restartable and able to use transportable media
- DS-859: Remove temp files created on the standby server by Dbvisit processes spawned by daemon
- DS-874: Provide optional post processing option to compress archives under ARCHDEST
- DS-883: Correct a typo in Dbvisit standby components uninstaller
- DS-891: Use release major version number only following a switch to GIT
- DS-893: Fix log gap report showing wrong instance name for threads other than one
- DS-894: Avoid archive logs being deleted from ARCHDEST until transferred to Cascade Standby
- DS-895: Use SRVCTL rather than SQLPLUS to open a Clusterware registered standby read only
- DS-896: Restart newly activated database on a database rather than instance level
- DS-901: Make sure log gap report fails unless the standby is mounted or read only
- DS-905: Generate support package when DBVISIT_DEBUG is set to 0
- DS-909: Implicitly set database parameter instance_mode to READ-WRITE on the standby during CSD
- DS-910: Make sure APPLY_DELAY_LAG_MINUTES and DMN_MONITOR_INTERVAL_DR are not both set
- DS-913: Fix daemon resetting AMM_CHECK_TRANSFERRED to N
- DS-914: Improve mechanism of switching the standby to recovery mode when APPLY_READ_ONLY set to Y
- DS-916: Make sure pre- and -post- processing scripts are called even when the database instance is down
- DS-917: Make sure installer sets correct dbvserver name and does not keep the 0.0.0.0 placeholder
- DS-918: Correct syntax error when starting a database read only using SRVCTL
- DS-919: Add --force option to "-o upgrade", for testing purposes
- DS-921: Make db_file_name_convert and log_file_name_convert case insensitive
- DS-922: Make sure PDBs get started on the new primary on completion of GS
- DS-923: Small improvement when restarting a database
- DS-924: Transfer a list of primary datafiles to the standby during CSD, to be potentially used for post-processing
- DS-925: Improve conversion of datafile names during CSD when conversion is set between two ASM diskgroups
- DS-927: Improve parsing db_file_name_convert when one "from" string is a substring of another "from" string
- DS-928: Improve logging generated by running log gap report when RUN_INSPECT set to Y
- DS-930: Use file mtime rather than ctime when picking up the latest compressed or uncompressed log to apply
- DS-931: Add DDC string to generic support package name
- DS-932: Check if restore points are set in the old primary prior to GS
- DS-934: Re-transfer a file if checksums do not match during file transfer
- DS-935: Add missing globals to a list of globals available to the user when editing a DDC via GUI
- DS-939: Display warning during CSD prechecks if primary is in NOLOGGING
- DS-948: Issue with db_create_online_log_dest_n being ignored affecting CSD and GS
- DS-952: Improve handling foreign language strings when parsing output during recovery
- DS-954: Improve handling tempfiles extended beyond max size, which could cause error during Graceful Switchover
- DS-956: Improve algorithm of applying convert parameter to a filename in mixed ASM and Windows environment
- DS-957: Treat temp files that belong to SEED container as OMF during GS
Further Help and Assistance
For further advice about Dbvisit Standby and Dbvisit Replicate, including product sales, installation and support services, please contact one of our pre-sales technical team on 0330 332 6223 or visit our website nlightn-IT.com
Latest Articles
- 22 October 2021
Oracle Database Critical Patch And Security Update October 2021 - 22 July 2021
Oracle Database Critical Patch And Security Update July 2021 - 26 April 2021
Oracle Database Critical Patch And Security Update April 2021 - 22 January 2021
Oracle Database Critical Patch And Security Update January 2021 - 27 October 2020
Oracle Database Critical Patch And Security Update October 2020 - 16 July 2020
Oracle Database Critical Patch And Security Update July 2020 - 15 April 2020
Oracle Database Critical Patch And Security Update April 2020 - 23 January 2020
Oracle Database Critical Patch And Security Update January 2020 - 16 October 2019
Oracle Database Critical Patch And Security Update October 2019 - 17 July 2019
Oracle Database Critical Patch And Scurity Update July 2019