This manual provides instructions for installing and setting up SharePlex on an Oracle source database and all supported target types.
This manual also contains some demonstration tutorials that show how certain features of SharePlex work.
For the complete SharePlex documentation set, go to https://support.quest.com/shareplex/technical-documents.
You can download, view and save this document in Adobe PDF format. Click Download in the upper right-hand corner of this page. This action downloads the entire publication.
The following typographic conventions are used in this guide.
[Brackets] represent optional command components and may also be used in example command strings to emphasize required user defined variables in long strings.
Example:
reconcile queue {queuename} for {datasource-datadest} [on host]
A vertical bar, or “pipe” character, ( | ) within brackets or braces indicates that you can use only one of the enclosed components.
Example:
abort service {service | all}
Names of commands, programs, directories and files are expressed in Bold.
Other names are expressed in capital letters using the default font.
Examples:
The sp_ctrl program is located in the bin directory.
Open the oramsglst file.
Find the value for ORACLE_HOME.
Click Apply.
System displays, such as prompts and command output, are expressed in a monofaced (fixed-space) font.
Examples:
sp_ctrl(sysA)>
User is a viewer (level=3)
Windows menu items, dialog boxes, and options within dialog boxes are expressed in Bold.
Example:
From the File menu, select Print.
System names are expressed generically or fictitiously. When necessary, the source system (or primary system) is referred to as SysA. Target systems (or secondary systems) are referred to as SysB, SysC, SysD, and so forth.
Review and satisfy all of the requirements in this checklist before installing SharePlex.
Note: The requirements in this checklist apply to all source and target systems where SharePlex will be installed unless otherwise noted.
| Requirement | Completed? (Y/N) |
|---|---|
|
Add SharePlex users and groups to the nameserver. If you are installing SharePlex in a network managed by a nameserver such as NIS or NISPLUS, do the following before you install SharePlex:
The SharePlex security groups spadmin (administrator), spopr (operator), and spview (viewer) control access to SharePlex processes. Add each SharePlex user to one of these groups on the nameserver. For more information, see Assign SharePlex users to security groups. To add the user groups:
To add SharePlex groups to the local system after you install SharePlex, see Assign SharePlex users to security groups. |
|
|
Ensure that SharePlex can resolve host names. If you find that SharePlex cannot connect to a host, try mapping the host name to an alphanumeric alias in the following locations:
In these files, put each entry on an individual line. The following is an example, where sysA and sysB are aliases: 111.22.33.44 sysA.company.com sysA # source system 55.66.77.88 sysB.company.com sysB # target system |
|
|
Resolve to the right network card If you have multiple network cards on Windows, you must set the SP_SYS_HOST_NAME environment variable to the network card name or IP address that you want SharePlex to use as the local host. Otherwise, if the server reboots after the SharePlex configuration is activated, the IP address may bind to a different network card from the one that is bound in the replication configuration. For more information about SharePlex environment parameters and how to set them, see the SharePlex Reference Guide. |
|
|
Allow access to Amazon EC2 instance For an EC2 instance, make certain that the appropriate network group is set up to allow access to EC2 instances. |
|
|
Verify the SharePlex port number. By default SharePlex uses the port number 2100 (hex equivalent is 834) for both TCP/IP and UDP. If port 2100 is available to SharePlex, no further action is needed. You will need to enter the SharePlex port number during the installation procedure, at which time you can specify a different port number if needed. Important! The SharePlex port number must be the same one on all machines in the replication configuration so that they can communicate through TCP/IP connections. Make certain the SharePlex port number is open for both TCP/IP and UDP on the firewall. |
|
|
Verify TCP/IP settings SharePlex replicates over any TCP/IP network connection. Typically, if all of the tables in a database are being replicated, SharePlex replicates about 33 percent of the redo log volume, the remainder being mostly maintenance data used by the Oracle software. The following is a formula for determining bandwidth. (size of a redo log) x (number of log switches in 1 hour) x 1/3 = volume of data per hour For example, if the redo logs are 20 MB in size, and they switch six times an hour, SharePlex will replicate approximately 40 MB each hour: 20 x 6 x 1/3 = 40 MB/hour |
|
|
VerifyTCP protocol SharePlex has been tested on IP v6 networks, but it is impossible to test all scenarios. See the System Requirements in the SharePlex Release Notes for more informationon. |
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center
