While troubleshooting a difficult windows issue, I worked with several members of the Dbvisit support group. Their efforts and our interactions were uniformly excellent. I am very happy with their support.
John Kelly, Oracle DBA— Aidhm Inc.
Standby v6 Latest Changes
Dbvisit Standby Latest Changes Listing
6.0.62 - (22 June 2015)
- Improve handling of temp files during Graceful Switchover when tempfile autoextend is on with unlimited specified as maximum size
- Add option to compare at least file size in certain scenarios when COMPARE_CHECKSUM is set to N
- Add addtional status checks during Graceful Switchover if Oracle RAC is used (on the primary)
- Fix issue with reporting graphs where they are not always displaying in the GUI (Dbvserver) under the Reporting page
- Fix daily redo generation graph calculation
- Improve logging and error handling when starting a standby database during CSD
6.0.60 - (24 April 2014)
- Minor internal improvement on obtaining sequence# and SCN numbers from standby database when Oracle 8.1.7 is used
- Minor internal improvements regarding OMF redo log management on standby databases, to ensure redo logs are multiplexed on completion of Graceful Switchover
- Minor improvements when obtaining required SCN and sequence numbers remotely from standby
- 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)
- Improve internal Dbvisit Standby Repository (DDR) cleanup procedure on the DBV_TRANSFER_LOG table when multiple threads (RAC) are used
- Internal improvement when using multiple threads in Graceful Switchover (GS) and one instance is shutdown (thread not active or closed)
6.0.56 - (31 January 2014)
- Update Graceful Switchover (GS) internal checks when primary is ASM and the standby database is not making use of ASM
- Update internal checks where Oracle Managed Files (OMF) is used, taking into account OMF files in uppercase on Windows platforms
- Minor fix implemented in Web Based interface when running commands against a database not currently running
- Improve backup function, detecting if existing datafiles are in already in backup mode
- Improve adding of OMF datafiles to standby database when db_file_name_convert parameter is set
6.0.54 - (17 December 2013)
- Implement change to cater for Windows OracleASMService+ASM service
- 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
- Fix minor issue with Dbvserver (GUI) closed socket handling
- Minor improvment when last archived sequence cannot be obtained
6.0.52 - (13 September 2013)
- Allow primary database to be in restricted mode when Graceful Switchover is started
- Improvements to internal function ora_recovery_scn to check for missing datafiles
- Disable disk space check for Archivelog Management Module (AMM) when THRESHOLD_ARCHSOURCE=0 or THRESHOLD_ARCHDEST=0
- Implement fix to resolve "Can't locate object method" error when the dbvisit standby shared connection is used
- 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)
- Fixed file and directory browser in GUI (Dbvserver) (Setup => New)
- Extended logging and wait interval when Windows Oracle Database service cannot be obtained
- Update licence agreement text and Windows Installer Signed Certificate
- Improve add datafile function when datafiles are added to the SYSTEM tablespace
- 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
- Added an additional check to review if the standby is behind current time prior to running a recovery session if delay lag is specified.
- 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.
- 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
- Improve functionality to maintain Oracle Windows Service and detect a non-existing service
6.0.48 - (16 May 2013)
- Added WalkMe switch to Dbvserver (used only for demonstration)
- Fixed temp file paths for SQL statement result output in Dbvserver
- Improve the use of RESETLOGS_ID to identify archive log files
- Recreate Primary Key index on dbv_transfer_log table to include LOG_ID
- Update Dbvisit repository to make use of intermidiate version (release) numbers when doing multi-step upgrade of software. This release will require and update to the Dbvisit Repository when upgrading
- Added an additional step to check if sqlplus executable has zero size. This check is also performed for sqlplus in the ASM instance software home
- Internal impprovements on function cmn_exec_sql (added error file)
- Improve the handling of standby database recovery if a apply lag is set using APPLY_DELAY_LAG_MINUTES. Especially when Oracle does not request any new logs to apply during the recovery process
- Improve the process for adding new datafiles to the standby. Take into account the ORA-01274 error to obtain a primary name
- Added an additional check for SQL*Plus and RMAN to Dbvserver setup-new
- Add new global option "ADD_DATAFILE_FORCE_OMF" to force creating a new Oracle Managed File (OMF) file on the standby, when a new file was added to the primary and the primary file name could not be obtained
6.0.46 - (16 Apr 2013)
- Fix small issue when using rsh instead of ssh
- Do not set "until time" clause for recover command if lag is not set
- Update Archive log Management Module (AMM) to only select logs with current resetlogs_change# for deletion
- Do not use AS BACKUPSET as part of the RMAN backup command for Oracle versions less than 10g
- Allow "dbv_oraStartStop status" to run when another Dbvisit executable runs
- Update internal tracing to allow more detailed Oracle session tracing
- Update Create Standby Database (CSD) transportable media option to allow both filesystem or ASM storage to be used
- Fixed potential issue in certain scenarios with SCN date formatting. Update format from using RR to using 4 digit year format - YYYY
- Fixed wrong exit code returned when a file transfer failed
6.0.44 - (26 Feb 2013)
- Allow backing up primary datafiles AS COPY when creating a standby database. This can be done by setting the following parameter in the DDC file - "RMAN_DBF_BACKUP_TYPE=AS COPY"
- Introduce SSH_SKIP_OUTPUT_LINES to the DDC file, by setting this parameter to a number value, that number of lines will be ignored during ssh connections. Example if your ssh banner is 5 lines, you can specify SSH_SKIP_OUTPUT_LINES=5 and the first 5 lines of ssh output (which will include the banner) will be skipped
- During CSD, the standby controlfile and pfile was deleted before being transferred to standby when the direct copy option was selected and a CSD process was restarted - fixed
- Internal repository table DBV_TRANSFER_LOG index extended to include ORACLE_SID_DEST this is to improve handling of multiple standby databases - A Repository upgrade should be performed with this release. Internal repository version is now 6.2
- Dbvisit calculated checksums multiple times in certain scenarios. This is now fixed to only calculate it once
- Update internal procedure ora_nologging_info() to format the return value of FIRST_NONOLOGGED_SCN in a non exponential format (E+)
- Internal update to function cmn_get_last_sequence() and add resetlogs_change# clause to a query
- Improved STDERR output redirection when executing SQL
- Added extended logging to trace files for add_datafiles on primary
- Extended logging when the last archived seq cannont be obtained on primary
- Fix possible issue with port number for rsh and rcp in specific scenarios
- For RAC environments, improve the procedure doing the log extract from ASM, create oracle directories with names unique to ORACLE_SID
- Use DBV_ORACLE_SID in instance clause when archive current log
- Fixed issue with archives being created during the GS process in default archive destinations when FRA is disabled causing possible GS failure
- In RAC environments, the processing of multiple threads for GS improved
6.0.42 - (30 Nov 2012)
- During Activation of a standby database a new "nosynch" option can be passed to the activation process which will set the _COPY_TO_REMOTE and SYNCH_DBVISIT_INSTALL to "No" in the newly Activated database DDC File. This will ensure that even if a schedule is running, the newly Activated database's DDC file will not be coppied back to the original primary server. This is useful to ensure the original primary DDC file stays in tact if the Activition is done while the original primary is still available.
- Allow the configuration (setup) of Dbvisit Standby to continue if the software owner account does not exist on the local system. This option is to allow for the use of LDAP or other external user management and authentication.
- During Graceful Switchover, improve process that determine if database is ASM by analyzing control and data files.
- Improve Archive log management module (AMM) to sort archive list by epoch, thread and sequence, not just epoch.
- During the process of obtaining the next required SCN for recovery, only check for missing/corrupted datafiles if SCN cannot be obtained.
- Fix small issue with Dbvisit repository upgrade from version 53 to 54.
- Improve RMAN integration and use RMAN_DEVICE_SPECIFIER when deleting backup tag during Create Standby and Synchronize Standby when devices of type SBT or SBT_TAPE are used in the environment.
- Fix small issue when removing standby tempfiles if DROP_STANDBY_TEMPFILES is set to "Y", this only affects Oracle versions 11.2 and above.
- Fix issue with catalogging backup with RMAN when transportable media is used during the Create Standby Database (CSD).
- Improve Graceful Switchover (GS) by using RMAN in RAC environments when the primary database is recovered during the GS process.
- Preserve TZ environment variable to resolve time display in GUI. This change is specific to AIX.
- Minor improvents to the GUI scheduler logging.
6.0.40 - (9 Oct 2012)
- Ensure checksum is disabled in both primary and standby if COMPARE_CHECKSUM is set to N.
- Improved SQL function used for searching files in ASM storage.
- Improved error handling when directory cannot be created.
- Improved recovery commands during Graceful Switchover when using 11g and above databases (disabled parallel recovery).
- Improved code around the use of APPLY_READ_ONLY. If set to Y (yes) the database will return to recovery mode if it was opened read only. Default value is N (no).
6.0.38 - (22 Sep 2012)
- Removed blank spaces from HOSTNAME_CMD return value.
- Improved process for retrieving recovery SCN without running a recovery session on standby. This new method will ensure that the log gap report does not interfere with the apply process on the standby. To switch to old functionality set FORCE_RECOVERY_SESSION = Y (default N).
- Datafiles can now be added to the standby database without recreating of the standby control file. To switch to old functionality set FORCE_RECREATE_STANDBY_CTL = Y (default N).
- Search for files in ASM is now limited by folder <db_unique_name> under each disk group by default. To lift the limitation set LIMIT_ASM_SEARCH = N (default Y).
- Added new improved function for displaying database alert log in the GUI.
6.0.36 - (10 Sep 2012)
- The "Synchcronize Standby Database" option is now part of the GUI. This new option can be found under the Setup menu option.
- Improved "dbv_functions -s <ddc>" can now run on both primary and standby to obtain current SCN and next sequence.
- Extended functionality of obtaining timestamp for SCN for improved reporting capability, such as the log gap report "dbvisit -i <ddc>".
- Archive Log Management Module (AMM) improved to delete archive logs in batches.
- RESYNC_SEQ_OFFSET global parameter is redundant from this release and was removed.
- Additional Standby Synchronization reporting option added in GUI.
- Small issue fixed when Log transfer fails on primary if a compressed log was found instead of uncompressed one.
- Archive log Management Module (AMM) on the primary database should check disk threshold only if DAYS_TO_KEEP_ARCHSOURCE, NUM_ARCHSOURCE_TO_KEEP and BACKUP_COUNT are all set to 0.
- Archive log Management Module (AMM) on primary now deletes archive logs regardless of their resetlogs_id.
- Check Dbvisit Standby repository version prior to running the "Synchronize Standby Database".
- GUI: if standby database creation or synchronisation is currently running, then the output of that process will be displayed. The usual controls are only displayed if there is no active CSD/SYNC process present already.
- The system_readiness function was improved to pick up correct Dbvisit installation directory.
6.0.34 - (25 July 2012)
- New "Synchronize Standby Database" Option (Recover or Update Standby Database using Incremental RMAN Backups). This new feature is only available from the Command Line (CLI) using option 8 under "dbvisit_setup". The GUI version will be available in the next release.
- Online refresh of one Datafile on the standby database from the primary using one of the dbv_functions new advance features opions.
- Adding improved RMAN integration and catering for default configuration. Clients can modify the default rman configuration without affecting Dbvisit Standby functionality.
- Extend the create directory option in Create Standby Database (CSD) to include ASM directory structures.
- Improved support for Amazon Web Services (AWS).
- Add new "Advanced Functions" section when using dbv_functions.
- Pass full executable path as a parameter to the HOSTNAME_CMD script.
- Fixed memory leak in Dbvserver scheduler.
- Fixed Dbvserver use of HOSTNAME_CMD variable when using the "run interactive" option.
- Fixed issue with Archive Management Module (AMM) when using Oracle 9i.
- Fixed minor issue with restore of controlfiles when using Oracle 8.
- Adjust INSTANCE_CLAUSE_FOR_ARCHIVE_LOG_CURRENT to default value of "Y".
- Improved Create Standby Database (CSD) prerequisite checks to ensure none of the primary database files requires recovery.
- Fixed minor issue when using password file (database authentication is used).
- Improved handling of default archive log destinations.
- Improved internal handling of adding and removing of datafiles.
- Allow for ZIP_EXTENSION not to include a leading dot (both "gz" and ".gz" valid now).
- Prevented the root user from starting the dbvserver daemon.
- Corrected the primary or standby node detection on the Logging page.
- Optimised multi-level directory creation.
- Enhanced general logging.
6.0.32 - (22 June 2012)
- Improve algorithm for generating standby database filenames when db_file_name_convert or log_file_name_convert is used.
- Fix issue with rman connection when using password authentication.
- Move copy of password file forward in the Create Standby Database (CSD) process to deal with password authentication.
- Fix issue that can cause possible ssl errors with Dbvserver upgrade on non Linux and Windows platforms.
- Implement minor internal improvements.
6.0.30 - (29 May 2012)
- Skip unexpected SSH output up to the string specified by SSH_SKIP_OUTPUT.
- Created index on DBV_TRANSFER_LOG for performance.
- Added support for management of archive log files in ASM.
- Improved management of archive log files when using multiple standby databases.
- Improved feedback for entering Oracle password.
- Improved new database setup through Web interface.
- Singled out database selection on Setup > New page.
- New option to edit the SSH port number on Setup > New page.
- Cosmetic web interface updates (smaller font size, new header layout).
- New menu item "About" added to Dbvserver main menu.
- Improved Create Standby Database (CSD) prerequisite checks.
- Exclude READONLY tablespaces in hot backup mode during creation of standby database using direct copy.
- Improved Dbvserver stability (error handling and debugging information).
- Improved reverse templates for creating standby database (CSD) following a graceful switchover.
- Improved Dbvserver SQL*Plus shell security.
- Fix index creation during repository upgrade process.
- Fix erroneous redirect in Dbvserver reporting page.
6.0.28 - (18 April 2012)
- Create standby database (CSD) through the web browser has been enhanced to provide greater stability, flexibility and robustness.
- SQL*Plus command can be run through the web browser under Run commands.
- Recreation of the standby control file functions through the dbv_functions -Q command has been extended to be able to handle ASM, OMF, regular file system and different primary and standby database layouts.
- CSD has been enhanced to further handle different primary and standby database layouts. For example an ASM primary database with a non ASM standby database.
- Added more options to find the Oracle alert log in the web interface.
- Add "AS COMPRESSED BACKUPSET" to take compressed backup of datafiles during creation of standby database (CSD), for Oracle versions 10 and higher.
6.0.26 - (30 March 2012)
- Enable Dbvisit Standby to be installed with a Windows Domain account. Workaround using a local account is no longer needed.
- Add check owner function for resolving "Check owner" issues. Run: dbv_functions -a check_owner
- Allow for unattended install for setting Dbvisit Standby license.
- Gracefull Switchover will attempt to reset Oracle parameters db_file_name_convert and log_file_name_convert to default values.
- Use ssh compression during CSD instead of file compression.
- Dbvisit Standby can now be installed in non default location in Windows.
- Fix for Spanish language setting and RAC.
- Fix for CSD (create standby database) stop point through web browser.
- Fix for connectivity between primary and standby scheduler for Windows domain accounts.
6.0.24 (14 March 2012)
- Scheduler message error (dbv_functions: not found) on the standby server when Dbvisit Standby is installed in a different location to the primary server.
- Improved Scheduler messaging.
- Activation of standby database through web interface did not update the DDC file - fixed.
6.0.22 (5 March 2012)
- Fixed ORA- error handling code bug introduced in 6.0.20. If running Dbvisit Standby 6.0.20, please upgrade as version 6.0.20 may not detect Oracle errors correctly. This only affects version 6.0.20.
- System_readiness test did not work on Windows if Dbvisit was not installed in standard location - fixed.
- Check CSD (create standby database) did not skip checking of duplicates in ASM OMF tempfiles - fixed.
6.0.20 (24 February 2012)
- Scheduler stagger option. This allows the standby database schedule to be behind the primary schedule.
- Added setting SSH_RETURN_CODE to allow for non zero return code of ssh connection. Return code of 1 can be valid for older versions of ssh.
- Removed limitation for Create Standby Database (CSD) through web interface on Windows 2008 R2 64bit.
- Fix for CSD (create standby database) and Win2K8R2.
- Grid infrastructure permission fix.
- No call to ddr_repos_upgrade_60() when upgrading from early versions of dbvisit, fixed.
- Fix for CSD when REMOTE_LISTENER parameter contains the word "ora".
- Create Standby Database using Transportable Media check for local files instead of remote files - fixed.
6.0.18 (10 February 2012)
- 1) Improve add datafile functionality. Removed limitations of adding only one datafile at a time. Dbvisit Standby will add all new datafiles to the standby database that are added to the primary database. All datafiles are supported including ASM andf OMF.
i - For RAC USE_LONG_SERVER_NAME must be set to the same value on all primary nodes to function.
ii - The standby controlfile is recreated to add the datafiles and so the standby database will be restarted during this operation.
- Improve dbv_functions -Q option to recreate a standby controlfile. This function can be used on all types of standby databases and also when the standby database has a different structure to the primary database.
- Validate standby datafiles after recreating a controlfile.
- Obtain default ASM database name during dbvisit setup (UNIX).
- Validate the DDC file on standby as part of pre-checks for CSD.
- Extend template validation to
a) pick up datafiles added since the template has been created
b) detect duplicate standby database filenames
- Added HTTPS support for Linux and Windows.
- Add ORACLE_SID_ASM and ORACLE_SID_ASM_DEST to quick setup.
- ORACLE_ASM_SID and ORACLE_ASM_SID_DEST recorded in a DDC file twice under Primary and Advanced catagories - fixed
- The name of a DDC file supplied by user not passed to function calls when using option 1) New Dbvisit Database setup (combines options 2,3,4) of dbvisit_setup - fixed
- Remove ASM databases from a list of databases available on primary server for dbvisit setup.
- Fixed GUI scheduler issues.
- Screen and display clarifications in the Dbvisit Standby - Setup GUI process.
- Reverse values of ORACLE_HOME_ASM and ORACLE_HOME_ASM_DEST after switchover.
- Ensure redo logs that have to be copied from/to ASM during switchover have write group permissions to be managed by both Dbvisit and grid owner.
- Various small GUI fixes.
- Create Standby Database through web interface is not supported for Windows 2008 R2 64bit. Create Standby Database can be created through the Command Line Wizard. This limitation will be resolved in near future.
6.0.16 (9 January 2012)
- New Create Standby Database (CSD) functionality which improves the overall ability to create different standby databases configurations.
CSD now makes use of the following parameters:
- Improved graceful switchover functionality. Existing controlfile is re-used for primary database and is no longer rebuild. Graceful switchover allows for more differences between primary and standby database.
- Provide silent install for dbvisit_setup. This installs product with all default values accepted. Type "dbvisit_setup -?" for details.
- Non existent directories on the standby server are automatically created as much as possible by Dbvisit Standby during creation of the standby database.
- Issue with adding own ORACLE_SID and ORACLE_HOME in web interface - fixed.
- Dbvisit temp p2x-* directories not cleaned up for HP-UX and AIX - fixed.
- Improve locking mechanism in rare cases when archive log file just arrives at the standby server and is 0 size and is picked up by Dbvisit Standby on the standby server.
- Improved tracing of Dbvserver.
- Obtain ORACLE_HOME and ORACLE_SID from registry for Windows 2008R2.
6.0.14 (10 November 2011)
- Display the Windows domain name during setting up of SSH configuration.
- Improve next steps output of dbvisit_install.
- Improve error message for error code 447 on RAC.
- Scheduler was not able to be set on remote server - fixed.
- On Windows, after creation of standby database the dbvserverd process may utilise too much CPU - fixed.
- Fix small issues during setup with web interface.
- Capture Oracle message: ORA-28002: the password will expire within x days.
- Fixed issues related to obtaining ORACLE_HOME for ASM instance on windows.
- Suppress displaying DBPASSWD in trace files.
6.0.12 (27 October 2011)
- Improved overall stability of Dbvserver, the web-server for Dbvisit Standby.
- Removed reference to STANDBY_FILE_MANAGEMENT parameter.
- Number of fixes in usability of Dbvserver, the web-based interface to Dbvisit Standby, including the setup and creation of standby databases and the scheduler.
6.0.10 (2 September 2011)
- Remove dependence on asmcmd to allow for separate Grid install.
- Graceful Switchover on Windows with ASM now supported.
- New END-USER LICENSE AGREEMENT.
- New Dbvisit Logo.
- In case FRA enabled Dbvisit only searched for an archive to transfer under date subdirectories but not directly under ARCHSOURCEn directories - fixed
- Attached incorrect PDF User manual - fixed.
- Remove PFILE setting. This is now obsolete.
- Display a warning message for Graceful Switchover on Windows to configure Windows service with STARTMODE=MANUAL.
- Fix minor bugs in functions to stop and start primary and standby databases.
- Fixed issue with Graceful Switchover and RAC introduced with version 6.0.08 to deal with issue when threads are closed.
- In some cases Graceful Switchover with RAC may want to transfer compressed archives and this fails - fixed.
- Scheduler displayed wrong timestamp in email - fixed.
- Dbvisit does not cope with commas in oracle parameter values when creating a standby database - fixed.
6.0.08 (9 August 2011)
- Extend Dbvisit functionality to cope with closed threads in RAC environment.
- AMM module is now called regardless of the fact some archive logs reside in ASM on the source, to process multiple archive destinations. ASM archive locations are skipped.
- If log archive destination is not set up for the database, use default values of ORACLE_HOME/dbs/arch or ORACLE_HOME\rdbms, for versions 10.2+.
- Separate checkpoint and log switch; Dbvisit now does not perform checkpoint during normal processing, only a log switch (if required).
- Global FLASH_DIR_NUM default value changed from 40 to 7.
- When parsing a value for log_archive_dest*, check if extra attributes like MANDATORY etc are separated not only by a space but by a comma.
6.0.06 (15 July 2011)
- CSD (create standby database) now compares Dbvisit Standby installation between primary and standby and copies executables from primary if different.
- Improved algorithm of searching for ASM archive logs in multiple locations, and under FRA-style date directories, to be shipped to the standby.
- Allow one-way communication of Dbvisit Standby from primary to standby for ultra secure configurations which only allow one-way traffic. Set BLIND=Y to enforce this, but there is reduced Dbvisit Standby functionality (no checkums, no log gap reporting, no Resync and no creation of standby database options available).
- Dbvisit Standby could not cope with Oracle reserved words used for tablespace names in SQL statements (like INDEX) - fixed.
- Dbvisit Standby restarted a database in restricted mode during shutdown that potentially lead to generating extra archive logs and issues during graceful switchover - fixed.
- Global variable LOGDIR set to value of LOGDIR_DR on the standby server.
- Queries of dictionary tables called by ora_list_dictionary function altered to format the display of checkpoint_change#.
- Dbvserver scheduler was leaving behind zombie processes - fixed.
6.0.04 (9 June 2011)
- Variable SEND_HEARTBEAT2_TIME24 made redundant. Multiple times to send a heartbeat message separated by colon can be specified by variable SEND_HEARTBEAT_TIME24
- Provide user feedback that Dbvisit Standby is running the silent archive log gap report.
- Release for all platforms.
- Dbvisit Standby could not locate trace files while running AMM module in windows environment - fixed
- When running -R, do not run silent inspect (RUN_INSPECT=Yes) as this meant Dbvisit Standby is contacting the standby database twice.
- Compatibility with IE9 resolved.
6.0.02 (23 May 2011)
"Dbvisit" is now renamed to "Dbvisit Standby".
- Web-based interface using build in web-server named Dbvserver. Dbvisit Standby can be now be run through: - traditional command line interface (CLI) or - graphical user interface (GUI) through browser. Dbvserver needs to be started to enable the Dbvisit Standby interface through the browser.
- On Linux/Unix type dbvserverd to start Dbvserver.
- On Windows start the Dbvserver Windows service to start Dbvserver.
- Dbvserver includes a full scheduler to be able to schedule Dbvisit Standby. An external scheduler such as cron are no longer required.
- Dbvisit Standby is now installed into a new subdirectory called "standby" under the main "dbvisit" directory.
- Full web-based access to the Dbvisit Standby logs on the primary and standby server. Full access to the Oracle alert log throug the web browser.
- Graphical reports showing key information about the standby database process such as lag, compression ratio, size of transfer, time taken for transfers, total redo per day, and total transfers per day.
Businesses in over 110 countries worldwide with Oracle® Database Standard Edition trust Dbvisit to protect and share their data.
Join a growing community of Oracle experts using Dbvisit software as the key to unlocking untapped revenue from customers and prospects.
Dbvisit provides Oracle® Database Standard Edition users with affordable disaster recovery and data replication solutions.