Table of Contents Previous Next


10 Appendix : 10.2 Upgrading to xDB Replication Server 6.1

Step 1: Any pending backlog of transactions on the publication tables must be replicated before starting the upgrade process.
Step 2: After all pending transactions have been replicated to their target databases, stop the xDB Replication Server 6.0.x publication server and subscription server (see sections 5.2.1 and 5.3.1).
Step 3: Install xDB Replication Server 6.1. See Chapter 3 for instructions on installing xDB Replication Server, but note the differences described in the following steps.
Step 4: Following the acceptance of the license agreement in Step 11 of Section 3.1, the Select Components screen appears, but with the entries grayed out. The old xDB Replication Server components are replaced by the new ones in the old xDB Replication Server’s directory location. Click the Next button.
Step 5: The Existing Installation screen confirms that an existing xDB Replication Server installation was found. Click the Next button to proceed with the upgrade.
Step 6: On the Ready to Install screen, click the Next button.
Step 7: The remaining screens that appear confirm completion of the installation process and allow you to exit from Stack Builder or StackBuilder Plus.
Step 8: After installation completes, the publication server of the new xDB Replication Server product should be running, connected to the controller database used by xDB Replication Server 6.0. The subscription server may or may not be running at this point, however, that is an expected outcome of this process.
Step 9: Complete the publication server and subscription server configuration file setup.
In the XDB_HOME/etc directory, a new set of configuration files for xDB Replication Server version 6.1 are created. These files are named xdb_pubserver.conf.new and xdb_subserver.conf.new. The new configuration files contain any new configuration options added for xDB Replication Server 6.1.
The final set of active configuration files must be named xdb_pubserver.conf and xdb_subserver.conf.
In the XDB_HOME/etc/sysconfig directory, make sure the xDB Startup Configuration file xdbReplicationServer-61.config contains the parameter settings you wish to use with xDB Replication Server 6.1. See Section 2.3.1.4 for information on the xDB Startup Configuration file.
Step 10: Restart the publication server and the subscription server (see sections 5.2.1 and 5.3.1).
Step 11: Check the publication server and subscription server log files to verify that no errors have occurred (see Section 10.3.2.4).
Step 12: Adjust the publication server and subscription server port numbers if necessary.
The xDB Replication Server 6.1 publication and subscription servers are installed to use the default port numbers 9051 and 9052, respectively. If the xDB Replication Server 6.0.x replication systems used port numbers other than 9051 and 9052, then perform the modifications to correct this inconsistency as described in Section 10.2.3.
Step 13: You are now ready to use xDB Replication Server 6.1 to create new replication systems and manage existing ones.
Note: Be sure the repository configuration file edb.repo for xDB Replication Server 6.1 is set up in the /etc/yum.repos.d directory. See Section 3.3 for information.
Step 1: Any pending backlog of transactions on the publication tables must be replicated before starting the upgrade process.
Step 2: After all pending transactions have been replicated to their target databases, stop the xDB Replication Server 6.0.x publication server and subscription server (see sections 5.2.1 and 5.3.1).
Step 3: Save a copy of the following configuration files:
Step 4: 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, will be accessible by the publication server and subscription server where xDB Replication Server 6.1 will be installed. See Section 5.1.3.1 for information.
Note: There are two options available: Option 1) Copy the Oracle JDBC driver to the jre/lib/ext subdirectory of your Java runtime environment. Option 2) Copy the Oracle JDBC driver to the lib/jdbc subdirectory of the xDB Replication Server installation directory.
It is suggested that you perform option 1 (copy the Oracle JDBC driver to the jre/lib/ext subdirectory of your Java runtime environment).
If on the other hand you perform option 2, you must copy the Oracle JDBC driver to the /usr/ppas-xdb-6.1/lib/jdbc directory after you have installed xDB Replication Server 6.1.
Step 5: It is best to ensure that the controller database is up and running. The other publication and subscription databases of existing SMR and MMR systems do not need to be up and running.
Step 6: As the root account invoke the yum update command to begin the upgrade from xDB Replication Server 6.0.x to xDB Replication Server 6.1 as shown by the following:
Be sure to include the asterisk character (*) following ppas-xdb in order to update all xDB Replication Server components.
xDB Replication Server 6.0.x remains in directory location /usr/ppas-xdb-6.0, but with the files removed from the subdirectories such as bin and lib.
The etc subdirectory contains the configuration files renamed as xdb_pubserver.conf.rpmsave and xdb_subserver.conf.rpmsave if they had been modified since their original installation.
The etc/sysconfig subdirectory contains the configuration file renamed as xdbReplicationServer-60.config.rpmsave if it had been modified since its original installation.
In the /etc directory, there may be either one or two xDB Replication Configuration files named edb-repl.conf and possibly edb-repl.conf.rpmsave. The file edb-repl.conf should contain the connection and authentication information for the controller database used by the xDB 6.0.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 the edb-repl.conf file contains the controller database connection and authentication parameters.
Step 7: Complete the publication server and subscription server configuration file setup.
In the /usr/ppas-xdb-6.1/etc directory, a new set of configuration files for xDB Replication Server version 6.1 are created. These files are named xdb_pubserver.conf and xdb_subserver.conf. The new configuration files contain any new configuration options added for xDB Replication Server 6.1.
The old configuration files used by xDB Replication Server version 6.0.x that you have modified remain in the /usr/ppas-xdb-6.0/etc directory renamed as xdb_pubserver.conf.rpmsave and xdb_subserver.conf.rpmsave.
Note: If these files do not exist, use the ones you saved in Step 3.
The final set of active configuration files must be contained in directory /usr/ppas-xdb-6.1/etc named xdb_pubserver.conf and xdb_subserver.conf.
In the /usr/ppas-xdb-6.1/etc/sysconfig directory, make sure the xDB Startup Configuration file xdbReplicationServer-61.config contains the parameter settings you wish to use with xDB Replication Server 6.1. See Section 2.3.1.4 for information on the xDB Startup Configuration file.
Step 8: Restart the publication server and the subscription server (see sections 5.2.1 and 5.3.1).
Step 9: Check the publication server and subscription server log files to verify that no errors have occurred (see Section 10.3.2.4).
Step 10: Adjust the publication server and subscription server port numbers if necessary.
The xDB Replication Server 6.1 publication and subscription servers are installed to use the default port numbers 9051 and 9052, respectively. If the xDB Replication Server 6.0.x replication systems used port numbers other than 9051 and 9052 for the publication and subscription servers, then perform the modifications to correct this inconsistency as described in Section 10.2.3.
Step 11: You are now ready to use xDB Replication Server 6.1 to create new replication systems and manage existing ones.
The newly installed publication server and subscription server of xDB Replication Server 6.1 are configured to use the default port numbers 9051 and 9052, respectively. These port numbers are set in the xDB Startup Configuration file as described in Section 2.3.1.4.
If your xDB Replication Server 6.0.x replication systems were running under port numbers other than 9051 and 9052, some of your settings in xDB Replication Server 6.1 must be adjusted to continue to use these existing replication systems.
Note: The following changes regarding port 9052 and the subscription server are only needed if you are running a single-master replication system. If you are using only a multi-master replication system, then only the changes involving port 9051 and the publication server are needed.
To continue to use the old port numbers (other than 9051 and 9052) that were in use for xDB Replication Server 6.0.x, stop the publication and subscription servers. Change the settings of the PUBPORT and SUBPORT parameters in the xDB Startup Configuration file from 9051 and 9052 to the old port numbers used by xDB Replication Server 6.0.x. Restart the publication and subscription servers. Register the publication server and the subscription server with the old xDB Replication Server 6.0.x port numbers along with the admin user and password as described in sections 5.2.1 and 5.3.1.
To use the default port numbers 9051 and 9052 with the xDB Replication Server 6.0.x replication systems, you must replace the old port numbers with the default port numbers 9051 and 9052. Register the publication server and the subscription server with port numbers 9051 and 9052 along with the admin user and password as described in sections 5.2.1 and 5.3.1. For single-master replication systems only, you then need to change the port numbers stored in the control schema from the old port numbers to 9051 and 9052. First, perform the procedure described in Section 7.6.1.2, and then perform the procedure described in Section 5.5.3.

10 Appendix : 10.2 Upgrading to xDB Replication Server 6.1

Table of Contents Previous Next