サポートと今すぐチャット
サポートとのチャット

SharePlex 12.0 - Upgrade Guide

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 targets involved in SharePlex replication.
  • See Before you Upgrade for any pre-installation items that apply to your SharePlex installation.

Pre-requisite for Snowflake database setup:

If any user has used Snowflake setup utility of a version prior to 11.4, they should first perform the following cleanup steps:

  1. Drop the role 'SHAREPLEX_ROLE' from the Snowflake account using the owner role. For example, if 'SHAREPLEX_ROLE' was created with a user having the 'ACCOUNTADMIN' role, execute the following query using the same privileges:

    drop role "SHAREPLEX_ROLE";

  2. Drop the table 'SHAREPLEX_OPEN_TRANS' from the target DB.SCHEMA. Refer to the query below:

    drop table SHAREPLEX_OPEN_TRANS;

    Re-run the Snowflake setup utility now, following the guidelines below. 'SHAREPLEX_ROLE' will be re-created correctly by the setup using the 'USERADMIN' role."

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.

    Please specify platform for license key (select a number):

    Please select the appropriate number from the following list of platforms to install the license key:

    1) Oracle
    2) File
    
    3) JMS
    4) Kafka
    5) SQL Server
    6) Postgres
    7) MySQL
    8) Snowflake
    9) MariaDB
    10) Event Hubs
    11) All Platforms
    q) Quit License Utility

    Note: To install a trial version of SharePlex, users need to select the All Platforms option.

    License key

    (If Y was selected) Enter the new license key that you received from Quest.

    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 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 Cygwin 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.
  • On Windows Server, Oracle 19c versions below 19.6 have an Oracle bug (29865658) that causes the SharePlex ora_setup, Reader, and Poster processes to get stuck. This bug is fixed in version 19.6 and later.To avoid this issue with SharePlex, either upgrade the Oracle 19c database to version 19.6 or higher. Users need to contact Oracle to obtain a patch for bug 29865658 or set the CLIENT_STATISTICS_LEVEL database parameter to 'OFF'.

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.

    Confirm installation Confirm the installation information.
    Finish

    If you were prompted to restart the system, you may do so at any time after exiting the installer.

  6. Remove the MKS Toolkit environment manually through Add/Remove programs.

  7. From the SP_Utils Licensing tab, select the required platform and add a license key for the selected platform.

  8. Run the appropriate Database Setup utility. For more information see SharePlex Reference Guide.

  9. Ensure that the Cygwin cygserver is running from the SharePlex installation directory.

  10. From the SP_Utils SharePlex Services tab, remove the installed SharePlex service, then install the service and start it.

  11. (Source only) To enable DDL replication again, set 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 theSharePlex 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
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択