These instructions are for upgrading SharePlex when configured for an Oracle or PostgreSQL database running on a Linux or Unix system.
Important!:
|
To upgrade SharePlex in the current product directory:
(If using copy/append) In sp_ctrl on the target systems, stop sp_sync_launcher before applying the SharePlex upgrade.
sp_ctrl> stop launcher
(applicable only for Oracle source) In sp_ctrl on the source system, use the set param command to stop DDL replication by setting the SP_OCT_REPLICATE_ALL_DDL parameter to 0.
sp_ctrl> set param SP_OCT_REPLICATE_ALL_DDL 0
Shut down the SharePlex instance that you are upgrading.
sp_ctrl> shutdown
Verify that all SharePlex processes in that SharePlex instance are stopped, and stop any that are still running.
# ps -ef | grep sp_
sp_ctl> stop process
Run the SharePlex installation program.
Prompt | Input |
---|---|
Installation type |
Select the current product directory of the SharePlex installation you are upgrading. |
SharePlex Admin group |
Select the DBA-privileged group to which the SharePlex Administrator user belongs. |
Proceed with upgrade? | Press Enter to confirm the SharePlex environment and proceed with the upgrade. |
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) Event Hubs 10) 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. |
Note: The installer will upgrade the default variable-data directory that is listed in the default.yaml file, which is located in the data sub-directory of the product directory.
PostgreSQL: pg_setup
Start SharePlex using the following syntax with options as appropriate.
$ cd /productdir/bin
$ ./sp_cop [-uidentifier] &
where:
(applicable only for Oracle source) In sp_ctrl on the source system, set the the SP_OCT_REPLICATE_ALL_DDL parameter to 1.
sp_ctrl> set param SP_OCT_REPLICATE_ALL_DDL 1
To upgrade SharePlex to a new product directory:
sp_ctrl> shutdown
You are prompted for the following:
Prompt |
Input |
---|---|
Installation type |
Select <New Installation>. |
Product directory location (path) |
Enter the path to the SharePlex installation directory. If the specified directory does not exist, the installer creates it. If the directory exists, it must be empty. The installer quits if the directory contains prior SharePlex installations or other files. (Applicable only for Oracle source) In a cluster, install on the shared disk. For more information, see Installation and setup for Oracle cluster in the Installation and Setup Guide document. |
Variable data directory location |
Specify an empty directory. The installer creates the specified directory if it does not exist. Important! Do not install this directory into the SharePlex product directory. (Applicable only for Oracle source) In a cluster, install the variable-data directory on the shared disk. For more information, see Installation and setup for Oracle cluster in the Installation and Setup Guide document. |
SharePlex Admin group |
Enter the DBA-privileged group to which the SharePlex Administrator user belongs, which will own the SharePlex binaries. If the default group of the SharePlex Administrator is oinstall, select any option, and make certain this user is listed under oinstall in the etc/group file. For more information, see Installer checklist in the Installation and Setup Guide document. |
TCP/IP port for SharePlex |
Enter the port number to use for SharePlex TCP/IP communications. |
License key (do you have?) |
Press Enter to accept the default of Y (yes). If you do not have a license, enter no. For licensing on a cluster, see Installation and setup for Oracle cluster in the Installation and Setup Guide document. At any point before you run SharePlex you can add the license key with the splex_add_key utility. For more information, see SharePlex license utilities in the Installation and Setup Guide document. |
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) Event Hubs 10) All Platforms q) Quit License Utility NOTE: To install a trial version of SharePlex, users need to select the All Platforms option. |
License key |
Enter the license key you received from Quest. |
These instructions are for upgrading SharePlex when configured for an open target database running on a Linux or Unix system.
Important!
|
To run the upgrade:
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.
Grant executable permissions to the file.
# chmod 555 installation_file
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
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) Event Hubs 10) 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.
Run the appropriate Database Setup utility for your database to upgrade the SharePlex database account. See SharePlex Utilities
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:
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
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center