Standby Latest Changes

Dbvisit Standby Latest Changes Listing

6.0.16 (9 January 2012)

New features:

1. 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:
   - db_file_name_convert
   - log_file_name_convert
2. 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.
3. Provide silent install for dbvisit_install. This installs product with all default values accepted. Type "dbvisit_install -?" for details.
4. Non existent directories on the standby server are automatically created as much as possible by Dbvisit Standby during creation of the standby database.

Fixes:

1. Issue with adding own ORACLE_SID and ORACLE_HOME in web interface - fixed.
2. Dbvisit temp p2x-* directories not cleaned up for HP-UX and AIX - fixed.
3. 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.
4. Improved tracing of Dbvserver.
5. Obtain ORACLE_HOME and ORACLE_SID from registry for Windows 2008R2.

 

6.0.14 (10 November 2011)

New features:

1. Display the Windows domain name during setting up of SSH configuration.
2. Improve next steps output of dbvisit_install.
3. Improve error message for error code 447 on RAC.

Fixes:

1. Scheduler was not able to be set on remote server - fixed.
2. On Windows, after creation of standby database the dbvserverd process may utilise too much CPU - fixed.
3. Fix small issues during setup with web interface.
4. Capture Oracle message: ORA-28002: the password will expire within x days.
5. Fixed issues related to obtaining ORACLE_HOME for ASM instance on windows.
6. Suppress displaying DBPASSWD in trace files.

 

6.0.12 (27 October 2011)
New features:

1. Improved overall stability of Dbvserver, the web-server for Dbvisit Standby.
2. Removed reference to STANDBY_FILE_MANAGEMENT parameter.

Fixes:

1. 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)

New features:

1. Remove dependence on asmcmd to allow for separate Grid install.
2. Graceful Switchover on Windows with ASM now supported.
3. New END-USER LICENSE AGREEMENT.
4. New Dbvisit Logo.

Fixes:

1. In case FRA enabled Dbvisit only searched for an archive to transfer under date subdirectories but not directly under ARCHSOURCEn directories - fixed
2. Attached incorrect PDF User manual - fixed.
3. Remove PFILE setting. This is now obsolete.
4. Display a warning message for Graceful Switchover on Windows to configure Windows service with STARTMODE=MANUAL.
5. Fix minor bugs in functions to stop and start primary and standby databases.
6. Fixed issue with Graceful Switchover and RAC introduced with version 6.0.08 to deal with issue when threads are closed.
7. In some cases Graceful Switchover with RAC may want to transfer compressed archives and this fails - fixed.
8. Scheduler displayed wrong timestamp in email - fixed.
9. Dbvisit does not cope with commas in oracle parameter values when creating a standby database - fixed.

 

6.0.08 (9 August 2011)

New features:

1. Extend Dbvisit functionality to cope with closed threads in RAC environment.
2. 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.
3. 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+.
4. Separate checkpoint and log switch; Dbvisit now does not perform checkpoint during normal processing, only a log switch (if required).

Fixes:

1. Global FLASH_DIR_NUM default value changed from 40 to 7.
2. 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)

New features:

1. CSD (create standby database) now compares Dbvisit Standby installation between primary and standby and copies executables from primary if different.
2. Improved algorithm of searching for ASM archive logs in multiple locations, and under FRA-style date directories, to be shipped to the standby.
3. 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).

Fixes:

1. Dbvisit Standby could not cope with Oracle reserved words used for tablespace names in SQL statements (like INDEX) - fixed.
2. Dbvisit Standby restarted a database in restricted mode during shutdown that potentially lead to generating extra archive logs and issues during graceful switchover - fixed.
3. Global variable LOGDIR set to value of LOGDIR_DR on the standby server.
4. Queries of dictionary tables called by ora_list_dictionary function altered to format the display of checkpoint_change#.
5. Dbvserver scheduler was leaving behind zombie processes - fixed.

 

6.0.04 (9 June 2011)

New features:

1. Variable SEND_HEARTBEAT2_TIME24 made redundant. Multiple times to send a heartbeat message separated by colon can be specified by variable SEND_HEARTBEAT_TIME24
2. Provide user feedback that Dbvisit Standby is running the silent archive log gap report.
3. Release for all platforms.

Fixes:

1. Dbvisit Standby could not locate trace files while running AMM module in windows environment - fixed
2. When running -R, do not run silent inspect (RUN_INSPECT=Yes) as this meant Dbvisit Standby is contacting the standby database twice.
3. Compatibility with IE9 resolved.

 

6.0.02 (23 May 2011)

"Dbvisit" is now renamed to "Dbvisit Standby".

New features:

1. 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.
2. On Linux/Unix type dbvserverd to start Dbvserver.
3. On Windows start the Dbvserver Windows service to start Dbvserver.
4. Dbvserver includes a full scheduler to be able to schedule Dbvisit Standby. An external scheduler such as cron are no longer required.
5. Dbvisit Standby is now installed into a new subdirectory called "standby" under the main "dbvisit" directory.
6. 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.
7. 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.