Table of Contents Previous Next


10 Appendix : 10.2 Upgrading to xDB Replication Server 6.0

Overview. Section 10.2.1 provides a general overview of the upgrading process.
Prerequisites. Section 10.2.2 provides the rules that apply to all variations of the upgrading process.
Upgrading with the Graphical User Interface Installer. Section 10.2.3 contains steps for the upgrading process if you are using the interactive installer available from Stack Builder or StackBuilder Plus.
Upgrading with the xDB Replication Server RPM Package. Section 10.2.4 contains steps for the upgrading process if you are using the xDB Replication Server RPM package.
Evaluating Control Schema Migration Failure. Section 10.2.5 provides information for recognizing and resolving control schema migration errors.
Updating the Publication Server and Subscription Server Ports. Section 10.2.6 provides the correction procedure if replication systems built with xDB Replication Server 5.1.x were using ports other than the default port numbers 9051 and 9052.
Upgrading from a Database Server Installation Directory. Section 10.2.7 provides alternatives for the upgrading process if xDB Replication Server 5.1 is installed in the same installation directory as a Postgres database server. This situation may have occurred when using the interactive installer from Stack Builder or StackBuilder Plus to install xDB Replication Server 5.1.
10.2.1 Overview
If the replication systems created under xDB Replication Server 5.1 used port numbers other than the default ports 9051 and 9052, there may be some additional steps needed to update the publication and subscription server port numbers.
Control schema migration refers to the process whereby the publication server of xDB Replication Server 6.0 creates database objects such as schemas, tables, triggers, etc. in the existing xDB Replication Server 5.1.x publication databases, then populates these newly created tables with the data it obtains from the xDB Control database. As part of this process, a subscription metadata object consisting of just a single table is created in every subscription database as well.
This newly created structure in the publication database storing this metadata is referred to as the control schema in xDB Replication Server 6.0. See Section 2.3.1.11 for information on the control schema. Every xDB Replication Server 6.0 publication database has a control schema. See Section 5.2.4 for a sample list of the control schema objects in a publication database. Every xDB Replication Server 6.0 subscription database has its own subscription metadata object. See Section 5.3.4 for a sample of this object in a subscription database.
The upgrade process designates one publication database as the controller database, which is the database to which the publication server and subscription server must establish a connection upon startup in order to use the xDB Replication Server 6.0 product. During the upgrade process, one of the existing publication databases is arbitrarily chosen to be the controller database. See Section 2.3.1.12 for information on the controller database.
When xDB Replication Server 6.0 is installed in the same directory containing xDB Replication Server 5.1.x, the etc subdirectory contains both the 5.1.x and 6.0 configuration files. The 6.0 configuration files are appended with the .new suffix.
If you had installed xDB Replication Server 5.1.x from an RPM package, the directory structure /usr/ppas-xdb-5.1 remains intact, but contains only the configuration files within the etc subdirectory modified with a .rpmsave suffix added. Keep these files in order to update your newly installed xDB Replication Server 6.0 configuration files with any non-default parameter settings you wish to retain from xDB Replication Server 5.1.x.
xDB Replication Server 5.1.x must not have been installed in the same directory location where a Postgres database server had been installed (for example, /opt/PostgresPlus/x.xAS). xDB Replication Server 6.0 is not permitted to be installed in the same installation directory as where a Postgres database server was installed. An error message box appears during the installation process identifying this issue. If this is the case, see Section 10.2.7 for directions on working around this issue.
It is highly recommended that all database servers running all publication and subscription databases be up and running. Unavailability of one or more servers will lead to a partial upgrade process that will be reattempted upon the next publication server startup. Note: The publication database designated as the master definition node must be up and running before starting the upgrade process. If that publication database will not be available, switch the role of the master definition node to another up and running publication database before performing the upgrade process. See Section 6.10 for information on switching the master definition node.
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 5.1.x publication server and subscription server (see sections 5.2.1 and 5.3.1).
Step 3: Create a backup of the xDB Control database so you can revert back to the 5.1.x version in case upgrade problems are encountered. The xDB Replication Configuration file contains the location and connection information for the xDB Control database.
Step 4: Verify that Java runtime version 1.7 or later is installed on your host. See Step 1 of Section 3.1 for information.
Step 5: 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.0 will be installed. This location is either the lib/jdbc subdirectory of the xDB Replication Server 5.1.x directory or the jre/lib/ext subdirectory of where Java runtime 1.7 or later is installed. See Section 5.1.3.1 for information.
Step 6: Make sure the database servers running the xDB Control database, the publication databases, and the subscription databases are up and running. These databases must be accessible from the host where xDB Replication Server 6.0 is to be installed.
Step 7: Install xDB Replication Server 6.0. The publication server installed with xDB Replication Server 6.0 initiates and performs the control schema migration. See Chapter 3 for instructions on installing xDB Replication Server, but note the differences described in the following steps.
Step 8: 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 9: The Existing Installation screen confirms that an existing xDB Replication Server installation was found. Click the Next button to proceed with the upgrade.
Step 10: On the Ready to Install screen, click the Next button.
Step 11: The remaining screens that appear confirm completion of the installation process and allow you to exit from Stack Builder or StackBuilder Plus.
Step 12: 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 13: Evaluate if the control schema migration has successfully completed.
If the publication server is not running, start it up (see Section 5.2.1). If the publication server does not start, see the publication server log file (see Section 10.3.2.4).
Use the xDB Replication Configuration file /etc/edb-repl.conf to evaluate the status of the control schema migration. See Section 2.3.1.3 for a description of the xDB Replication Configuration file. See Section 3.4 for its location on other operating system hosts such as Windows.
Prior to Startup or in Process. Prior to startup or completion of the control schema migration, these parameters are set to the connection and authentication information of the xDB Control database of xDB Replication Server 5.1.x.
Successful Completion. Upon successful completion of the control schema migration the host, port, type, database, user, and password parameters are set to the connection and authentication information of a publication database, now acting as the controller database. There must be no presence of parameters with a prefix of 51_ such as 51_type, 51_password, etc.
Incompletion Due to Failure. If the xDB Replication Configuration file contains parameters with a prefix of 51_ such as 51_type, 51_password, etc., then the control schema migration has encountered a failure, probably due to an offline publication or subscription database. See Section 10.2.5 for information.
The installer performs a change to upgrade the old xDB Replication Configuration file to the xDB Replication Server 6.0 format with the new administrator user credentials set by admin_user and admin_password. See Section 2.3.1.3 for the xDB Replication Server 6.0 format of the xDB Replication Configuration file.
The admin_user and admin_password parameters are set by default to the same database superuser name and password that were used to connect to the xDB Control database as well as to register the publication and subscription servers in xDB Replication Server 5.1.x.
Specify the values for parameters admin_user and the unencrypted form of the password given by admin_password when you register the publication server (see Section 5.2.1) and the subscription server (see Section 5.3.1) when you begin using the xDB Replication Console for the first time. See Section 8.2.3 for the similar process regarding the xDB Replication Server CLI.
The following is an example of the successfully updated xDB Replication Configuration file where the designated controller database is an Oracle publication database with Oracle database system ID xe originally defined in the 5.1.x replication system on host 192.168.2.23, with port 1521 using Oracle database user name pubuser and the encrypted password shown by the password parameter.
The admin_user parameter is set to enterprisedb, which was used to connect to the xDB Control database and register the publication and subscription servers in xDB Replication Server 5.1.x. with the password given by admin_password.
When the upgrade process has successfully completed, every publication database has a control schema. See Section 5.2.4 for a sample list of database objects comprising a publication database control schema.
Step 14: 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.0 are created. These files are named xdb_pubserver.conf.new and xdb_subserver.conf.new. The new configuration files contain new configuration options added for xDB Replication Server 6.0.
One approach is to first rename the original xDB Replication Server 5.1.x configuration files to names such as xdb_pubserver.conf.51 and xdb_subserver.conf.51, then to edit files xdb_pubserver.conf.new and xdb_subserver.conf.new with the non-default settings obtained from xdb_pubserver.conf.51 and xdb_subserver.conf.51. Finally, remove the .new suffix from files xdb_pubserver.conf.new and xdb_subserver.conf.new.
Alternatively, you can add the new xDB Replication Server 6.0 configuration options from files xdb_pubserver.conf.new and xdb_subserver.conf.new into the current xdb_pubserver.conf and xdb_subserver.conf files originally used with xDB Replication Server 5.1.x.
Note: If you previously encountered an upgrade problem due to the xDB Replication Server 5.1.x installation in a Postgres database server installation directory as described in Section 10.2.7, be sure to use the publication server and subscription server configuration files you saved in Step 1 of Section 10.2.7.1 or Step 1 of Section 10.2.7.2 when merging your xDB Replication Server 5.1.x configuration files with the xDB Replication Server 6.0 configuration files.
In the XDB_HOME/etc/sysconfig directory, make sure the xDB Startup Configuration file xdbReplicationServer-60.config contains the parameter settings you wish to use with xDB Replication Server 6.0. See Section 2.3.1.4 for information on the xDB Startup Configuration file.
Step 15: Restart the publication server and the subscription server (see sections 5.2.1 and 5.3.1).
Step 16: Check the publication server and subscription server log files to verify that no errors have occurred (see Section 10.3.2.4).
Step 17: Adjust the publication server and subscription server port numbers if necessary.
The xDB Replication Server 6.0 publication and subscription servers are installed to use the default port numbers 9051 and 9052, respectively. If the xDB Replication Server 5.1.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.6.
Step 18: After you have verified that xDB Replication Server 6.0 is operating properly with your replication systems you can delete the old xDB Control database.
Step 19: You are now ready to use xDB Replication Server 6.0 to create new replication systems and manage existing ones.
Note: Be sure the repository configuration file xdb60.repo for xDB Replication Server 6.0 is set up in the /etc/yum.repos.d directory. See steps 3 and 4 in 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 5.1.x publication server and subscription server (see sections 5.2.1 and 5.3.1).
Step 3: Create a backup of the xDB Control database so you can revert back to the 5.1.x version in case upgrade problems are encountered. The xDB Replication Configuration file contains the location and connection information for the xDB Control database.
Step 4: Verify that Java runtime version 1.7 or later is installed on your host. See Step 1 of Section 3.1 for information.
Step 5: 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.0 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) as this enables the control schema migration for Oracle publication and subscription databases immediately following installation of xDB Replication Server 6.0.
If on the other hand you perform option 2, you must copy the Oracle JDBC driver to the /usr/ppas-xdb-6.0/lib/jdbc directory after you have installed xDB Replication Server 6.0. In this case, the initial control schema migration attempt for the Oracle publication and subscription databases will have failed due to the absence of the Oracle JDBC driver immediately following the installation of xDB Replication Server 6.0 and the automatic startup of the publication server to perform the control schema migration. You must evaluate and perform the correction process for the migration schema failure as described in Step 8.
Step 6: Make sure the database servers running the xDB Control database, the publication databases, and the subscription databases are up and running. These databases must be accessible from the host where xDB Replication Server 6.0 is to be installed.
Step 7: As the root account invoke the yum update command to begin the upgrade from xDB Replication Server 5.1.x to xDB Replication Server 6.0 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 5.1.x remains in directory location /usr/ppas-xdb-5.1, but with the files removed from the subdirectories such as bin and lib. The etc subdirectory still contains the configuration files renamed as xdb_pubserver.conf.rpmsave and xdb_subserver.conf.rpmsave if they had been modified since their original installation.
In the /etc directory, there are two xDB Replication Configuration files named edb-repl.conf and edb-repl.conf.rpmnew. The file edb-repl.conf is used by the publication server to perform the control schema migration for existing replication systems. The file edb-repl.conf.rpmnew contains the new administrator user parameters admin_user and admin_password.
Note: If the upgrade process does not create file edb-repl.conf.rpmnew and file edb-repl.conf contains only two parameters admin_user and admin_password, go to Step 9.
Step 8: Evaluate if the control schema migration has successfully completed.
If the publication server is not running, start it up (see Section 5.2.1). If the publication server does not start, see the publication server log file (see Section 10.3.2.4).
Use the xDB Replication Configuration file /etc/edb-repl.conf to evaluate the status of the control schema migration. See Section 2.3.1.3 for a description of the xDB Replication Configuration file. See Section 3.4 for its location on other operating system hosts such as Windows.
Prior to Startup or in Process. Prior to startup or completion of the control schema migration, these parameters are set to the connection and authentication information of the xDB Control database of xDB Replication Server 5.1.x.
Successful Completion. Upon successful completion of the control schema migration the host, port, type, database, user, and password parameters are set to the connection and authentication information of a publication database, now acting as the controller database. There must be no presence of parameters with a prefix of 51_ such as 51_type, 51_password, etc.
Incompletion Due to Failure. If the xDB Replication Configuration file contains parameters with a prefix of 51_ such as 51_type, 51_password, etc., then the control schema migration has encountered a failure, probably due to an offline publication or subscription database. See Section 10.2.5 for information.
When the upgrade process has successfully completed, every publication database has a control schema. See Section 5.2.4 for a sample list of database objects comprising a publication database control schema.
Step 9: Complete the xDB Replication Configuration file setup.
In the /etc directory, you will find two xDB Replication Configuration files edb-repl.conf and edb-repl.conf.rpmnew.
Note: If the /etc directory does not contain file edb-repl.conf.rpmnew, and the /etc/edb-repl.conf file only contains two parameters admin_user and admin_password, then restore the edb-repl.conf file you saved in Step 3 back to the /etc directory, but copy the admin_user and admin_password parameters into your restored copy of edb-repl.conf. Make note of, or change the settings for admin_user and admin_password to your desired values. (Information regarding the admin_password setting is described later in this step.) Restart the publication server in order to initiate the control schema migration. Perform the evaluation as described in Step 8 to ensure the control schema migration completed and was successful. Proceed to Step 10.
Before using the xDB Replication Console or the xDB Replication Server CLI for the first time, copy the entries for the admin_user and admin_password parameters located in the newly installed xDB Replication Configuration file edb-repl.conf.rpmnew into edb-repl.conf.
The following example shows the content of the newly installed xDB Replication Configuration file edb-repl.conf.rpmnew containing the admin_user and admin_password parameters:
Note: The default password for admin_password upon installation is edb.
If you wish to set a different password, see Section 10.4.2 for information on generating an encrypted password.
After including these parameters, the final xDB Replication Configuration file edb-repl.conf to be used by xDB Replication Server 6.0 appears as follows:
Specify the values for parameters admin_user and the unencrypted form of the password given by admin_password when you register the publication server (see Section 5.2.1) and the subscription server (see Section 5.3.1) when you begin using the xDB Replication Console for the first time. See Section 8.2.3 for the similar process regarding the xDB Replication Server CLI.
You can delete file edb-repl.conf.rpmnew after you have made the modification to edb-repl.conf.
Step 10: Complete the publication server and subscription server configuration file setup.
In the /usr/ppas-xdb-6.0/etc directory, a new set of configuration files for xDB Replication Server version 6.0 are created. These files are named xdb_pubserver.conf and xdb_subserver.conf. The new configuration files contain new configuration options added for xDB Replication Server 6.0.
The old configuration files used by xDB Replication Server version 5.1.x remain in the /usr/ppas-xdb-5.1/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.
One approach is to edit files xdb_pubserver.conf and xdb_subserver.conf in the /usr/ppas-xdb-6.0/etc directory with the non-default settings obtained from the xdb_pubserver.conf.rpmsave and xdb_subserver.conf.rpmsave files in the /usr/ppas-xdb-5.1/etc directory.
Alternatively, you can add the new xDB Replication Server 6.0 configuration options from files xdb_pubserver.conf and xdb_subserver.conf in the /usr/ppas-xdb-6.0/etc directory into the xdb_pubserver.conf.rpmsave and xdb_subserver.conf.rpmsave files originally used with xDB Replication Server 5.1.x in the /usr/ppas-xdb-5.1/etc directory. In the /usr/ppas-xdb-6.0/etc directory, replace files xdb_pubserver.conf and xdb_subserver.conf with xdb_pubserver.conf.rpmsave and xdb_subserver.conf.rpmsave from the /usr/ppas-xdb-5.1/etc directory, but rename them to xdb_pubserver.conf and xdb_subserver.conf.
In either case, the final set of configuration files must be contained in directory /usr/ppas-xdb-6.0/etc named xdb_pubserver.conf and xdb_subserver.conf.
In the /usr/ppas-xdb-6.0/etc/sysconfig directory, make sure the xDB Startup Configuration file xdbReplicationServer-60.config contains the parameter settings you wish to use with xDB Replication Server 6.0. See Section 2.3.1.4 for information on the xDB Startup Configuration file.
Step 11: Restart the publication server and the subscription server (see sections 5.2.1 and 5.3.1).
Step 12: Check the publication server and subscription server log files to verify that no errors have occurred (see Section 10.3.2.4).
Step 13: Adjust the publication server and subscription server port numbers if necessary.
The xDB Replication Server 6.0 publication and subscription servers are installed to use the default port numbers 9051 and 9052, respectively. If the xDB Replication Server 5.1.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.6.
Step 14: After you have verified that xDB Replication Server 6.0 is operating properly with your replication systems you can delete the old xDB Control database.
Step 15: You are now ready to use xDB Replication Server 6.0 to create new replication systems and manage existing ones.
If the xDB Replication Configuration file contains parameters with a prefix of 51_ such as 51_type, 51_password, etc., then the control schema migration has not completed, probably due to an offline publication or subscription database.
The parameters 51_host, 51_port, 51_type, 51_database, 51_user, and 51_password are the connection and authentication information for the xDB Control database used by xDB Replication Server 5.1.x. The xDB Control database must remain accessible to the publication server installed by xDB Replication Server 6.0 in order to complete the control schema migration for all publication and subscription databases.
The parameters host, port, type, database, user, and password are the connection and authentication information for a publication database that has been selected as the controller database by the publication server during the upgrade process. The controller database must also remain accessible to the publication server installed by xDB Replication Server 6.0.
Also notice the presence of the upgrade_pending=n parameter where n is the number of publication and subscription databases to which the control schema is yet to be migrated.
See Section 10.3.2.4 for the publication server log file.
The newly installed publication server and subscription server of xDB Replication Server 6.0 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 5.1.x replication systems were running under port numbers other than 9051 and 9052, some of your settings in xDB Replication Server 6.0 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 5.1.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 5.1.x. Restart the publication and subscription servers. Register the publication server and the subscription server with the old xDB Replication Server 5.1.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 5.1.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.
xDB Replication Configuration File Modification. Basic process: 1) Uninstall xDB Replication Server 5.1.x. 2) Install xDB Replication Server 6.0 without initializing upgrade. 3) Modify the xDB Replication Configuration file. 4) Restart the publication server to initiate upgrade of existing replication systems.
Reinstallation of xDB Replication Server 5.1.x. Basic process: 1) Uninstall xDB Replication Server 5.1.x. 2) Install xDB Replication Server 5.1.x in a new directory location. 3) Install xDB Replication Server 6.0 allowing it to perform the upgrade of existing replication systems during the installation process.
See Section 10.2.7.1 for instructions on using the first method. See Section 10.2.7.2 for instructions on using the second method.
Step 1: Save a copy of the existing xDB Replication Configuration file used by xDB Replication Server 5.1.x.
Also make copies of the publication server and subscription server configuration files, xdb_pubserver.conf and xdb_subserver.conf so you can refer to any non-default settings for the configuration options you wish to apply after you upgrade to xDB Replication Server 6.0. Do the same for the xDB Startup Configuration file xdbReplicationServer-51.config.
See Section 3.4 for the location of these configuration files.
Step 2: Stop the publication server and the subscription server, then uninstall xDB Replication Server 5.1.x. See Section 3.6 for uninstallation instructions for xDB Replication Server 6.0, which is basically the same as for xDB Replication Server 5.1.x.
Step 3: Install xDB Replication Server 6.0 according to the directions in Section 3.1. Be sure to specify the same publication and subscription server port numbers (entered in Step 16 and Step 17) that were used by xDB Replication Server 5.1.x along with the same operating system account (entered in Step 18).
Step 4: Copy the entries for the admin_user and admin_password parameters from the newly installed xDB Replication Configuration file into the one you saved in Step 1. Replace the newly installed file with the one you saved from Step 1 that now includes the admin_user and admin_password parameters.
Note that parameters port, user, password, type, host, and database should reference the existing xDB Control database used by xDB Replication Server 5.1.x. Make sure this database is up and running.
Parameters admin_user and admin_password are the administrator user credentials you have chosen during the xDB Replication Server 6.0 installation process. Use these credentials when you register the publication server and the subscription server.
Step 5: Restart the publication server (see Section 5.2.1). The upgrade process for existing replication systems should begin.
Step 6: Continue with Step 12 onward in Section 10.2.3 to complete the upgrade process.
Step 1: Make a copy of the xDB Replication Configuration file. You must use the same xDB Control database connection information that is currently in this file when you reinstall xDB Replication Server 5.1.x later in this process in order to maintain existing replication systems.
Also make copies of the publication server and subscription server configuration files, xdb_pubserver.conf and xdb_subserver.conf so you can refer to any non-default settings for the configuration options you wish to apply after you upgrade to xDB Replication Server 6.0. Do the same for the xDB Startup Configuration file xdbReplicationServer-51.config.
See Section 3.4 for the location of these configuration files.
Step 2: Uninstall xDB Replication Server 5.1.x. See Section 3.6 for uninstallation instructions for xDB Replication Server 6.0, which is basically the same as for xDB Replication Server 5.1.x.
Step 3: Install xDB Replication Server 5.1.x, but note the following points.
For Oracle only: After reinstallation of xDB Replication Server 5.1.x has completed, and if any of your existing replication systems use an Oracle publication or subscription database, be sure the Oracle JDBC driver version ojdbc5 or later, is available to the newly installed publication and subscription servers. See Section 5.1.3.1 for information. Restart the publication and subscription servers if you copied the Oracle JDBC driver to a new directory location.
Step 4: The xDB Replication Console should display your existing replication systems in the replication tree.
Note: A publication server or subscription server error message box appears if your existing replication systems use publication or subscription server ports other than 9051 and 9052. After you install xDB Replication Server 6.0, you can adjust the publication and subscription server ports.
Note: For an Oracle or a SQL Server publication database and its subscriptions, the replication tree in the xDB Replication Console may not display the publication node. The complete replication tree appears properly after upgrading to xDB Replication Server 6.0.
Step 5: Upgrade from xDB Replication Server 5.1.x to xDB Replication Server 6.0 as described in Section 10.2.3.

10 Appendix : 10.2 Upgrading to xDB Replication Server 6.0

Table of Contents Previous Next