...
| Note |
|---|
The existing configurations are kept during upgrading of Dbvisit Replicate. |
| Info |
Upgrading Dbvisit Replicate involves the following steps:
...
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.
| No Format | ||
|---|---|---|
| ||
dbvrep> shutdown all |
...
| Note |
|---|
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` |
Optional Step 2a. 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.
| Note |
|---|
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.
...
| Note |
|---|
UPGRADE REPOSITORY command is required to be executed only once. It upgrades both MINE and APPLY. |
Example:
Follwing 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.
...