Use the ora_cleansp utility to remove the current replication state on a system, including deactivating configurations.
Caution:
Oracle on Unix, Linux, and Windows
Before running ora_cleansp, consider the following alternatives:
To use this utility, the Korn (ksh) shell must be installed on the system. The utility calls this shell during processing.
ora_cleansp works in two stages to restore replication to an initial state, as follows:
truncate internal tables: First ora_cleansp truncates any SharePlex internal tables that can be truncated safely. It does not remove the SharePlex Oracle user, password, or demonstration objects.
clean the variable-data directory: Next, ora_cleansp removes the following components from the SharePlex variable-data directory:
ora_cleansp preserves user-created files such as configuration files, conflict-resolution files, transformation files, hint files, the paramdb, and the oramsglist file.
ora_cleansp deactivates configurations. To start replication after running ora_cleansp, you must activate a configuration.
Important! ora_cleansp must be run on all source and target systems to restore replication to an initial state. To verify if and when ora_cleansp was run on a system, view the Event Log on that system.
[Unix and Linux ONLY] Set the SP_SYS_VARDIR environment variable to point to the SharePlex variable-data directory. If you are running multiple instances of sp_cop using multiple variable-data directories, set SP_SYS_VARDIR for the variable-data directory that you want to clean up.
ksh shell:
csh shell:
Shut down sp_cop.
[Unix and Linux ONLY] If you have not done so already, view the oratab file to determine the values for ORACLE_HOME and ORACLE_SID for the instance.
[Unix and Linux ONLY] Set the ORACLE_HOME and ORACLE_SID environment variables.
ksh shell:
csh shell:
On the command line of the operating system, change directories to the bin sub-directory of the SharePlex product directory (note: this must be the current working directory).
Run ora_cleansp as the SharePlex user account in the Oracle instance. Note: If run as a different user, ora_cleansp does not truncate the SharePlex tables.
Additionally, on Unix and Linux, include the database/datasource name (Oracle_SID) as defined in the connections.yaml file.
Unix and Linux:
$ ./ora_cleansp database_name/SharePlex_username[/SharePlex_password]
(For an Oracle PDB): $./ora_cleansp tns_alias for pdb/SharePlex_username[/SharePlex_password]
Windows:
C:\users\splex\bin>ora_cleansp SharePlex_username[/SharePlex_password]
(For an Oracle PDB): C:\users\splex\bin>ora_cleansp SharePlex_username[/SharePlex_password@tns_alias for pdb]
Important! On Windows, if you installed SharePlex on any port other than the default of 2100, use the -r option to specify the port number. For example, in the following command the port number is 9400:
C:\users\splex\bin>ora_cleansp SharePlex_username[/SharePlex_password] -r9400
View the Event Log after you run the utility to confirm its results.
Note: If the utility generates an error message stating that it cannot remove the .../ save_SharePlex_version directory, you can ignore the message and remove this directory.
Use the pg_cleansp utility to remove the current replication state on a system where SharePlex is replicating to an Postgres target.
Caution: The effects of pg_cleansp are not reversible. To stop replication without restoring it to an initial state, you might be able to use the abort config or purge config command.
To use this utility, the Korn (ksh) shell must be installed on the system. The utility calls this shell during processing.
pg_cleansp does the following on the target system:
pg_cleansp preserves the following:
All implementations of the Postgres open-source database on supported platforms
Run the pg_cleansp utility from the bin sub-directory of the SharePlex product directory with the following syntax:
C:\users\splex\bin>pg_cleansp [port number ] database_name/user_name
where:
Enter the password at the prompt.
Enter the password for the Shareplex User :
Type Y to confirm that you want to run cleanup for this SharePlex instance.
Are you sure you want to perform the clean for '/splex/vardir/var2' and port 2200? [N] : Y
Use the td_cleansp utility to remove the current replication state on a system where SharePlex is replicating to a Teradata target.
Caution: The effects of td_cleansp are not reversible. To stop replication without restoring it to an initial state, you might be able to use the abort config or purge config command.
To use this utility, the Korn (ksh) shell must be installed on the system. The utility calls this shell during processing.
td_cleansp does the following on the target system:
td_cleansp preserves the following:
Teradata on supported platforms
Run the td_cleansp utility from the bin sub-directory of the SharePlex product directory with the following syntax:
C:\users\splex\bin>td_cleansp [port number ] database_name/user_name
where:
Enter the password at the prompt.
Enter the password for the Shareplex User :
Type Y to confirm that you want to run cleanup for this SharePlex instance.
Are you sure you want to perform the clean for '/splex/vardir/var2' and port 2200? [N] : Y
Use the SharePlex license utilities to view and add license keys to hosts in the SharePlex replication environment. Each installation of SharePlex requires a valid license key. There are three types of SharePlex license keys:
The current license model for SharePlex is to license for a specific host, which depending on edition is licensed by core(s) or socket(s) and specific message repository (i.e. database, JMS/text files) etc. Specifics of license terms should be obtained from your account manager.
If you do not have a valid license key, you may obtain one from Quest Technical Support or your Quest sales representative. Use the appropriate procedure in this documentation to obtain the necessary information to support your license request.
On Unix and Linux systems, separate utilities are used to:
Use the splex_uname utility to collect information about the local host that is required for Quest to generate a license key. Run this utility from the util sub-directory of the SharePlex product directory.
$ /proddir/util/splex_uname
The information is similar to the following example:
Local system info: Host Name = irvspxu09 Host ID = 2198894273 (831076C1 HEX) Operating System = SunOS Machine model = SUNW,UltraAX-i2 CPU Type = sparc9 CPU Speed = 500 Number of CPUs = 1
Use the splex_add_key utility to add a license key to a machine during the installation of SharePlex or afterward to convert from one type of license to another.
You can use the splex_add_key utility as follows:
To run splex_add_key
If SharePlex is running, shut it down.
sp_ctrl> shutdown
Run splex_add_key from the install sub-directory of the SharePlex product directory.
$ /proddir/install/splex_add_key
Choose the appropriate option for how to install the key:
SharePlex License Utility
1) Read license key from file
2) Enter license key manually
3) Add license key for alternate host
q) Quit License Utility
Enter option:
Note: Use option 3 when installing on secondary nodes in a cluster. To install SharePlex in a cluster, see "Preinstallation instructions for Oracle cluster" in the SharePlex Installation and Setup Guide for Oracle.
If you are entering the key manually, type the license key exactly as you received it from Quest, including the SPLEXKEY= string if one prepends the key, any spaces, and any capitalization. Press Enter when finished typing the key.
Enter the SiteMessage text string provided by Quest with the license key.
Note: If you selected option 3 to install in a cluster, the utility continually prompts for another machine ID to license, until you exit the license utility.
Use the splex_get_key utility to view the SharePlex license key, license type, and expiration date on a machine. Run this utility from the install sub-directory of the SharePlex product directory.
$ /proddir/install/splex_get_key
The information is similar to the following example:
$ /splex/proddir/install/splex_get_key Customer Name = Quest License Key = EANLCF3P56F8M1JB1K6RBJCBB6TBEP0 Product Name = SharePlex Oracle License type = demo key Expired on = 01/01/2008 12:00 AM
On Windows platforms, all licensing functions are performed through the SpUtils utility, including viewing the machine ID for a system. Launch the SpUtils utility from the shortcut on the Windows desktop.
Select the Information tab to view information about the local host that is required for Quest to generate a license key. In a cluster, run SpUtils on each node.
Use SpUtils to add a license key to a machine during the installation of SharePlex or afterward to convert from one type of license to another. In a cluster, run SpUtils on the primary node.
If SharePlex is running, do the following:
Select the SharePlex port number from the Port list.
Click Add License, then type or paste the information exactly as you received it from Quest, as follows:
(Windows Cluster) To add a license for another node in a cluster, select the Add Alternate Host Id check box, then select the machine ID from the CPU ID list box. Repeat this step to add a license to all secondary nodes in the cluster.
Click OK to close the utility.
To start SharePlex, do the following:
Select the License Key tab, then select the port number (if running multiple SharePlex instances) for which you want to view license information.
In a cluster, run SpUtils on each node to view the local license.
© 2019 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy