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. |
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.
Run the appropriate Database Setup utility for your database to upgrade the SharePlex database account. See SharePlex utilities.
These instructions are for upgrading SharePlex on the Windows platform.
Important!
Do not uninstall SharePlex or the MKS Toolkit® environment before upgrading. Install the upgrade over the existing version.
To run the upgrade
(If using copy/append) Stop sp_sync_launcher on the target systems before applying the SharePlex upgrade.
sp_ctrl> stop launcher
(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.
Stop the SharePlex service:
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. |
Run the appropriate Database Setup utility:
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
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. Nutzungsbedingungen Datenschutz Cookie Preference Center