Upgrading Dbvisit Replicate - Linux/Unix

Owned by KrupeshD (Deactivated)
Last updated: Oct 21, 2015 by Chris Lawless (Deactivated)

 

 

Upgrading of Dbvisit Replicate involves two simple steps:

  1. Replacing the existing software with new software
  2. Upgrading the Dbvisit Replicate repository (this is not always needed)
The existing configurations are kept during upgrading of Dbvisit Replicate.

 

Upgrading Dbvisit Replicate involves the following steps:

1. Stop the replication:

Before shutting down you may want to see if MINE/APPLY are going to go back in time.

dbvrep> list obsolete redo
dbvrep> list transactions 

This is to make sure that the MINE process does not need old redo/archive logs, and for APPLY that it is in the middle of a long transaction.  Consider doing the upgrade when MINE/APPLY don't have far to go back.

1a. (Optional)  You may wish to perform a backup of all the directories.  Also consider backup up the dbvrep schema on both the source and the target.  This is for fallback purposes.

 

dbvrep> shutdown all

2. Install the Dbvisit Replicate software. This is the same as a new install of the software. After installation, there is no need to reconfigure Dbvisit Replicate.

For RPM, please ensure the old RPM is removed before installing the new RPM. The old RPM can be uninstalled by running command:

rpm -e `rpm -qa | grep dbvisit_replicate`

For zip/tar files, unzip the file, untar the file and then extract the Replicate directory from the .zip build and replace it with the old directory.  Basically this is a reinstall directly on top of the old installation.

 

3. Restart the replication, by running the start scripts.

4. Upgrade the Dbvisit Replicate repository (if necessary). Dbvisit Repository will notify if the repository needs to be upgraded. If upgrading from Dbvisit Replicate from 2.6 to 2.7 you must upgrade the repository.  To upgrade the repository:

dbvrep> UPGRADE REPOSITORY

UPGRADE REPOSITORY command is required to be executed only once. It upgrades both MINE and APPLY.

Example:

The following example shows the repository error message and its solution using the replication "reptest1" which was configured in 2.6 and later upgraded to 2.7.

Error: 

oracle@dbvlin203[/home/oracle/reptest1]: ./reptest1-run-dbvlin203.sh 
Initializing......done
1 records in DDCDB updated to use new variable names.
DDC loaded from database (291 variables).
Dbvisit Replicate version 2.7
Copyright (C) Dbvisit Software Limited.  All rights reserved.
DDC file /home/oracle/reptest1/reptest1-MINE.ddc loaded.
Starting process MINE...ERR-10: Your Dbvisit Replicate dictionary version 2.6 is not supported by this executable, 2.7.00 is required. Please run "upgrade repository".
FATAL-9214: Not starting MINE, could not connect to database.

Solution :

oracle@dbvlin203[/home/oracle/reptest1]: ./start-console.sh --silent upgrade repository
MINE: Your Dbvisit Replicate dictionary version 2.6 is not supported by this executable, 2.7.00 is required. Please run "upgrade repository".
APPLY: Your Dbvisit Replicate dictionary version 2.6 is not supported by this executable, 2.7.00 is required. Please run "upgrade repository".
Upgrade to 2.7.00 done.
MINE: Upgrade done.
Upgrade to 2.7.00 done.
APPLY: Upgrade done.
OK-0: Completed successfully.
oracle@dbvlin203[/home/oracle/reptest1]:

To see the latest changes for Dbvisit Replicate please see:http://www.dbvisit.com/products/replicate_latest_changes