Upgrading from a Replication Server 6.2 installation on Linux v7

Suggest edits

If you're using Replication Server 6.2.x that was installed using the Replication Server RPM package, you can upgrade to Replication Server 7 from an RPM package.

Note

Be sure the repository configuration file edb.repo for Replication Server 7 is set up in the /etc/yum.repos.d directory.

Before starting the upgrade process, replicate any pending backlog of transactions on the publication tables.
After all pending transactions are replicated to their target databases, stop the Replication Server 6.2.x publication server and subscription server. See Registering a publication server and Registering a subscription server).
Save a copy of the following configuration files:
- /etc/edb-repl.conf
- /usr/edb/xdb/etc/xdb_pubserver.conf
- /usr/edb/xdb/etc/xdb_subserver.conf
- /usr/edb/xdb/etc/sysconfig/xdbReplicationServer-70.config
Copies of these files are typically saved by the upgrade process if the files were modified since their original installation. However, it's safest to save copies in case the upgrade process doesn't. Use the saved files as your Replication Server 6.2.x configuration files for the updates described in Step 7.
If any Oracle publication or subscription databases are used in existing single-master replication systems, make sure a copy of the Oracle JDBC driver, version ojdbc5 or later, is accessible by the publication server and subscription server where Replication Server 7 will be installed. See Enabling access to Oracle for information.
Note
Two options are available: 1) Copy the Oracle JDBC driver to the jre/lib/ext subdirectory of your Java runtime environment. 2) Copy the Oracle JDBC driver to the lib/jdbc subdirectory of the Replication Server installation directory.
We recommend that you copy the Oracle JDBC driver to the jre/lib/ext subdirectory of your Java runtime environment. If you instead copy it to lib/jdbc, you must copy the Oracle JDBC driver to the /usr/edb/xdb/lib/jdbc directory after you install Replication Server 7.
Make sure that the controller database is up and running. The other publication and subscription databases of existing SMR and MMR systems don't need to be up and running.

As the root account, invoke the yum update command to begin the upgrade from Replication Server 6.2.x to Replication Server 7 as shown by the following:

yum update ppas-xdb*

Be sure to include the asterisk character (*) to update all Replication Server components.

The following is an example:

[root@localhost ~]# yum update ppas-xdb*
Loaded plugins: fastestmirror, langpacks
Determining fastest mirrors
Resolving Dependencies
--> Running transaction check
---> Package edb-xdb.x86_64 0:7.0.0-1.rhel7 will be obsoleting
--> Processing Dependency: edb-jdbc-driver >= 42.2.24.1 for package: edb-xdb-7.0.0-1.rhel7.x86_64
--> Processing Dependency: edb-xdb-subscriber for package: edb-xdb-7.0.0-1.rhel7.x86_64
--> Processing Dependency: edb-xdb-publisher for package: edb-xdb-7.0.0-1.rhel7.x86_64
--> Processing Dependency: edb-xdb-libs for package: edb-xdb-7.0.0-1.rhel7.x86_64
--> Processing Dependency: edb-xdb-console for package: edb-xdb-7.0.0-1.rhel7.x86_64
---> Package ppas-xdb.x86_64 0:6.2.15b-1.rhel7 will be obsoleted
---> Package ppas-xdb-console.x86_64 0:6.2.15b-1.rhel7 will be obsoleted
---> Package ppas-xdb-libs.x86_64 0:6.2.15b-1.rhel7 will be obsoleted
---> Package ppas-xdb-publisher.x86_64 0:6.2.15b-1.rhel7 will be obsoleted
---> Package ppas-xdb-subscriber.x86_64 0:6.2.15b-1.rhel7 will be obsoleted
--> Running transaction check
---> Package edb-jdbc.x86_64 0:42.2.19.1-1.rhel7 will be updated
---> Package edb-jdbc.x86_64 0:42.2.24.1-1.rhel7 will be an update
---> Package edb-xdb-console.x86_64 0:7.0.0-1.rhel7 will be installed
---> Package edb-xdb-libs.x86_64 0:7.0.0-1.rhel7 will be installed
---> Package edb-xdb-publisher.x86_64 0:7.0.0-1.rhel7 will be installed
---> Package edb-xdb-subscriber.x86_64 0:7.0.0-1.rhel7 will be installed
---> Finished Dependency Resolution

Dependencies Resolved

============================================================================================================================================
Package Arch Version Repository Size
============================================================================================================================================
Installing:
edb-xdb x86_64 7.0.0-1.rhel7 edb 9.3 k
replacing ppas-xdb.x86_64 6.2.15b-1.rhel7
replacing ppas-xdb-console.x86_64 6.2.15b-1.rhel7
replacing ppas-xdb-libs.x86_64 6.2.15b-1.rhel7
replacing ppas-xdb-publisher.x86_64 6.2.15b-1.rhel7
replacing ppas-xdb-subscriber.x86_64 6.2.15b-1.rhel7
Installing for dependencies:
edb-xdb-console x86_64 7.0.0-1.rhel7 edb 1.6 M
edb-xdb-libs x86_64 7.0.0-1.rhel7 edb 13 M
edb-xdb-publisher x86_64 7.0.0-1.rhel7 edb 41 k
edb-xdb-subscriber x86_64 7.0.0-1.rhel7 edb 11 k
Updating for dependencies:
edb-jdbc x86_64 42.2.24.1-1.rhel7 edb 1.0 M

Transaction Summary
============================================================================================================================================
Install 1 Package (+4 Dependent packages)
Upgrade ( 1 Dependent package)

Total download size: 15 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for edb
(1/6): edb-xdb-7.0.0-1.rhel7.x86_64.rpm | 9.3 kB 00:00:01
(2/6): edb-xdb-console-7.0.0-1.rhel7.x86_64.rpm | 1.6 MB 00:00:09
(3/6): edb-jdbc-42.2.24.1-1.rhel7.x86_64.rpm | 1.0 MB 00:00:11
(4/6): edb-xdb-publisher-7.0.0-1.rhel7.x86_64.rpm | 41 kB 00:00:01
(5/6): edb-xdb-subscriber-7.0.0-1.rhel7.x86_64.rpm | 11 kB 00:00:00
(6/6): edb-xdb-libs-7.0.0-1.rhel7.x86_64.rpm | 13 MB 00:02:14
--------------------------------------------------------------------------------------------------------------------------------------------
Total 109 kB/s | 15 MB 00:02:25
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : edb-xdb-libs-7.0.0-1.rhel7.x86_64 1/12
Installing : edb-xdb-publisher-7.0.0-1.rhel7.x86_64 2/12
Installing : edb-xdb-console-7.0.0-1.rhel7.x86_64 3/12
Installing : edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 4/12
Updating : edb-jdbc-42.2.24.1-1.rhel7.x86_64 5/12
Installing : edb-xdb-7.0.0-1.rhel7.x86_64 6/12
Erasing : ppas-xdb-6.2.15b-1.rhel7.x86_64 7/12
Erasing : ppas-xdb-subscriber-6.2.15b-1.rhel7.x86_64 8/12
warning: /usr/ppas-xdb-6.2/etc/xdb_subserver.conf saved as /usr/ppas-xdb-6.2/etc/xdb_subserver.conf.rpmsave
Erasing : ppas-xdb-console-6.2.15b-1.rhel7.x86_64 9/12
Cleanup : edb-jdbc-42.2.19.1-1.rhel7.x86_64 10/12
Erasing : ppas-xdb-publisher-6.2.15b-1.rhel7.x86_64 11/12
warning: /usr/ppas-xdb-6.2/etc/xdb_pubserver.conf saved as /usr/ppas-xdb-6.2/etc/xdb_pubserver.conf.rpmsave
Erasing : ppas-xdb-libs-6.2.15b-1.rhel7.x86_64 12/12
Verifying : edb-jdbc-42.2.24.1-1.rhel7.x86_64 1/12
Verifying : edb-xdb-libs-7.0.0-1.rhel7.x86_64 2/12
Verifying : edb-xdb-publisher-7.0.0-1.rhel7.x86_64 3/12
Verifying : edb-xdb-7.0.0-1.rhel7.x86_64 4/12
Verifying : edb-xdb-console-7.0.0-1.rhel7.x86_64 5/12
Verifying : edb-xdb-subscriber-7.0.0-1.rhel7.x86_64 6/12
Verifying : ppas-xdb-subscriber-6.2.15b-1.rhel7.x86_64 7/12
Verifying : ppas-xdb-console-6.2.15b-1.rhel7.x86_64 8/12
Verifying : edb-jdbc-42.2.19.1-1.rhel7.x86_64 9/12
Verifying : ppas-xdb-libs-6.2.15b-1.rhel7.x86_64 10/12
Verifying : ppas-xdb-6.2.15b-1.rhel7.x86_64 11/12
Verifying : ppas-xdb-publisher-6.2.15b-1.rhel7.x86_64 12/12

Installed:
edb-xdb.x86_64 0:7.0.0-1.rhel7

Dependency Installed:
edb-xdb-console.x86_64 0:7.0.0-1.rhel7 edb-xdb-libs.x86_64 0:7.0.0-1.rhel7 edb-xdb-publisher.x86_64 0:7.0.0-1.rhel7
edb-xdb-subscriber.x86_64 0:7.0.0-1.rhel7

Dependency Updated:
edb-jdbc.x86_64 0:42.2.24.1-1.rhel7

Replaced:
ppas-xdb.x86_64 0:6.2.15b-1.rhel7 ppas-xdb-console.x86_64 0:6.2.15b-1.rhel7 ppas-xdb-libs.x86_64 0:6.2.15b-1.rhel7
ppas-xdb-publisher.x86_64 0:6.2.15b-1.rhel7 ppas-xdb-subscriber.x86_64 0:6.2.15b-1.rhel7

Complete!

At this point, the publication server and the subscription server for Replication Server 7 aren't running. The directories now contain the following:

Replication Server 7 is installed in directory location /usr/edb/xdb.
Replication Server 6.2.x remains in directory location /usr/ppas-xdb-6.2 but with the files removed from the subdirectories such as bin and lib.
In the etc subdirectory, there might be the configuration files renamed as xdb_pubserver.conf.rpmsave and xdb_subserver.conf.rpmsave.
In the etc/sysconfig subdirectory, there might be the configuration file renamed as xdbReplicationServer-62.config.rpmsave.
In the /etc directory, there might be either one or two Replication Server configuration files named edb-repl.conf and possibly edb-repl.conf.rpmsave. The file edb-repl.conf contains the connection and authentication information for the controller database used by the Replication Server 6.2.x publication server. The file edb-repl.conf.rpmsave contains only the new administrator user parameters admin_user and admin_password. Before starting the publication server and subscription server, be sure the controller database is up and running and that the edb-repl.conf file contains the controller database connection and authentication parameters.

Complete the publication server and subscription server configuration file setup.
In the /usr/edb/xdb/etc directory, a new set of configuration files for Replication Server version 7 was created. These files are named xdb_pubserver.conf and xdb_subserver.conf. The new configuration files contain any new configuration options added for Replication Server 7. The old configuration files used by Replication Server version 6.2.x can be found in the /usr/ppas-xdb-6.2/etc directory renamed as xdb_pubserver.conf.rpmsave and xdb_subserver.conf.rpmsave.
Note
If these files don't exist, use the ones you saved in Step 3.
Merge the old and new configuration files so that the resulting, active configuration files contain any new Replication Server 7 configuration options as well as any nondefault settings you used with Replication Server 6.2.x and want to continue to use with Replication Server 7.
The final set of active configuration files must be contained in the directory /usr/edb/xdb/etc and named xdb_pubserver.conf and xdb_subserver.conf. In the /usr/edb/xdb/etc/sysconfig directory, make sure the Replication Server startup configuration file xdbReplicationServer-70.config contains the parameter settings you want to use with Replication Server 7. See Replication Server configuration file for more information.
Restart the publication server and the subscription server (see Registering a publication server and Registering a subscription server).
Check the publication server and subscription server log files to verify that no errors occurred (see Replication Server configuration file).
Adjust the publication server and subscription server port numbers if necessary.
The Replication Server 7 publication and subscription servers are installed to use the default port numbers 9051 and 9052, respectively. If the Replication Server 6.2.x replication systems used port numbers other than 9051 and 9052 for the publication and subscription servers, then make the changes to correct this inconsistency as described in Updating the publication and subscription server ports.
If you don't need to adjust the port numbers, register the publication server and subscription server with the Replication Server console as described in Registering a publication server and Registering a subscription server). The existing replication systems appear in the replication tree of the Replication Server console.

After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it. See Installing a JDBC driver for more information.

You're now ready to use Replication Server 7 to create new replication systems and manage existing ones.

← Prev

Upgrading with the graphical installer

Uninstalling

Upgrading from a Replication Server 6.2 installation on Linux v7

Note

Note

Note

← Prev

Next →