We're here to help!

Dbvisit Standby 8.0.14 (9 November 2017) Released

Follow

Notes:  

  • Dbvisit Standby download for SLES 11 and 12 now available as of 8.0.10
  • Windows 2016 supported - 8.0.14 or higher recommended
  • Oracle 12.2 supported as of 8.0.12 release

 

8.0.16 (9 November 2017)
Changes:

  1. DS-460: Allow Synchronize Standby Database (SYNC) option to be restartable and able to use transportable media
  2. DS-859: Remove temp files created on the standby server by Dbvisit processes spawned by daemon
  3. DS-874: Provide optional post processing option to compress archives under ARCHDEST
  4. DS-883: Correct a typo in Dbvisit standby components uninstaller
  5. DS-891: Use release major version number only following a switch to GIT
  6. DS-893: Fix log gap report showing wrong instance name for threads other than one
  7. DS-894: Avoid archive logs being deleted from ARCHDEST until transferred to Cascade Standby
  8. DS-895: Use SRVCTL rather than SQLPLUS to open a Clusterware registered standby read only
  9. DS-896: Restart newly activated database on a database rather than instance level
  10. DS-901: Make sure log gap report fails unless the standby is mounted or read only
  11. DS-905: Generate support package when DBVISIT_DEBUG is set to 0
  12. DS-909: Implicitly set database parameter instance_mode to READ-WRITE on the standby during CSD
  13. DS-910: Make sure APPLY_DELAY_LAG_MINUTES and DMN_MONITOR_INTERVAL_DR are not both set
  14. DS-913: Fix daemon resetting AMM_CHECK_TRANSFERRED to N
  15. DS-914: Improve mechanism of switching the standby to recovery mode when APPLY_READ_ONLY set to Y
  16. DS-916: Make sure pre- and -post- processing scripts are called even when the database instance is down
  17. DS-917: Make sure installer sets correct dbvserver name and does not keep the 0.0.0.0 placeholder
  18. DS-918: Correct syntax error when starting a database read only using SRVCTL
  19. DS-919: Add --force option to "-o upgrade", for testing purposes
  20. DS-921: Make db_file_name_convert and log_file_name_convert case insensitive
  21. DS-922: Make sure PDBs get started on the new primary on completion of GS
  22. DS-923: Small improvement when restarting a database
  23. DS-924: Transfer a list of primary datafiles to the standby during CSD, to be potentially used for post-processing
  24. DS-925: Improve conversion of datafile names during CSD when conversion is set between two ASM diskgroups
  25. DS-927: Improve parsing db_file_name_convert when one "from" string is a substring of another "from" string
  26. DS-928: Improve logging generated by running log gap report when RUN_INSPECT set to Y
  27. DS-930: Use file mtime rather than ctime when picking up the latest compressed or uncompressed log to apply
  28. DS-931: Add DDC string to generic support package name
  29. DS-932: Check if restore points are set in the old primary prior to GS
  30. DS-934: Re-transfer a file if checksums do not match during file transfer
  31. DS-935: Add missing globals to a list of globals available to the user when editing a DDC via GUI
  32. DS-939: Display warning during CSD prechecks if primary is in NOLOGGING
  33. DS-948: Issue with db_create_online_log_dest_n being ignored affecting CSD and GS
  34. DS-952: Improve handling foreign language strings when parsing output during recovery
  35. DS-954: Improve handling tempfiles extended beyond max size, which could cause error during Graceful Switchover
  36. DS-956: Improve algorithm of applying convert parameter to a filename in mixed ASM and Windows environmentDS-957: Treat temp files that belong to SEED container as OMF during GS

 

8.0.14 (20 June 2017)
Changes:

  1. DS-636: Allow for entering license key on completion of creating a new DDC
  2. DS-727: Allow to use trace file name instead of process id (pid) when creating a Support Package
  3. DS-760: Introduce "Blackout Window" functionality when scheduling Dbvisit via daemon process
  4. DS-818: New functions to extract data from repository tables in text and json formats
  5. DS-819: New option to schedule repository maintenance when running default send/apply of logs
  6. DS-820: Improve algorithm of applying logs on the standby when both compressed and uncompressed copies present (DS-873)
  7. DS-828: Copy repository to the standby server once changes have been made to it on the primary server
  8. DS-829: Improve cleanup of trace files following default Dbvisit run
  9. DS-851: Improve Create Standby Database (CSD) options in Central Console when using Oracle RAC configurations and templates
  10. DS-853: Make sure database connections are kept open when using daemon
  11. DS-856: Handle a scenario when parameter db_unique_name is not set in the primary spfile during CSD
  12. DS-858: Remove misleading messages inserted in history log by daemon
  13. DS-859: Make sure temp files created by Dbvisit processes spawned by daemon are removed on completion
  14. DS-864: Central Console - when spfile is present and enforced during Create Standby Database (CSD), template option is disabled
  15. DS-865: Provide a meaningful error message when an attempt to use -l (license) option on the standby server is made
  16. DS-866: When applying logs using either SQLPLUS or RMAN, skip logs with names ending in ".part" as being in use
  17. DS-867: Automatically reestablish RMAN connection opened by daemon if the database is restarted
  18. DS-868: Update internal API call for activate sync and no-sync options
  19. DS-869: Improved timestamp display in Central Console under Task History table - tooltip added with timezone of webserver
  20. DS-871: When performing CSD and GS, check if daemon has not been stopped on both sides and terminate
  21. DS-875: Improved handling of ASM Oracle Managed File (OMF) primary password file during Create Standby Database (CSD)
  22. DS-882: Improvements to Graceful Switchover between primary RAC and single instance standby
  23. DS-885: Fix upgrade of Dbvisit Standby Configuration file (DDC) - does not set CONFDIR_DR when called from Central Console

 

8.0.12 (11 May 2017)

Changes:

  1. DS-306: Implement fix to resolve error when using TLS sending email notifications
  2. DS-522: Improved error handling for sending email failures
  3. DS-578: Add new option to Central Console to open standby database read-only
  4. DS-716: Implement change to accommodate default spfile location when Oracle Restart is used
  5. DS-729: Add option to Create Standby Database (CSD) to re-use an existing spfile
  6. DS-730: Allow Create Standby Database (CSD) of RAC standby from Single Instance (Multi threaded database that was originally a primary). Important that original RAC database spfile must still be in place and the option to use an existing spfile must be used when detected during the CSD process
  7. DS-739: Display error message when running Create Standby Database (CSD) from Central Console, when the agent is not contactable
  8. DS-740: The Central Console parameters for the DDC or the database parameters are now sorted alphabetically
  9. DS-747: Allow for the option to register the standby database with Oracle Restart or Clusterware - if detected
  10. DS-748: Internal change to set DB_UNIQUE_NAME to DB_UNIQUE_NAME_DR on the standby when setting environment
  11. DS-750: Resolve issue where standby database does not recover when apply_delay_lag_minutes is set when running the dbvctl in daemon mode
  12. DS-751: Improve the way the Central Console display the source and destination following a Failover/Activation
  13. DS-752: Improve error handling during the DDC creation if one of the hosts (source or destination) is not available
  14. DS-753: Internal improvement to reduce amount of calls to standby server during Create Standby Database (CSD) process
  15. DS-756: Fix wrong status being displayed during Database Status checks using the Central Console
  16. DS-758: Internal change to repository to include use_existing_spfile_yn and srvctl_register_yn
  17. DS-763: Remove some logging of functions to the trace file
  18. DS-765: Add additional information to the support package - srvctl config database
  19. DS-766: Fix wrong license information being displayed in the central console - 2099
  20. DS-768: Add correct example of send_heartbeat_time24 to DDC file (should be ":" not "," as delimiter between times)
  21. DS-769: Fix issue where TLS/STARTTLS email notifications did not work
  22. DS-773: Improve handling of closed thread (when Oracle RAC is used) on standby when looking for next required SCN
  23. DS-780: Ensure all Create Standby Database (CSD) and DDC creation errors in the Central Console display the create support package option
  24. DS-781: Enable management of the repository in batch mode (--mode BATCH --action uninstall|install)
  25. DS-783: Fix wrong default port 4493 being displayed for dbvserver (should be 4433) in ./install-dbvisit -h
  26. DS-784: New options added to Central Console to allow for Registration of standby with Oracle Restart or Clusterware or the use of an existing spfile - during the Create Standby Database (CSD) process
  27. DS-787: Improved handling of Dbvctl daemon monitoring and applying logs on standby when Oracle RAC configurations are used where one thread is not as active as another
  28. DS-790: Improve support package to include dbvnet, dbvagent, dbvctl daemon and history log information
  29. DS-795: Fix send_heartbeat function to allow sending of emails
  30. DS-802: Improved support for Oracle 12.2 ASM configurations
  31. DS-803: Add additional use of srvctl for Oracle Restart and Oracle Clusterware environments
  32. DS-804: Add status and status description to json output of -o status when --mode GUI is used
  33. DS-805: Use correct spfile when starting standby database during Create Standby Database (CSD) when central console is used
  34. DS-806: Improve "dbvctl -h -f" to display help output regarding functions
  35. DS-808: Improved handling or Oracle Database 12.2 when password file is stored in ASM when Oracle RAC is used
  36. DS-809: Ensure correct error is reported when extract of a file from ASM failed
  37. DS-810: Fix issue where dbvctl incorrectly removed a lock file for an existing running process
  38. DS-811: Internal improvement on repository used by dbvagent and dbvserver
  39. DS-812: Improve function used to search for archive logs - especially where old logs were removed and later restored
  40. DS-813: Internal improvement in dbvagent on handling larger data packets during launch-updates
  41. DS-815: Add additional columns START_EPOCH and EPOCH to dbv_transfer_log and dbv_sequence_log
  42. DS-823: Remove direct copy method option when running Create Standby Database during a creation of a cascade database process. When using cascading standby databases, the direct copy method is not supported and this option is now removed
  43. DS-825: Support for Oracle Database 12.2
  44. DS-827: Create Standby Database (CSD) ignored USE_EXISTING_SPFILE_YN when set to Y - fixed
  45. DS-831: Internal change in preparation for upcoming reporting screens in later release
  46. DS-832: A number of AMM module variables do not get reset on each run of dbvctl Daemon run, but get appended to - Fixed
  47. DS-833: Fix issue where the resume Create Standby Database option did not work in certain scenarios when using the Central Console
  48. DS-836: Create the dbvisit standby repository if it does not exist during a failover/activation of a standby database
  49. DS-841: Copy dbvisit repository to the standby on successful application of a license key
  50. DS-846: Fix batch installation on Unix based systems where host names were not set correct for dbvnet, dbvagent and dbvserver
  51. DS-848: Internal change to improve handling of OracleService<SID> services on Windows for shutdown, startup, restart functions
  52. DS-850: Improve Synchronize Standby Database (SYNC) function to better handle newly added datafiles
  53. DS-854: Skip compressed archived logs when applying to standby using RMAN and Dbvisit Standby compression is disabled
  54. DS-855: Fix status check of Dbvserver and Dbvnet wrongly reporting as Dbvagent

 

 

8.0.10 (27 January 2017)
Changes:

  1. DS-719: Add new sample Linux startup scripts to DBVISIT_BASE/standby/doc folder
  2. DS-732: Internal change to address internal repository error "Error: file is encrypted or is not a database" 
  3. DS-733: Adjust order of creating new Redo Logs during Graceful Switchover (GS) to remove risk of Redo being left in a temporary location in case of an error during GS
  4. DS-734: Improve upgrade script executed during "dbvctl -d DDC -o upgrade" including improved handling of ORACLE_SID_ASM and ORACLE_SID_ASM_DR and ensuring that ORACLE_SID and ORACLE_SID_DR is not set if Oracle RAC is used and Dbvisit Standby version is 8 and above 
  5. DS-735: Resolve incorrect reporting of dbvctl Daemon/Backround process status as well as improved handling of PID files 
  6. DS-736: Add changes to allow Oracle RAC configurations where Dbvisit Standby is not using shared storage. For more detail see the Online Documentation (Advanced - Oracle RAC Configurations - https://goo.gl/ydzVkJ)
  7. DS-738: Internal change - skip tracing a directory listing of a missing archive log if the log is ASM
  8. DS-741: Improved handling of single tenant database - PDB state when running "dbvctl -d DDC -o restart" on standby server
  9. DS-744: Error being reported when using delay lag - Cannot open file: Media recovery complete (No such file or directory) - fixed

 

8.0.08 (18 January 2017)
Changes:

  1. DS-692: Check for dbvctl daemon running when performing CSD, GS or SYNC
  2. DS-701: Add additional dbvnet network testing options
  3. DS-710: Improved socket closing - dbvnet
  4. DS-711: Trace files were not always removed
  5. DS-712: Add new global CHECK_ARCHTMP (default value Y). If ARCHTMP in any Oracle Archive destiniations an error will be raised. Set to N to only have a warning message displayed
  6. DS-714: Resolve issue where running dbvctl as daemon/background process when ASM is used did not ship logs
  7. DS-717: Resolve upgrade issue seen when upgrading from 8.0.04 to later versions "Error Code: 2000"
  8. DS-718: Dbvisit Archivelog Management Module (AMM) did not remove archive logs that met criteria - fixed
  9. DS-720: When using Oracle RAC primary with single instance standby on Filesystem, an attempt to connect to ASM on standby is performed when not needed - fixed
  10. DS-721: During Create Standby Database (CSD) it failed on renaming standby redo to ASM diskgroup names - fixed
  11. DS-725: During the creation of a new DDC, changing the Source Host after initial selection caused problems
  12. DS-728: Error Code 2000 during Windows database status check - fixed

 

8.0.06 (22 December 2016)
Changes:

  1. DS-593: Internal change - adding additional logging information when performing local file copy
  2. DS-630: Introduce new feature to Windows systems to allow for Windows service to be created for each DDC on the primary and standby servers to be used for automated log shipping and applying without using a Windows Scheduler. Users can now use either the Windows scheduler or this new option.
  3. DS-631: Add additional check to ensure file id is provided when refreshing only one datafile
  4. DS-633: Add function to copy repository from primary to standby: dbvctl -f ship_repo -d <ddc>
  5. DS-643: Add additional information to the support package
  6. DS-655: Enhance DDC upgrade process when using the Central Console
  7. DS-664: Add additional checks to Edit Configuration (DDC) screen to resolve strings to be added to DDC
  8. DS-665: Improve logging of expected ORA-01034 error messages
  9. DS-667: Add additional tracing of database parameters during Graceful Switchover (GS) 
  10. DS-668: Fix misleading notification about log switch being performed 
  11. DS-669: Improve logging mechanism for Dbvnet, Dbvserver and Dbvagent
  12. DS-670: Central Console - Improve page transition and error formatting on Graceful Switchover page
  13. DS-671: Improve pattern search when removing trace files during tracefile maintenance
  14. DS-672: Central Console - Internal improvements on page loading and DDC/dbvctl version handling
  15. DS-673: Improved internal error handling - error code 2000
  16. DS-674: Use the same method to obtain archive log names when shipping to standby and during Graceful Switchover
  17. DS-676: Display a meaningful message when no databases is detected on a server during DDC creation
  18. DS-577: Show additional PDB status informaiton when checking database status
  19. DS-680: Incorrect description in DDC file for DMN* variables (min vs sec)
  20. DS-682: Update Windows Installer to handle new dbvsmgr utility. The new dbvsmgr utility is only used and available on Windows based installations and is used to manage Dbvisit Standby services for Dbvnet, Dbvagent, Dbvserver as well as the new dbvctl background processes (deamon) - one per DDC per server - if enabled 
  21. DS-683: Handle scenario where variable is declared more than once in DDC file
  22. DS-685: Implement new improved logging module for Dbvnet, Dbvagent and Dbvserver - clearing all old log files when upgrading from earlier version is recommended
  23. DS-686: Remove internal error message during upgrade error messages
  24. DS-687: Add additional check to ensure ARCHSOURCE and ARCHDEST is not the same as any of the database archive log destinations or the database recovery area. These locations (ARCHSOURCE and ARCHDEST) are specific to Dbvisit Standby and should never be located in the database archive log or recovery area destinations
  25. DS-688: Fix Dbvisit Archivelog Management Module (AMM) error where archive logs are not removed (managed) on primary - if enabled 
  26. DS-690: Central Console - Minor style corrections
  27. DS-693: Do not error when license check is perfomed and no licese key provided
  28. DS-694: Internal improvements on Create Standby Database (CSD) batch process
  29. DS-696: Improve message when license key expired
  30. DS-698: Fix issue where Graceful Switchover (GS) in an Oracle RAC to single instace database fail in final steps during redo log recreation
  31. DS-699: Resolve issue where DDC is upgraded from CLI and Central Console does not detect this, selecting the upgrade option from the Central Console will now recognise that the CLI performed the upgrade 
  32. DS-702: Add new feature to handle network problems where tasks are successfully executed from Central Console, but incoming updates from Agents are not detected (example possible firewall blocking of port 4433)
  33. DS-703: Central Console - Replace various dual-selection components with improved single-click elements. Currently the database action page is affected, in particular the Database and Daemon group action buttons
  34. DS-705: Update installer to cater for various new upgrade functions 
  35. DS-707: Central Console - resolve issue where deleted Hosts from the hosts repository table can cause unexpected results - example displaying incorrect connection statuses next to incorrect Hosts
  36. DS-708: It is no longer possible to delete hosts that are currently part of a known DDC. You can still attempt it, however a red error message will be displayed
  37. DS-709: Central Console update - When a DDC is upgraded to a newer version, only that particular DDC table row record is refreshed, instead of the entire configurations table.


Note: When upgrading from 8.0.0x to 8.0.06 and above, we recommend you stop Dbvserver, Dbvnet and Dbvagent and remove all old log files located in their respective "log" sub directories (dbvisit/dbvserver/log/, dbvisit/dbvnet/log/, dbvisit/dbvagent/log/)

 

8.0.04 (14 November 2016)
Changes:

  1. DS-634: Internal update to resolve corrupt support package trace file on Windows based systems
  2. DS-638: Incorrect handling of log_archive_dest_n parameters during CSD - fixed
  3. DS-639: Add additional internal tracing
  4. DS-640: Minor Central Console style changes - import button on Configuration Page
  5. DS-641: Do not use HOSTNAME_CMD if not set - can happen when upgrading from version 7 to version 8
  6. DS-642: Add support for case-insensitive hostnames in Central Console that was affecting Windows based systems
  7. DS-643: Add additional information to support packages - listing of latest 50 files in ARCSOURCE and log locations
  8. DS-644: Email - add trace file name in success emails
  9. DS-645: Email messages when using Daemon on linux appended old details - now fixed
  10. DS-646: Add maximum number of attempts to send email on failure - configurable with DMN_MAX_FAIL_NOTIFICATIONS
  11. DS-647: Do not send email notification if Daemon is stopped with USR1 signal
  12. DS-648: Improved query on v$archived_log when archive logs detected on filesystem (due to RMAN catalog) and ASM
  13. DS-649: Central Console - improved error handling when adding new host and agent cannot be contacted or passphrase is wrong
  14. DS-650: Improved insert into internal repository table (TRANSFER) to better handle multiple standby databases for same primary 
  15. DS-651: Improved naming of trace files for Daemon process
  16. DS-652: Dbvnet internal change to better handle closing connections on server side when multiple connections received at exact same time
  17. DS-653: Fix upgrade of 8.0.0x where NETPORT was mistakenly set to 22 ignoring already set NETPORT
  18. DS-654: Improve handling of DDC Version and dbvctl version and performing upgrade of DDC files - upgrade of DDC files must be executed following a software upgrade
  19. DS-656: Log Gap report in Central Console showed thread numbers as n-1 - fixed
  20. DS-657: Clear local and remote trace file listing in memory during Daemon/Background execution 
  21. DS-658: Ensure Support Packages can include Daemon background process trace files
  22. DS-659: Execute HOSTNAME_CMD if enabled and upgrading an existing DDC file
  23. DS-660: Do not send mail when INT or TERM signals received (CTL-C)

 

8.0.02 (8 November 2016)
Key New Features & Enhancements:


1) New directory structure
2) New enhanced network communication - Dbvnet
  - All communication is encrypted by default
  - New compression option introduced
3) New Dbvisit agent (dbvagent) and web server (dbvserver)
4) New web based user interface (GUI) - Dbvserver
  - Manage one or more Primary/Standby configurations from one web based console
  - Dbvisit Standby Core components (Dbvnet, Dbvagnet and CLI) must be installed on primary/standby servers
  - Communication between Central Console and Agents are encrypted
  - Central Console cater for more than one user (two roles - Administrator and User)
  - Core tasks can be performed by Central Console including:
    - Create Standby Database
    - Manage Dbvisit Standby Configuration (DDC) file
    - Manage Licensing
    - Send and Apply logs
    - Re-syncrhonize the Standby Database due to unrecoverable archive log gap or nologging operations
    - Graceful Switchover
    - Activation (Failover)
    - Reporting - Log Gap Report
5) Graceful Switchover (GS):
  - Run only from one node (primary or standby)
  - Improved performance
  - Better handling of redo logs
  - No requirement for unique keys during execution
6) Enhanced Create Standby Database (CSD)
7) Dbvisit Standby repository stored outside the Oracle database
8) Dbvisit Standby Command Line Interface - CLI, is now one executable "dbvctl"
9) New API interface (see dbvctl -h)
10) Various new functions. Most functions are exposed see "dbvctl -f -h"
11) Enhanced error handling
12) New Support Package option is introduced
13) Enhanced tracefile management
14) New Oracle RAC management
  - New option to create Oracle RAC enabled Standby Database (conditions apply)
  - Dbvisit Standby components are now more RAC Aware and cluster resources can be created
  - Dbvisit Standby is now run from only one node in the cluster
  - Upgrading from version 7 to version 8 when using Oracle RAC will require new DDC files to be created
15) Support for creating Cascading Standby Databases (conditions apply)
16) Support for Oracle 12c Multitenent option in Oracle 12c SE2 (Single Tenant for Oracle Standard Edition Two)
17) Various internal improvements and fixes

Note: Operating System support in 8.0.02 limited to the following:

  • Microsoft Windows 2008 and above (64bit)
  • Oracle Linux 5,6 and 7 (64bit)
  • Red Hat Enterprise Linux 5,6 and 7 (64bit)

 

----------------------------------------
Beta and Release Candidate Changes
----------------------------------------

8.0.01 (07 November 2016) RC 1
1) Various internal enhancements
2) Include Windows Version
3) Updated documentation
4) Enhance access authorization in Central Console
5) Remove SSH option if using Windows in Central Console - Dbvnet must be used.
6) Various style and multiselect input enhancements in Central Console
7) Improve handling of Hostnames in Central Console
8) Various updates to installer script
9) Add task complete or task error messages to bottom of lightboxes in Central Console
10) Lower debug level for Dbvnet, Dbvserver, Dbvagent to value of 1
11) Update "Task log unavailable" message to "Retrieving task progress" to indicate process
12) Add new import DDC option in the Central Console Configurations Screen

8.0.01 (21 October 2016) Beta 3
1) Central Console updates:
- Database Actions are now grouped into logical groups
- Add new option to start the Dbvisit Standby Background (Daemon) process (Start/Stop/Status)
- Add new option to ship only one archive log to standby - similar to the -r option in CLI
- New confirmation option (Continue/Cancel) was added to remove/delete option for DDC, HOSTS and USERS
- Various Enhancements to DDC Upgrade process
- Added new progress indicators at various areas where actions are performed
- Add new option to update an existing license
- Improve error handling when a DDC is imported where primary or standby host is not yet defined in Central Console
- Create new configuration option is disabled if there is no hosts (agents) configured
- Resolve "in-progress" symbol spinning when viewing the Central Console via a RDP connection
- Add new "About" and "Documentation" links to bottom right of screen
- Activate new option to handle USER/HOST security - a user can be assigned to specific hosts. If a user does not have access to a host,
it will not have access to do anything with a DDC referencing that host
- Admin role - does not have any restrictions. It is important to note that only users with the admin user role can add new hosts
- Add support for creating an Oracle RAC to Single Instance standby DDC
- Add support for creating an Oracle RAC primary to Oracle RAC standby (node count must match primary) DDC
- IMPORTANT: Note that the cluster on the standby must already be configured (GI and Database software must be installed and diskgroups
configured). It is recommended in this configuration that the standby Oracle RAC matches the primary Oracle RAC as much as possible
(disk groups, file locations). Using shared storage for the Dbvisit Standby installation is required with a new Virtual IP (VIP) that
is allocated with a hostname alias. This is used to identify the node that will be running the Dbvisit Standby processes. Using ACFS
is recommended for the shared filesystem.
2) Add option to handle PDB states - especially when a PDB had a saved OPEN state - this resolved GS failure if saved OPEN state was used on the primary
3) Improved error message output in various areas
4) Improved handling of the HOSTNAME_CMD command option - used by default in version 8. Not used if upgrading a DDC from v7 where HOSTNAME_CMD was not configured.
5) Various updates and enhancements to prepare for Windows version release
6) Various Installer enhancements
7) Update to internal libraries

8.0.01 (3 October 2016) Beta 2
1) Add support for Transportable Media during CSD process (Central Console)
2) Add option to run Dbvisit Standby as background process - ./dbvctl -d <DDC> -D start|stop|status
3) Various internal bug fixes since beta 1
4) Rename central console "MANAGE DATABASES" to "DATABASE ACTIONS"
5) Fix certificates used causing certain browsers to not function correct
6) Browsers support includes Safari, Chrome, Firefox. Initial IE support experimental
7) Delete DDC files from Central Console now deletes DDC files from disk - backup will be made
8) Disable compression by default for Dbvisit Standby archive log shipping and management. This is to allow
the use of the new Dbvnet compression to be used. COMPRESS=N and UNCOMPRESS=N is now the default.
9) Installer Enhancements
10) The default HOSTNAME_CMD file will now be of format dbvhost_<ddc>.sh
11) Sending archive logs to standby now shows the thread# and sequence# for the log being transferred
12) Update Oracle Instant Client from 11.2.0.4 to 12.1.0.2
13) Update OpenSSL libraries to 1.0.2j
14) Update help output to display correct syntax for resending just one log: dbvctl -d <ddc> -r sequence# -t thread#
15) Enhanced format of error messages - both CLI and GUI
16) Add option -o read: dbvctl -d <ddc> -o open|read
17) Fix display of license expiry warning to round days remaining
18) Add header to Task History table listing in Central Console

8.0.01 (15 September 2016) Beta 1
New Features & Enhancements:
1) New directory structure
2) New enhanced network layer - Dbvnet
3) New Dbvisit agent and web server component
4) New web based interface (GUI) - Dbvserver
5) Enhanced Graceful Switchover (GS) (various enhancements, including performance improvement)
6) Enhanced Create Standby Database (CSD)
7) Repository outside the Oracle database
8) Dbvisit Standby core (command line interface) is now one executable "dbvctl"
9) New API interface
10) Various new functions. Most functions are exposed see "dbvctl -f -h"
11) Enhanced error handling
12) New Support Package option is introduced
13) Enhanced tracefile management
14) New and enhanced Oracle RAC management
15) New option to create Oracle RAC enabled Standby Database (conditions apply)
16) Support for creating Cascading Standby Databases (conditions apply)
17) Support for Oracle 12c Multitenent option - Single Tenant for Oracle Standard Edition
18) Various internal improvements and fixes

Notes:
------

  • The first Beta 1 release of Dbvisit Standby version 8 does have certain features disabled. These are expected
  • to be enabled in Beta 2 release.
  • For Beta 1 there will be a number of updates being released on a regular basis - Beta testers will be notified
  • The Beta program is considered private - please do not share or distribute the installation package or license keys provided
  • All bug fixes and changes up until Dbvisit Standby version 7.0.62 are also included in version 8 - if relevant

 

Have more questions? Submit a request

Comments