SharePlex 10.0 - Upgrade Guide for Oracle Source

Upgrade on Linux/Unix for Open Target Databases

These instructions are for upgrading SharePlex when configured for an Open Target database running on a Linux or Unix system.

Important!

• If you are upgrading some SharePlex installations in a configuration, but not others, view the SharePlex Release Notes for interoperability support between versions.
• Perform the upgrade on all Linux machines that host Open Target targets involved in SharePlex replication.
• See Before you upgrade for any pre-installation items that apply to your SharePlex installation.

To run the upgrade

1. Log in to the system as the user that will be named as the SharePlex Administrator during this installation. This user will own the installation files and binaries.

2. (Reinstallations) If sp_cop is running, shut it down.
3. Copy the installation file to a temporary directory where you have write permissions.

4. Grant executable permissions to the file.

   # chmod 555 installation_file

5. Run the .tpm file. If installing SharePlex in a cluster, run the installer from the primary node (the one to which the shared disk is mounted)

   # ./installation_file

6. You are prompted for the following:

   Prompt for:	Input
   Installation type	Select <New Installation>.
   Product directory location (path)	Enter the path to the existing SharePlex installation directory.
   Variable data directory location	Enter the name of the existing variable-data directory.
   SharePlex Admin group	Enter the DBA-privileged group to which the SharePlex Administrator user belongs, which owns the SharePlex binaries.
   TCP/IP port for SharePlex	Enter the port number of the SharePlex instance you are upgrading.
   License key (do you want to upgrade?)	Press Enter to accept the default of N (no) to keep the existing license, or enter Y to specify a new license key if required for this upgrade.
   License key	(If Y was selected) Enter the new license key that you received from Quest.
   Customer name	If you added the license key, enter the SiteMessage text string provided by Quest with the license key.

   The installer displays the location of the install log file and then quits.

7. Run the appropriate Database Setup utility for your database to upgrade the SharePlex database account. See SharePlex utilities.

8. Repeat all of the installation procedures for all Unix and Linux machines that host an Open Target database.

Upgrade on Windows

These instructions are for upgrading SharePlex on the Windows platform.

Important!

• If you are upgrading some SharePlex installations in a configuration, but not others, view the SharePlex Release Notes for interoperability support between versions.
• Perform the upgrade on all Windows machines that host databases involved in SharePlex replication.

• Do not uninstall SharePlex or the MKS Toolkit® environment before upgrading. Install the upgrade over the existing version.

• On Windows, install SharePlex on all nodes of each cluster, on the same port number, with identical path names. This is required to make the binaries and the required MKS Toolkit components available to all nodes, and to establish Registry entries.
• See Before you upgrade for any pre-installation items that apply to your SharePlex installation.

To run the upgrade

1. Log into Windows as the SharePlex Administrator.

2. (If using copy/append) Stop sp_sync_launcher on the target systems before applying the SharePlex upgrade.

   sp_ctrl> stop launcher

3. (Oracle as source only) In sp_ctrl, use the set param command to stop DDL replication (if active) by setting the SP_OCT_REPLICATE_ALL_DDL parameter to 0.

   sp_ctrl>set param SP_OCT_REPLICATE_ALL_DDL 0

   Important! Keep the setting at 0 until prompted otherwise.

4. Stop the SharePlex service:

   1. Run SpUtils from the shortcut on the Windows desktop.
   2. Select the SharePlex Services tab.
   3. Select the correct port, and then stop the SharePlex service.
   4. Close the utility.

5. Run the sp_setup installation program and follow the prompts:

   Prompt	Input
   Destination Folder	Install the upgrade into the existing SharePlex product directory.
   Port number	Select the port that this instance of SharePlex currently uses.
   Variable Data directory	Specify the existing SharePlex variable-data directory.
   Program Manager group	Specify the existing Programs menu location.
   MKS Platform Components	Appears if this version of SharePlex contains a new version of MKS Toolkit®. Accept the default Program Files location. If prompted to restart your system, you can postpone the restart until after you finish this installation.
   Confirm installation	Confirm the installation information.
   SharePlex license	Accept the existing license shown or enter a new one if applicable.
   Finish	If you were prompted to restart the system after you installed the MKS Toolkit files, you may do so at any time after exiting the installer.

6. Run the appropriate Database Setup utility:

   • Oracle: see Database Setup for Oracle
   • SQL Server: see Database Setup for SQL Server
7. From SpUtils, start the SharePlex service.
8. (Source only) To enable DDL replication again, set the the SP_OCT_REPLICATE_ALL_DDL parameter to 1.

Verify Partition Schemes

If you are upgrading from a SharePlex version earlier than 9.0, the method of creating and storing partition schemes and row partitions for horizontal partitioning has changed. This information no longer is stored in the database.

When you run database setup during an upgrade, it converts the data from the SHAREPLEX_PARTITION table to the new internal storage format. After the conversion, you can view the partitions with the view partitions command in sp_ctrl to ensure that the partitions converted properly.

Note: For more information about the view partitions command, see the SharePlex Reference Guide.

To view row partitions

1. Run sp_ctrl on the source system.

2. Issue the following command with either option, depending on whether you want to view all partitions or just those for a particular partition scheme.

   sp_ctrl> view partitions for {scheme_name | all}

The following is an example of converted partition schemes. Note that the conversion program populates the Name field with the name of the queue from the Route column.

Scheme        Name           Route                            Hash     Condition
-----------   -------------  ------------------------------   ------   ---------------
HASH4         hash           sys02:hash|#@o.ora112            4        ROWID
TEST_CT       highvalues     sys02:highvalues@o.ora112                 sales>=10000
TEST_CT       lowvalues      sys02:lowvalues@o.ora112                  sales<10000

Target upgrade for SAP ASE

This section applies to upgrades from SharePlex version 8.5 to the current release.

This procedure updates the way that SAP ASE is defined in the routing map in the configuration file and the way that connection settings are defined for Post.

• In the configuration file, the routing map now requires r.database_name, where database_name is the actual name of the target database, not a DSN.
• The connection information for Post to connect to SAP ASE is now configured through the connection command, rather than in the target configuration created by the target command.

To complete the upgrade from version 8.5 to the current version of SharePlex for an SAP ASE target, while keeping the current configuration active so that replication can continue, use the following procedure.

Note: This upgrade keeps the routing map as configured in version 8.5 and only changes the Post connection settings.

1. From the Unix command line of the operating system, run the following command, where database_name is the actual name of the target database (not a DSN).

   export SP_TARGET_DATABASE=database_name

2. Start sp_cop.

   /product_dir/bin/sp_cop

3. In sp_ctrl, issue the show post command. The state should be "stopped-due to error." If Post did not stop, stop it with the stop post command.

   stop post [for datasource-datadest]

4. Issue the following commands, using the new connection command, but this time substitute the DSN of the database for DSN. Do not specify the actual database name in this case.

   connection r.DSNset user=name_of_Post_database_user

   connection r.DSNset password=password

5. Start Post.

   start post [for datasource-datadest]