Professional Documents
Culture Documents
5
Installation and Setup Guide
2014Dell Inc.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a
software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the
applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying and recording for any purpose other than the purchasers personal use without the written
permission of Dell Software Inc.
The information in this document is provided in connection with Dell Software products. No license, express or implied, by estoppel
or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Dell Software products.
EXCEPT AS SET FORTH IN DELL SOFTWARES TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT
FOR THIS PRODUCT, DELL SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS,
IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT
SHALL DELL BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL
DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR
LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF DELL
SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Dell Software makes no representations or
warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes
to specifications and product descriptions at any time without notice. Dell Software does not make any commitment to update the
information contained in this document.
If you have any questions regarding your potential use of this material, contact:
Dell Software Inc.
Attn: LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656
Refer to our web site (www.software.dell.com) for regional and international office information.
Patents
This product is protected by U.S. Patent #: 7,065,538 and 7,461,103 Additional Patents Pending.
Trademarks
Dell, and the Dell logo are trademarks of Dell Inc.and/or its affiliates. Other trademarks and trade names may be used in this
document to refer to either the entities claiming the marks and names or their products. Dell disclaims any proprietary interest in the
marks and names of others.
Legend
Caution: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not
followed.
Warning: A WARNING icon indicates a potential for property damage, personal injury, or death.
IMPORTANT Note, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.
Index 90
l Bold represents required components of a command or option that must be typed as shown.
l Bold Italics represents required user defined variables in example command strings.
l [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]
l 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 Arial 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 Courier New.
Examples:
sp_ctrl(sysA)>
User is a viewer (level=3)
Windows menu items, dialog boxes, and options within dialog boxes are expressed in Arial 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.
For information about planning and implementing a replication strategy, see the SharePlex Administrators
Guide. That manual also has information about:
Reporting instances
SharePlex for Oracle's target instances are ideal for offloading report and query processing because they are
accessible while being kept up-to-date, and they can be optimized with keys and indices designed for optimal
query performance. You can run reports all day long, without complaints about performance from your OLTP
users. Even during busy reporting times such as the end of the month or quarter, application response time will
be unaffected by heavy reporting. And, your organizations decision-makers will appreciate the accuracy of the
data reflected in the reports.
Important information about upgrades: Before you upgrade SharePlex, read the Release Notes for
the version you are installing. Requirements can vary from one version of SharePlex to another, and
you could be asked to take other steps instead of, or in addition to, those documented in this manual.
Instructions for upgrading SharePlex are located in the Release Notes.
Network checklist
1. Nameserver users: Add all SharePlex users to the nameserver before installing SharePlex.
Have all SharePlex users been added to the Nameserver?
2. Each system on which you are loading SharePlex must be connected to the network. The network node
name and IP address must be established sufficiently to allow the installation process to perform TCP
operations, even though the machines themselves are not yet configured. If you disconnect the system
from the network, the installation will fail. This failure might appear to be a license utility error, but it is
usually the inability of the license utilities and other components of SharePlex to perform initial TCP
System checklist
1. The SharePlex installer will need up to 120 MB of disk space to extract the compressed
installation package. Additionally, for new installations, the product install itself will require up to
200 MB of disk space.
Note: The .tpm installer may be extracted to a file system separate from the product install location by
invoking the -t option when executing the installation package. The default extraction location is in the
/tmp directory. For more information on using the -t option and other .tpm file options see the .tpm
Command Line Options on page 31.
Is there sufficient disk space to extract and complete the install?
2. The SharePlex queues grow dynamically as data is replicated. To determine the amount of disk space
that you will need for the variable-data directory, use the following guidelines.
a. Estimate the longest time that you can tolerate replication to be down.
b. Determine how much data would be replicated in that time, using the following formula as a
guide. The formula multiplies the redo log value by 1/3 because only about 1/3 of the redo log
is data that is replicated. The rest is used by Oracle for maintenance and operation of the
instance itself.
[size of a redo log] x [number of log switches in 1 hour] x 1/3 x [number of hours downtime] =
amount of disk space needed for the queues on each system
For example, if you expect to recover from 8 hours of downtime, and your redo logs are 500 MB in size
and switch five times an hour, then you could need 6.5 GB of space on both the source and target
machines for the SharePlex queues.
$ ulimit -aH
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) 1024
vmemory(kbytes) unlimited
The nofiles(descriptors) value is the one to verify and change if necessary. Changing the system file
descriptors setting requires root privileges (usually the Systems Administrator), and the system must be
rebooted after you make the change. Consult your Systems Administrator for assistance.
Instead of changing the hard limit, you can set a soft limit for this parameter, but the soft limit only stays in
effect for the duration of the sp_cop session for which it was set. When you shut down sp_cop and start
it again, the soft limit reverts back to its default value, which could be lower than the hard limit.
The soft limit can be set as high as the hard limit, but not higher. It does not require a root user to change
it. On Sun Solaris, IBM AIX, and HP-UX (Bourne shell), the following command displays the soft limit for
file descriptors.
$ ulimit -aS
The following command sets the soft limit for system file descriptors.
$ ulimit -n value
Because of the session-based limitations of the soft limit, Dell Software recommends that you use the
hard limit setting for sp_cop to ensure that the system file descriptors setting remains at a sufficient
value. If you increase the hard limit to satisfy SharePlex, you can use the soft limit to restrict other
applications to lower levels.
ulimit -a.
If you see coredump(blocks) 0, then you must change the core dump block size to ensure that a core file
is produced. (This setting must be changed before SharePlex is started.) To set the core dump block size
to a reasonable number, such as 1.5 million blocks, type the following:
ulimit -c 1500000
10. Many platforms support system-wide, user, or process-specific placement of application core files, and
customizable naming conventions for core files. For core file location, SharePlex supports only the dump
subdirectory of the SharePlex variable data directory. This is the "current working directory" for sp_cop
and the processes started by sp_cop.
For naming conventions, SharePlex supports "core" and "core.<pid>". SharePlex will rename files
named "core" to "core.<pid>" unless the core file is from sp_cop. In that case, the core file will not be
renamed. If the OS naming convention is set to "core.<pid>", all core files will have that name format.
If the SharePlex core file policy is not met, the SharePlex event log might report that a core file was not
generated. The core file generating process might exit even if a core file was actually created.
11. The ora_setup program uses SQL*Plus to install the SharePlex objects needed for replication. To
ensure that ora_setup and other non-Oracle users have permission to log into SQL*Plus, the
Oracle software must have a set-user-id of the following, which is the default configuration after
Oracle is installed:
Database checklist
1. If you are upgrading your Oracle database: If you plan to upgrade your database, perform the Oracle
upgrade before you install SharePlex. At the end of the SharePlex installation process, you will run a
program named ora_setup, which establishes an Oracle account for SharePlex, installs some database
objects, and runs an analysis that establishes object definitions. Installing the database upgrade before
you run ora_setup ensures that SharePlex has the correct object definitions.
Have all Oracle upgrades been performed?
2. Do you use Oracle Name Server? If so, ensure that the instance is listed in the oratab file prior to running
the SharePlex installation script.
Is the instance listed?
3. The minimum number of Oracle PROCESSES and SESSIONS for the Post process is calculated by
Important: The SharePlex user is created with the default Oracle profile under the assumption
that the profile has the unlimited resource privileges originally assigned by Oracle. View the
profiles in your database to verify that the default is unlimited. If the default has been changed,
assign SharePlex a DBA profile with unlimited privileges for all definitions.
The following grants are applied during ora_setup for the SharePlex user, where splex in the syntax is
the name of your SharePlex user.
a. For Oracle 9i or 10g, the SharePlex Oracle user requires the following grant to access the data
dictionary if O7_DICTIONARY_ACCESSIBILITY is set to FALSE*.
grant select any dictionary to splex;
(*SharePlex requires access to the dictionary tables outside of the standard DBA roles.)
b. To replicate DDL supported for Oracle 9i (e.g., when setting SP_OCT_REPLICATE_DDL_
ALL=1), the SharePlex Oracle user requires the following grants:
2. The installation package will prompt you for the following SharePlex Admin User and SharePlex Admin
group information:
a. SharePlex Admin User name:
If this is a new user SharePlex will create this user for you. You will need the following
information:
New user password:
New user home directory:
b. SharePlex Admin group name:
Note: If running the installation as non-root the SharePlex Admin User and SharePlex Admin group
must exist prior to install, as non-root users are not able to create new users and groups.
3. The installation package creates a product directory named by you (named /productdir in this manual)
into which it installs the SharePlex binaries.
Install the SharePlex product directory on a separate filesystem from the one containing the production
Oracle instance, but not on a raw device.
Do not install the product directory in the same directory as the variable-data directory that is created in
the Installation Checklist step 4. There are identically named sub-directories in both directories, and it is
possible that SharePlex utilities that restore replication to a clean state could affect the wrong files.
What is the name of the SharePlex product directory?
For a list of the SharePlex directories and files, see the SharePlex Administrators Guide.
4. The installation package creates a variable-data directory named by you (referred to as /vardir in this
manual) only if this directory currently does not exist. SharePlex maintains the current replication
environment in this directory, including the data files for its queues.
Install the SharePlex variable-data directory on a separate filesystem from the one containing the
production database instance, but not on a raw device, to prevent the queues from affecting the
performance of the production instance.
Other requirements for the variable-data directory:
a. Do not install the variable-data directory in the same directory as the SharePlex product directory
that is created in Installation Checklist step 3. There are identically named sub-directories in both
directories, and it is possible that SharePlex utilities that restore replication to a clean state could
affect the wrong files.
b. To determine space requirements for the variable-data directory, see System Checklist step 2.
What is the name of the SharePlex variable-data directory?
5. SharePlex uses the default TCP/IP and UDP port numbers of 2100 (for which the hex equivalent is 834).
Please review the following information about establishing the SharePlex port number.
ora9:/oracle/ora9/product: N
In this example, ora9 is the ORACLE_SID, and /oracle/ora9/product is the ORACLE_HOME.
Important!
a. Sun OS only: SharePlex uses the oratab file located in the /var/opt/oracle directory. If there is a
copy of the oratab file in the /etc directory ensure that this file is identical to the one in the
/var/opt/oracle directory.
b. If you intend to use a single set of SharePlex binaries for replicating data on a system with
multiple minor or patch release versions of Oracle, when prompted during installation for the
ORACLE_SID and ORACLE_HOME provide the information that corresponds to the lowest patch
release version intended for replication. For example, if you have a system running Oracle
9.2.0.4, 9.2.0.6, and 9.2.0.8 and you want to use a single set of SharePlex binaries, when
prompted for instance information you should associate the installation with the ORACLE_SID
and ORACLE_HOME of the lowest minor or patch release version, which in this case is Oracle
9.2.0.4. Alternately, you may install separate SharePlex binaries for each minor or patch release
version intended for replication.
c. Some oratab files have an asterisk symbol (*) instead of a specific entry for the ORACLE_SID.
This causes ora_setup to fail. Ensure that a valid ORACLE_SID exists in the oratab file.
What are the ORACLE_SID and ORACLE_HOME?
7. The installation package will attempt to associate the SharePlex Admin User with a dba privileged group
identified by the name dba. If it does not locate a group of this name and privilege it will prompt you for
the name of a dba privileged group.
Note: This group must exist prior to installation. The installation package will not create a dba
privileged group.
What is the name of the dba privileged group?
8. You will be prompted for a unique license key for each machine where you are installing SharePlex. The
ORA_SETUP checklist
1. When initiating ora_setup you will be asked for the following information:
a. The Oracle SID that the set-up process is being run against.
b. The password for the SYSDBA privileged SYSTEM account on the Oracle SID listed above.
c. The name and password of the SharePlex Admin User.
2. SharePlex requires a tablespace for its internal tables in each database involved in replication. With
the exception of the SHAREPLEX_LOBMAP tables, SharePlex tables use the tablespaces default
storage settings.
If the tables to be replicated have extensive LOB columns that are updated or inserted frequently
consider the following when sizing the tablespace:
LOB Considerations
The SHAREPLEX_LOBMAP table is created with a 1 MB INITIAL extent, 1 MB NEXT extent, and
PCTINCREASE of 10. The MAXEXTENTS of this table is 120, allowing it to grow to 120 MB. The default
storage usually accommodates this table, permitting more than 4 million LOB entries. If you expect more
than that, size the SharePlex tablespace accordingly, taking into account that this table shares the
tablespace with other SharePlex tables. The SHAREPLEX_LOBMAP table does not contain entries for
LOBs stored in-row.
If the database is using the cost-based optimizer (CBO) and the replicating tables include numerous
LOBs, incorporate the SHAREPLEX_LOBMAP table into the analysis schedule.
* For upgrades in which a SharePlex account already exists, the storage parameters of the internal
tables will not be changed.
Note: For a list of the SharePlex internal tables and their default storage values, see SharePlex Tables
in this guide.
What is the name of the default SharePlex tablespace?
3. SharePlex requires a temporary tablespace where it can perform sorts and other operations. This
tablespace will be used for sorts when the compare commands are used to compare source and target
tables to verify synchronization. Compares performed on large tables require large sorting operations,
This change to the maximum number of kernel undo structures for SYS V semaphores and the maximum SYS
V shared-memory segment size is necessary to ensure the maximum amount of protection for SharePlex
processes. This will not affect performance, but will increase system stability.
Semaphores provide a locking mechanism for access to queues; undo structures are a subset of semaphores.
The shared-memory segment is used by SharePlex queues as the primary working area and is shared by all
SharePlex processes. If the number of semaphore undo structures, semmnu, on your system is larger than 255,
do not change it. If it is smaller than 255, change it to 255. If the maximum shared-memory size, shmmax, is
greater than 60 MB, do not change it. If it is smaller than 60 MB, change it to 60 MB.
In the HP_UX environment, the configurable kernel parameters are set by the SAM utility. These changes must
be performed by someone with root-level authority before SharePlex software is installed.
l semmnu: number of processes using the undo facility (SharePlex requires 255)
Note: Editing kernel parameters requires that you overwrite the existing kernel, move the kernel to the
appropriate directory, and perform a system reboot.
Note: The instance of /stand/vmunix will not match the currently running vmunix, which may result in PS
inaccuracies.
This change the maximum number of kernel undo structures for SYS V semaphores and the maximum SYS V
shared-memory segment size is necessary to ensure the maximum amount of protection for SharePlex
processes. This will not affect performance, but will increase system stability.
Semaphores provide a locking mechanism for access to queues; undo structures are a subset of semaphores.
The shared-memory segment is used by SharePlex queues as the primary working area and is shared by all
SharePlex processes. If the number of semaphore undo structures on your system is larger than 255, do not
change it. If it is smaller than 255, change it to 255 according to the following instructions. If the maximum
shared-memory size is greater than 60 MB, do not change it. If it is smaller than 60 MB, change it to 60 MB
according to the following instructions.
In SunOS, configurable kernel parameters are set by adding entries in the /etc/system file. The changes must
be performed by someone with root-level authority before Share- Plex software is installed.
l semmnu: number of processes using the undo facility (SharePlex requires 255)
l semmsl: maximum number of System V semaphores that can be used by a single process at one time
(the minimum SharePlex requires 128)
l semume: number of undo structures per process (SharePlex requires 255)
l shmseg: number of shared memory segments per process (SharePlex requires 26)
Note: If you are using the Solaris 9 Operating System the shmmin kernel parameter value cannot be changed.
Note: The shmseg and shmmin kernel parameters are obsolete in Solaris 9 and later.
1. Change the core dump block size from the default value of 0 to a positive value
2. Ensure that the ksh shell is set.
3. Ensure that the configurable kernel parameters are set with values equal to or exceeding the SharePlex
default values.
ulimit -a.
If you see coredump(blocks) 0, then you must change the core dump block size to ensure that a core file is
produced. To set the core dump block size to a reasonable number, such as 1.5 million blocks, type the
following:
ulimit -c 1500000
l semmsl: maximum number of System V semaphores that can be used by a single process at one time
(the minimum requirement for SharePlex is 128)
l semopm: maximum number of operations that can be outstanding on a single system V semaphore at
one time (SharePlex requires 64)
l semume: number of undo structures per process (SharePlex requires 255)
l shmseg: number of shared memory segments per process (SharePlex requires 26)
Please note that the semmns and semmni kernel values are additive. You will need to add the Oracle min
values to the Shareplex min values to obtain the appropriate setting.
If a replication system is within a nameserver environment, such as NIS or NISPLUS, you have the following
choices for installing SharePlex groups:
l Use the following procedure to add the SharePlex groups and the SharePlex Administrator to the
nameserver before installing SharePlex.
Or...
l To install the SharePlex entries on the local system, add the SharePlex groups to the local /etc/group file
and assign users to them. The SharePlex Administrator named in the preinstallation checklist must be
listed in the SharePlex Admin group in the local /etc/group file and on the nameserver.
Warning! If you have not done so already, review the Preinstallation Checklist on page 11 and the
preinstallation procedures starting on page 26 before you begin the installation process.
USAGE
tpm [<options>] [ [<package> | <location>] ... ]
OPTIONS
-v, --verbose Turns verbose mode on
-h, -?, --help Prints out this message
--debug Starts the interactive debugger
--info Print information about installed
packages
--install Perform product installation
--remove Perform product deinstallation
--commit Commit last installation
--revert Revert last installation
-t, --tmp <directory> Temporary directory location
-d, --directory <directory> Working directory
-f, --force Unconditionally update existing files
--no-cleanup Do not perform cleanup on failure
--nocleanup Same as --no-cleanup, for compatibility
--list List the content of the archive
--extract Extract the archive into the current directory
-r, --responses <yaml file> Use the responses from a specified file
-D, --defaults Accept default answers
-l, --log Leave the installation log file
DESCRIPTION
Provides package management facilities. Packages can be installed, removed,
reverted or committed. The utility also figures out its role based on the command
name of its invocation path. For example, "tpm-install" is treated as "tpm --
install", "tpm-remove" as "tpm --remove", etc.
It can also be invoked as part of a self extracting package invocation, in which
case it is treated as "tpm --install".
Note: All command line options for the .tpm file are preceded by two dashes.
l Location of the installation directories, e.g. the product directory and the variabledata directory
Note: When installing the product please specify new directories that do not contain prior installations of
SharePlex or other files. The installer will exit if the directories are not empty. You may specify directories that do
not exist. The installer will create them for you.
Note: If your system has an older version(s) of SharePlex you will see a different prompt for the install
directories. Please be sure to provide new directories that do not contain prior installations or other files. The
installer will exit if the directories are not empty.
1. Login as the user who will own the install, run the .tpm file:
You will need the following information prior to running the installer:
l Location of the installation directories, e.g. the product directory and the variabledata directory
Unattended Install/Upgrade
The unattended option is designed to assist users with multiple install/upgrade instances. When invoked with
the -r option, the install/upgrade process utilizes a text response file. The responses to standard user prompts
/productdir/install
Editable response files may also be obtained from the SupportLink web site or by contacting Customer
Support directly.
The response file is divided into two (2) sections. The top section is user configurable. This is where the user
provides responses for the install/upgrade process. As stated below, only the values to the right of the colon
should be edited. Editing the values to the left of the colon could cause the process to encounter an error and
subsequently become interactive. The following example is for non-root installation:
# ./SharePlex-6.0.0-b86-oracle100-aix-52-ppc.tpm -r /splex/temp/nonroot-
upgrade-only.rsp
l spopr
l spview
Important! For Oracle 11gR2 & ASM: The Shareplex Admin user must also be in the OSDBA group for
Oracle ASM (typically named asmdba) as well as in the OSDBA group (typically named dba). For
example: $ useradd g spadmin G dba,asmdba splex
1 Administration SharePlex Can issue all SharePlex commands. Commands that can only be issued by
Admin group a SharePlex Administrator are:
l startup, shutdown
l start capture
l stop capture
l abort capture
l truncate log
2 Operator spopr Can issue all SharePlex commands except those listed above.
3 Viewer spview Can view lists, status screens, and logs to monitor replication
only.
spadmin:*:102:spadmin,root,jim,jane,joyce,jerry
a. Put user names for SharePlex Administrators in the SharePlex Admin group. You need at least
one user with Administrator rights on each source and target system.
b. Put user names for SharePlex operators in the spopr group.
c. Put user names for SharePlex viewers in the spview group.
d. To include the root user as a SharePlex user, add it to the desired group. By default, the root user
is not added to the SharePlex user groups
3. Save the /etc/group file.
4. Repeat these steps for each source and target system, including all the nodes in a cluster.
Tip: After logging onto UNIX, any user can verify his or her authorization level from the sp_ctrl interface
by issuing the authlevel command.
5. Proceed to Establishing SharePlex as an Oracle user on page 45.
l If this is a source system, run ora_setup now. You cannot commence replication until ora_setup has
been run for the source instance to establish SharePlex as an Oracle user.
l If this is a target system, choose one of the following options, depending on your replication strategy,
unless you have been instructed otherwise by a documented SharePlex procedure, a Technical Support
representative, or a Dell Software Systems Consultant.
A. If the target instance exists, and you will be using transportable tablespaces or a cold-copy
method to synchronize the data (export/import, store/restore from tape, FTP), run ora_setup now.
B. If you will be using an Oracle hot backup to synchronize the data, run ora_setup after the backup
has been applied and the database has been recovered and opened, following the instructions
in the synchronization procedure. Running ora_setup on an existing target instance, such as a
hot standby, before the backup and recovery does no harm, but you will need to re-run ora_setup
again after the backup.
l For centralized reporting (consolidated replication) using separate variable-data directories, run ora_
setup for each variable-data directory. Create a different Oracle user for each one.
l Do not alter the SharePlex for Oracle database objects. If you have questions or concerns about these
objects, contact Technical Support.
To run ora_setup
1. Start the Oracle database instance, if it is not already.
2. Log onto UNIX as a non-root user with DBA privileges.
3. View the oratab file, and make certain that the values for ORACLE_SID and ORACLE_HOME directory
paths are valid.
The oratab file is typically located in the /etc directory; however, it may be located in the var/opt/oracle
directory, as is the case for Sun Solaris platforms. If the oratab file is located in the var/opt/oracle
directory ensure that no other version of this file exists in the /etc directory. (The ora_setup process first
looks in the /etc directory and then the var/opt/oracle directory. If there are multiple oratab files they
should be identical or have different file names.)
Warning! Sometimes oratab files have an asterisk (*) symbol instead of an entry for the
ORACLE_SID, and that can cause ora_setup to fail. Ensure that the oratab file contains a valid
ORACLE_SID.
4. Make a note of the ORACLE_SID. You will need it for the setup process. To set the ORACLE_SID as the
default, export it by typing one of the following commands.
ksh shell:
export ORACLE_SID=OracleSID of this instance
csh shell:
setenv ORACLE_SID OracleSID of this instance
5. [FOR CONFIGURATIONS USING MULTIPLE VARIABLE-DATA DIRECTORIES] Export the environment
variable that points to the variable-data directory for the SharePlex instance for which you are
running ora_setup
ksh shell:
export SP_SYS_VARDIR=/full pathname of variable-data directory
csh shell:
setenv SP_SYS_VARDIR /full pathname of variable-data directory
6. Change directories to the bin sub-directory of the SharePlex product directory.
$ cd /product_dir/bin
7. If sp_cop is running, run sp_ctrl and shut down sp_cop with the following command. SharePlex cannot
be running when you run ora_setup.
$ ./sp_ctrl
sp_ctrl> shutdown
8. From the bin sub-directory of the SharePlex product directory, run the ora_setup program.
If this is the first time ora_setup is being run, create a new SharePlex user. If this is not the first
time that ora_setup is being run you may use the existing SharePlex Admin user or you may
elect to use another existing SharePlex user.
o DEFAULT tablespace for use by SharePlex
Default options are shown in brackets [ ]. To choose the default, press Enter
Note: You are allowed five attempts to enter a valid password for an existing user. At any point, you can
press Enter to return to the Create New User prompt. After five invalid passwords, you are also returned
to the Create New User prompt. Enter y to create a new user or n to quit ora_setup. If you quit, SharePlex
will not be established as an Oracle user.
Note: If you have an active configuration and you would like to change the SharePlex Oracle user, to
preserve the current replication environment copy the SharePlex objects from the existing SharePlex
users schema to the new SharePlex users schema. When prompted for the SharePlex Oracle user
specify the changed SharePlex Oracle user.
10. When the ora_setup program completes the Oracle setup process it will exit with confirmation of a
successful setup:
Important!
l Before you configure SharePlex for replication, run the demonstrations in this manual to confirm that
your installation was successful and that you are familiar with the software.
l Before you activate a configuration for production, read the following chapters in the SharePlex
Administrators Guide for additional instructions for planning and configuring replication.
Chapter 2: How SharePlex Works
Chapter 3: Running the SharePlex Programs
Chapter 4: Planning SharePlex Replication
Chapter 5: Preparing for SharePlex Replication
Chapter 6: SharePlex Optional Setup
Chapter 7: Starting SharePlex Replication
Important information about upgrades: Before you install an upgrade of SharePlex, refer to the
Release Notes for the version you are installing. Requirements can vary from one version of
SharePlex to another, and you could be asked to take additional actions beyond what is documented
in this manual. Instructions for upgrading SharePlex are located in the Release Notes.
Network checklist
1. Each system on which you are loading SharePlex must be connected to the network. The network node
name and IP address must be established sufficiently to allow the installation process to perform TCP
operations, even though the machines themselves are not yet configured. If you disconnect the system
from the network, the installation will fail. This failure might appear to be a license utility error, but it is
usually the inability of the license utilities and other components of SharePlex to perform initial TCP
operations.
Are all systems connected?
2. In some situations, machine names cannot be resolved between UNIX and Windows systems. The
workaround is to add the IP addresses and names of all UNIX and Windows servers in the replication
network to the following files, which contain mappings of IP addresses to host names.
o The hosts file on all Windows machines. The file normally is in C:\Windows\
System32\Drivers\etc).
Put each entry on an individual line. Type the machines IP address first, then tab or space over at least
once and add the corresponding host name, then tab again to add the alias. Comments can be used
after the host name if they are preceded by the pound (#) symbol.
System Checklist
1. The SharePlex install file requires 60MB of disk storage and the installation process requires an
additional 400MB of temporary disk space. When installed, the SharePlex files will utilize at least 600MB
of disk space. The MKS Toolkit installation requires at least 20MB of disk space.
Is there sufficient disk space to complete the install?
2. In order for SharePlex security features to be utilized, partition the drives that contain replication
components as NTFS. SharePlex user groups cannot function as designed on a FAT partition, since it
lacks the file security features of the NTFS format. On FAT partitions, you cannot control access to, and
use of, the SharePlex processes and the sp_ctrl user interface. Any user who logs onto a FAT partition,
regardless of his or her SharePlex user authorization level, will have SharePlex Admin group
permissions with full capability to stop, start and abort SharePlex replication processes, except for
remote logins, which retain the SharePlex group assignments.
To employ the security provided by the SharePlex user groups if FAT partitions must be used,
prevent local access to the FAT partitions by all users except SharePlex Admin group, and allow
only remote login for spopr and spview groups. Additional information about the SharePlex user
groups is on page 88.
Have security issues with FAT partitions been addressed?
3. SharePlex needs an additional 200 MB of page file size if more than 80% of the current total page file
size is being used. Greater page size provides faster processing speed when SharePlex is handling
large transactions in the queues.
Is there adequate page size?
4. SharePlex on the Windows platform uses the MKS Toolkit operating environment from Mortice Kern
Systems (MKS), formerly known as NuTCRACKER. This enables SharePlex to be ported to the UNIX
and Windows platforms in a uniform manner. The MKS Toolkit files are installed by the MKS Platform
Components installation program. One Registry entry is created under the manufacturers name,
Mortice Kern Systems, and another is created under the name Data Focus. The default folder for the
MKS Toolkit is C:\Program Files\MKS Toolkit, but if you select a different folder, ensure that it is
secured so that it cannot accidentally be moved or removed. The MKS Toolkit files must not be moved
[size of a redo log] x [number of log switches in 1 hour] x 1/3 x [number of hours downtime] =
amount of disk space needed for the queues on each system
For example, if you expect to recover from 8 hours of downtime, and your redo logs are 500 MB in size
and switch five times an hour, then you could need 6.5 GB of space on both the source and target
machines for the SharePlex queues
Important: The SharePlex user is created with the default Oracle profile under the assumption
that the profile has the unlimited resource privileges originally assigned by Oracle. View the
profiles in your database to verify that the default is unlimited. If the default has been changed,
assign SharePlex a DBA profile with unlimited privileges for all definitions.
The following grants are applied during OraSetup for the SharePlex user, where splex in the syntax is
the name of your SharePlex user.
o For Oracle 9i or 10g, the SharePlex Oracle user requires the following grant to access the data
dictionary if O7_DICTIONARY_ACCESSIBILITY is set to FALSE*.
grant select any dictionary to splex;
*SharePlex requires access to the dictionary tables outside of the standard DBA roles.
What will be the name of the SharePlex Oracle user?
6. The Oracle instance must be open before you run OraSetup, although the database does not have to be
populated. SharePlex does not create or populate the database.
Exception: If you will be using an Oracle hot backup to synchronize the data, it creates the target
instance and database files. See the SharePlex Administrators Guide for synchronization procedures.
Are all Oracle instances open?
Installation checklist
1. [CLUSTERS ONLY] If you are installing on a system cluster, follow the steps in Pre-
installation instructions for Windows cluster environments on page 65 before you install
SharePlex. After installation, follow the steps in Post-installation procedures for Windows cluster
environments on page 82.
2. At a minimum, the Oracle 9.2.0.2 client must be installed prior to installing Share- Plex. Ideally, the
Oracle Client version should match the version of Oracle involved in SharePlex replication. You can
download Oracle Client upgrades from the Oracle web site.
Is the correct Oracle client installed?
3. Assign a user who will own and write to the SharePlex product and variable-data directories. This user
must already exist on the system and must have read privileges to the Oracle redo logs. This user must
also belong to the administrators group.
Who is the owner of the SharePlex directories?
4. The installation creates a SharePlex product directory on the local system. This directory contains the
SharePlex binaries and default parameter settings. Within a cluster, you will install the SharePlex
product directory on each node so that binaries are available, Registry entries are created, and the MKS
Toolkit operating environment is established in readiness for failover.
As a normal precaution, install the product directory on a separate internal hard drive than the
production database, or on a different partition. If you do not specify a directory during installation, the
default installation directory that is used is C:\Program Files\Quest Software\SharePlex.
What is the path of the SharePlex product directory?
For a list of the SharePlex directories and files, see the SharePlex Administrators Guide.
5. The installation package creates a variable-data directory named by you (referred to as /vardir in this
manual). SharePlex maintains the current replication environment in this directory, including the data
files for its queues.
Install the SharePlex variable-data directory on a separate filesystem from the one containing the
production database instance, but not on a raw device, to prevent the queues from affecting the
performance of the production instance.
o If you are using SSH software, you can configure SharePlex to work with it through a secure
port. Using SSH for a SharePlex instance is incompatible with the SharePlex Manager
application. For instructions for establishing SSH compatibility for SharePlex, see the SharePlex
Administrators Guide.
Important: Windows users should not use port 2101. The SharePlex module, SpRemote, uses
port 2101.
Note: You may change the default TCP/IP port after installation by following the instructions located in
the SharePlex Administrators Guide. What is the port number for TCP/IP and UDP?
7. You will be prompted for the ORACLE_SID of the Oracle instance for which you are implementing
replication. The ORACLE_SID is stored in the Windows Registry.
IMPORTANT: SharePlex must link to the binaries of the version of Oracle that is involved in SharePlex
replication. Please ensure that the PATH is set correctly, with the correct ORACLE_HOME appearing first
in the PATH env variable.
Does the correct ORACLE_HOMEappear in the PATH?
What is the ORACLE_SID?
8. You will be prompted for a unique license key for each machine where you are installing SharePlex,
including each machine of a cluster. The software can be installed without a key, but you will not be able
to run it.
Permanent SharePlex license keys are generated for a specific machine ID, so be sure you know which
key was assigned to which machine. Keep a copy of your license keys in a safe place in case you need
them in the future.
For SharePlex demonstration trials only: You need a temporary demonstration key for each system
where you are installing SharePlex. If you did not receive keys, contact your Dell Software sales
representative to get them.
Do you have a valid key for each machine?
9. After you install SharePlex, but before you run OraSetup, install all current patches for your version of
SharePlex. It is possible that one or more patches were created after the software was released. To find
out if there are patches for your version of SharePlex and for instructions for downloading and applying
them, log onto Support and confirm you have the current patches: http://software.dell.com/support/.
o The password for the SYSDBA privileged SYSTEM account on the Oracle SID listed above.
2. SharePlex requires a tablespace for its internal tables in each database involved in replication. With
the exception of the SHAREPLEX_LOBMAP tables, SharePlex tables use the tablespaces default
storage settings.
If the tables to be replicated have extensive LOB columns that are updated or inserted frequently
consider the following when sizing the tablespace:
LOB Considerations
The SHAREPLEX_LOBMAP table is created with a 1 MB INITIAL extent, 1 MB NEXT extent, and
PCTINCREASE of 10. The MAXEXTENTS of this table is 120, allowing it to grow to 120 MB. The default
storage usually accommodates this table, permitting more than 4 million LOB entries. If you expect more
than that, size the SharePlex tablespace accordingly, taking into account that this table shares the
tablespace with other SharePlex tables. The SHAREPLEX_LOBMAP table does not contain entries for
LOBs stored in-row.
If the database is using the cost-based optimizer (CBO) and the replicating tables include numerous
LOBs, incorporate the SHAREPLEX_LOBMAP table into the analysis schedule.
* For upgrades in which a SharePlex account already exists, the storage parameters of the internal
tables will not be changed.
Note: For a list of the SharePlex internal tables and their default storage values, see SharePlex Tables
in this guide.
What is the name of the default SharePlex tablespace?
3. SharePlex requires a temporary tablespace where it can perform sorts and other operations. This
tablespace will be used for sorts when the compare commands are used to compare source and target
tables to verify synchronization. Compares performed on large tables require large sorting operations,
especially if there are no primary or unique keys. For more information about the compare commands,
see the SharePlex Reference Manual.
If you expect to be using these commands, take into account sorting requirements when sizing the
SharePlex temporary tablespace or choosing an existing temporary tablespace for SharePlex. The
default tablespace is the tablespace where the Share- Plex tables are installed.
What is the name of the SharePlex temporary tablespace?
4. SharePlex requires an index tablespace for the indices for its internal tables. The default for this
tablespace is the tablespace for the SharePlex tables, but performance will be enhanced if the
SharePlex tables and indices are on separate tablespaces to minimize I/O contention.
If you have a previous version of SharePlex, the SharePlex indices were installed in the tablespace
where you installed the SharePlex tables. These indices are not moved when you install this version of
SharePlex, but it is recommended that you move them to the index tablespace you are defining for this
installation. If the existing SharePlex indices are in an index tablespace, you can specify that tablespace
for this installation.
What is the name of the SharePlex index tablespace?
Installation sequence
1. Install SharePlex first on the primary node the one to which the shared disk that you created in
preinstallation checklist step 5 normally will be mounted. Do the following during installation:
o When you are prompted for the location of the variable-data directory, choose a location on the
shared disk.
o Install the license key for this node when prompted during the installation.
o Install license keys for all other nodes in the cluster at the same time that you install the license
for the primary node. To install the additional license keys, select the Add Alternate Host Id
check box in the License Key dialog box.
Tip: If you do not know the machine ID, run the SplexCpuID utility, located in the bin sub-directory of the
SharePlex product directory.
o In the SharePlex port field, select the port number.
o In the Enter License Key field, type the license key, observing spaces and spelling case. If you
received the key in a file, you can copy it (Control-c) and paste it (Control-v) into the field.
This places the secondary machines license in the shared variable-data directory.
2. Run SplexAddKey again on the primary node for each additional node in the cluster. The objective of
these steps is to place all license keys in the shared variabledata directory.
Install SharePlex on all of the other nodes in the cluster (the secondary nodes), specifying for each one a
variable-data directory on the local machine. You may use a temporary directory for this purpose. This directory
will not be used for replication, and 66 SHAREPLEX FOR ORACLE Installation and Demonstration Guide
Version 8.0 (document revision 1) you can delete all of the temporary variable-data directories from the
secondary nodes after SharePlex is installed.
Note: The reason you are installing SharePlex on each node, in addition to installing the binaries, is to establish
essential Registry entries on those nodes and to establish the MKS Toolkit operating environment, which
enables SharePlex to replicate between Windows and UNIX systems in a uniform manner.
IP addressing
Host names and IP addresses are part of the SharePlex queue structures and cannot be changed after
replication commences. A logical host name must be created, also known as a global cluster package name,
which must be mapped to the floating IP address before activating a configuration file.
To map the global cluster package name to the floating IP address, create an alias in the hosts file (usually
located in C:\\WINNT\System32\Drivers\etc) on all nodes or in a nameserver (DNS, NIS, NISPLUS). The alias
cannot contain non-alphanumeric characters, such as underscores ( _ ) or dots (.).
Example hosts file:
Perform the installation instructions in this chapter on all Windows machines involved in SharePlex replication,
including all nodes of a cluster. Before each installation, review the Windows Preinstallation Checklist on page
51 again to ensure that all of the installation requirements are satisfied on that machine.
You will need the following information prior to running the installer:
l Location of the installation directories, e.g. the product directory and the variabledata directory
l Installation type, Full or Client. If you are performing a Full install, you must know the Oracle version of
the instance that corresponds to this installation.
l SharePlex communications port number
1. Log into Windows as the SharePlex Administrator that was specified in step 3 of the Windows
Preinstallation Checklist. This user must have Administrator privileges for Windows. The installation
automatically adds this user to the SharePlex Admin group.
2. [REINSTALLATION, UPGRADES, AND PATCHES ONLY]
Stop the SharePlex service by launching the SpUtils from the shortcut on the Windows desktop and
selecting the SharePlex Services tab from the SharePlex Utility.
o If the port for this instance of SharePlex is not displayed in the Port field, select the port from the
drop-down list, and click Stop.
o Click Close to close the dialog box.
3. Launch the sp_setup installation program. (The install process will begin by displaying the Welcome
dialog box.) Proceed through the installation by following the prompts.
Important: If you cancel this installation, do not run OraSetup unless you re-install the SharePlex
software first. Otherwise, the correct port number for SharePlex will not be reflected in the
OraSetup process.
4. When you are prompted for the SharePlex folder, otherwise known as the SharePlex product directory, if
you enter the path of a different directory, and any of the folders have spaces in them (for example,
Product Directory) the path name must be within quotation marks, for example
C:\SharePlex\Product Directory.
5. When you are prompted for the port number for SharePlex, do not use port 2101 as a SharePlex port
because the SpRemote SharePlex module on Windows uses port 2101.
o Click Cancel to postpone OraSetup and continue the installation. Run OraSetup when you are
instructed to do so by the synchronization procedure. Synchronization options are explained in
the SharePlex Administrators Guide.
Important: If you cancel the OraSetup installation, it does not cancel the installation of
the SharePlex software, nor does it remove it. SharePlex is still installed on the system,
but you cannot start replication unless you first run OraSetup. You can run OraSetup at
any time by using the SpUtils or SpClient utility.
9. After closing the utility to run OraSetup, the installer will navigate you to the SharePlex Services section
of the SharePlex Utility. This will enable you to install SharePlex as a service.
After reviewing the information and instructions provided in Installing the Share- Plex service on page
77, you may:
10. When you have completed the steps above, the Installation Complete dialog box will appear, click
Finish to complete the installation. Be sure to review the Important! notes that follow these
installation steps.
11. If you were prompted to restart the system after you installed the MKS Toolkit files, you may do so now.
12. If you are using SharePlex in a cluster environment, proceed to Post-installation procedures for
Windows cluster environments on page 82. Otherwise, proceed to Assigning SharePlex users and
authorization levels on page 88
13. [OPTIONAL] If you are installing multiple instances of SharePlex on this system, you can set a default
port number for the sp_ctrl process so that it automatically connects to that port when it starts. If you do
not set a default port number, sp_ctrl connects to the SharePlex instance with the lowest port number.
Important!
l Repeat all of the installation procedures in this chapter for all Windows machines that will be involved in
SharePlex replication.
l Before each installation, review the Windows Preinstallation Checklist on page 51 again to ensure that
all of the system requirements are satisfied for each machine.
To install SharePlex on multiple ports in preparation for consolidated replication or other configurations
requiring multiple variable-data directories, see the SharePlex Administrators Guide.
Important!
l Before you configure SharePlex for replication, run the demonstrations in this manual to confirm that
your installation was successful and that you are familiar with the software.
l Before you activate a configuration for production, read the following chapters in the SharePlex
Administrators Guide for additional instructions for planning and configuring replication.
Chapter 2: How SharePlex Works
Chapter 3: Running the SharePlex Programs
Chapter 4: Planning SharePlex Replication
Chapter 5: Preparing for SharePlex Replication
Chapter 6: SharePlex Optional Setup
Chapter 7: Starting SharePlex Replication
l If this is a source system, complete the OraSetup process during installation. You cannot
commence replication until OraSetup has been run for the source instance to establish SharePlex
as an Oracle user.
l If this is a target system, choose one of the following options, depending on your replication strategy,
unless you have been instructed otherwise by a documented SharePlex procedure, a Technical Support
representative, or a Dell Software Systems Consultant:
o If the target instance exists and you will be using transportable tablespaces or a cold-copy
method to synchronize the data (export/import, store/restore from tape, FTP), it is recommended
that you complete the OraSetup process during installation.
o If you will be using a hot backup to synchronize the data, run OraSetup after the backup has
been applied and the database has been recovered and opened, following the instructions in the
synchronization procedure. Running OraSetup on an existing target instance, such as a hot
standby, before the backup and recovery does no harm, but you will need to re-run OraSetup
again after the backup.
To run OraSetup
1. Start the Oracle database instance, if it is not already.
2. Launch the SpUtils from the shortcut on the Windows desktop and select the OraSetup tab from the
SharePlex Utilities dialog box.
3. Follow the prompts through the OraSetup process. You will need the following information to complete
the process:
o SharePlex port number
o ORACLE_SID
Note: If this is the first time OraSetup is being run, create a new SharePlex user. If this is not the first
time that OraSetup is being run you may use the existing SharePlex user or you may elect to use
another existing SharePlex user.
o DEFAULT tablespace for use by SharePlex
Note: You are allowed five attempts to enter a valid password for an existing user. At any point, you can
press Enter to return to the Create New User prompt. After five invalid passwords, you are also returned
to the Create New User prompt. Enter y to create a new user or n to quit OraSetup. If you quit, SharePlex
will not be established as an Oracle user.
Note: If you have an active configuration and you would like to change the SharePlex Oracle user, to
preserve the current replication environment copy the SharePlex objects from the existing SharePlex
users schema to the new SharePlex users schema. When prompted for the SharePlex Oracle user
specify the changed SharePlex Oracle user.
Note: If you have an active configuration and you would like to change the SharePlex Oracle user, to
preserve the current replication environment copy the SharePlex objects from the existing SharePlex
users schema to the new SharePlex users schema. When prompted for the SharePlex Oracle user
specify the changed SharePlex Oracle user.
4. When the OraSetup program completes the Oracle setup process it will display a confirmation of a
successful setup:
1. From the Control Panel, double-click MKS Toolkit. The Configure MKS Toolkit dialog box appears.
2. Select the Runtime Settings tab and then select Miscellaneous Settings from the Categories
pull-down menu.
3. Under Global Settings in the Max Memory for Global Resources text box, change the value by typing
67108864 in the box
4. Click OK to close the dialog box. You must restart your system in order for the change to take effect.
l Set the SP_SYS_HOST_NAME variable in the Windows Registry to the global cluster package name
that is associated with the floating IP address. The global cluster package name is the alias you created
in the hosts file. SP_SYS_HOST_NAME instructs SharePlex to use the alias when any of its processes
issues a name lookup (gethostname), superseding the local system name. It ensures that sp_ctrl
commands are directed to the correct host, in this case the global cluster package name, and it enables
SharePlex to migrate properly during failover.
l Set the SP_SYS_VARDIR environment variable in the Windows Registry to point to the shared variable-
data directory. This ensures that the current replication environment continues to be used by SharePlex
after failover.
l [OPTIONAL] Set the SP_QUE_SYNC parameter. SP_QUE_SYNC protects data from certain system
failures that cause data corruption by writing data to disk as it is received, instead of using UNIX
buffering. Use of this parameter can significantly slow replication speed, especially posting, so you
should test it if you replicate large volumes of data.
Note: This parameter is not a substitute for UPS or any other high-availability fault tolerance system.
l Do not set these variables on source or target systems outside the cluster.
Warning! Do not add, change or remove Registry entries unless you are familiar with the functionality
of the Registry and the Windows platform. Errors when changing Registry settings can adversely
affect the operation of the software or the system itself. If you are not familiar with the Registry,
consult your Systems Administrator for assistance.
Setting SP_QUE_SYNC
If you use SP_QUE_SYNC, set it on the primary node of the cluster (the node to which the shared variable-data
directory is mounted) and on each source and target machine outside the cluster that is part of this replication
environment. For more information about SP_QUE_SYNC, see the SharePlex Reference Manual.
To monitor, control, or change SharePlex replication, a person must be designated as a SharePlex user on the
systems where he or she will be issuing commands. When designating users, you designate their authorization
levels. The authorization level defines which SharePlex commands a user can issue.
To designate SharePlex users and assign their command authorization levels, you add their names to one of
the following SharePlex user groups on the replication system(s) they will be accessing.
l spopr
l spview
Important! Or Oracle 11gR2 & ASM: The Shareplex Admin user must also be in the OSDBA group for
Oracle ASM (typically named asmdba) as well as in the OSDBA group (typically named dba). For
example: $ useradd g spadmin G dba,asmdbasplex
1 Administrator SharePlex Can issue all SharePlex commands. Commands that can only be issued by a
Admin Group Share- Plex Administrator are:
startup, shutdown
all configuration commands relating to an active configuration
all parameter commands except list param
start capture
stop capture
abort capture
truncate log
2 Operator spopr Can issue all SharePlex commands except those listed above.
3 Viewer spview Can view lists, status screens, and logs to monitor replication
only.
Before you configure SharePlex for replication, you are encouraged to start SharePlex and run the
demonstrations in this manual to confirm that your installation was successful and that you are familiar with the
software. After you run the demonstrations, refer to the SharePlex Administrators Guide for additional
information about:
l Performing administrative operations on replication systems. Refer to the SharePlex Reference Manual
for information about:
Warning! These demonstrations are intended to introduce you to the SharePlex software. All of the
demonstration components were created specifically for demonstration purposes, not deployment in
a production environment. Do not use these demonstrations as the basis for establishing replication.
To properly implement replication in your environment, use the SharePlex Administrators Guide.
Tip: The commands used in these demonstrations are described in more detail in the SharePlex
Reference Manual.
l How SharePlex resumes from its stopping point when the target system is recovered
l How SharePlex verifies synchronization and repairs out-of-sync rows When you complete these
demonstrations, you may move on to the next chapter, which contains more advanced demonstrations of
SharePlex performance and features.
qa10:/qa/oracle/ora10/app/oracle/product/10.0
In the example, qa8 is the ORACLE_SID. On Windows systems, the ORACLE_SID is in Oracles entry in the
Windows Registry.
UNIX systems
Log onto the system as a SharePlex Administrator (a member of the SharePlex Admin group).
From the bin sub-directory of the SharePlex product directory (the one containing the binaries, represented by
the productdir variable in the following syntax), run sp_cop and sp_ctrl.
$ cd /productdir/bin
$ ./sp_cop &
$ . /sp_ctrl
Windows systems
1. Log onto the system as a SharePlex Administrator (a member of the SharePlex Admin group).
2. On the Windows desktop, double-click the SpUtils shortcut to open the SharePlex Utilities dialog box.
3. Click the SharePlex Services tab to display the SharePlex Services dialog box.
4. In the Port list box of the SharePlex Services dialog box, select the SharePlex port number, then
click Start.
l The datasource (source database) the ORACLE_SID of the Oracle database on the source system
that contains the data to be replicated.
l The source objects the names of the objects within the source database that contain the data to be
replicated. You can replicate some or all of the tables and sequences within a database.
l The target objects the names of the objects in the database on the target system that will receive the
replicated data.
l The routing map the route for transporting the data. This includes the target system( s), any
intermediary systems, and the target databases ORACLE_SID. (An intermediary system is not used in
this demonstration.)
datasource:o.source_SID
splex.demo_src splex.demo_dest targetsys@o.target_SID
2. On the first non-commented line of the file, type the following, leaving no space between any
of the items.
datasource:o.source_SID
(Substitute the ORACLE_SID of the source instance for source_SID.) This tells SharePlex where to find
the table whose data will be replicated. The o. tells Share- Plex that Oracle data is being replicated.
3. On the next line, enter the owner name (splex) and table name (demo_src) of the source table,
separating the two items with a dot (.) but no spaces. Using the owners name with a table name ensures
that SharePlex replicates the correct table, since different tables in different schemas in a database
could have the same name.
splex.demo_src
splex.demo_dest
6. Type a few spaces or a tab to create a third column. Do not press Enter.
7. In the third column, type the following items with no space between them. This creates the routing map
for your configuration, telling SharePlex where to put the replicated data.
l the name of the target system
l the @ symbol
l the letter o
l a dot (.)
Example:
sysB@o.oraB
8. Save the file and exit the editor. This returns you to the sp_ctrl prompt.
9. [OPTIONAL] To view the configuration, issue the view config command in sp_ctrl on the
source system:
sp_ctrl(sysA)> view config sample_config
10. Activate the configuration in sp_ctrl on the source system. Configuration names are case-sensitive.
sp_ctrl(sysA)> activate config sample_config
11. To confirm that your configuration is active, type the following sp_ctrl command on the source system to
display a list of all configurations. The sample_config configuration should appear under File Name,
and the word Active should appear under State.
sp_ctrl(sysA)> list config
Tip: If your configuration activation fails, use the view config sample_config command in sp_ctrl to view the file.
Compare it to Template 1 on page 95 and make sure all of the information you entered is correct. For example,
check for extra spaces that are not supposed to be there, or for missing components, such as the o. before the
SID. For other configuration troubleshooting tips, refer to Chapter 3 of the SharePlex Reference Manual.
To correct mistakes in the configuration file:
Use the edit config sample_config command in sp_ctrl to correct mistakes in the configuration file before you
activate it (or if the activation failed). This command opens the file in the text editor, and you can make the
changes by editing the file. Save the changes, and re-try the activation. To change an active configuration, you
must copy it to a new file first with the copy config command, and then edit and activate the copy. For more
information about the copy config command, see the SharePlex Reference Manual.
1. Insert and commit a record into the source table (splex.demo_src) by typing:
SQL> insert into splex.demo_src values (JIM, 8001 Irvine Center Drive, 949-754- 8000);
SQL> commit;
SharePlex replicates the changes and posts them to the target table.
2. Verify that the new record is now in the splex.demo_dest table on the target system by typing the
following query:
SQL> select * from splex.demo_dest;
You can see that the row you inserted now exists in the target table as well as the source table.
1. Create a SQL script to insert 500 rows into the splex.demo_src table on the source system, following
it with a COMMIT. You can refer to the description on page 93 for the table's description when
creating the script.
2. Run the perf_mon.sh script. This script monitors the speed of the Post process. When it runs, it polls the
Post process to determine the number of operations that were processed. It repeats this poll a specified
number of times at specified intervals, and then it computes the number of INSERTs, UPDATEs,
DELETEs, and COMMITs per second that SharePlex posted during that time. The results are printed to
screen. Following are instructions for UNIX and Windows systems.
UNIX systems
Run perf_mon from the util sub-directory of the SharePlex product directory using the following syntax.
You can control the frequency and interval of the poll.
Syntax:
perf_mon.sh #_polls poll_interval
where #_polls is the number of times to poll the Post process
and poll_interval is the time interval between polls
Example:
perf_mon.sh 10 60
Windows systems
Run sp_perf_mon in the Command Prompt from the bin sub-directory of the Share- Plex product
directory. Use the following syntax. On Windows systems, the poll occurs every second and continues
until you kill it with the control+C command.
sp_perf_mon -rport_number
where port_number is the SharePlex port number
Example:
sp_perf_mon -r2100
Note: This script does not work with multiple post queues using the same port.
3. As you did in Test 1, verify that all rows have been sent to the target system. By the time you run
SQL*Plus and generate the query on the target system, the data should already have been posted.
1. Shut down SharePlex on the target system to simulate that this system is unavailable.
sp_ctrl(sysB)> shutdown
2. On the source system, INSERT and COMMIT records into splex.demo_src using the script you created
for Test 2.
3. Since the target system was made unavailable by shutting down SharePlex, meaning that there is no
Import service available on that system to receive data, the records will be queued in the export queue
on the source system. You can verify this by issuing the qstatus command, which displays the status of
all SharePlex queues on a system.
sp_ctrl(sysA)> qstatus
Figure 1 (following) is similar to what you will see when you issue the qstatus command on the source
system. Notice that there is no post queue on the source system. This is because the system is only
being used as a source system. Normally, the post queue for this configuration would be on a different
system, the target system. However, this system also could be a target system if a configuration is active
on another system.
1. Start sp_cop and sp_ctrl (if they are not already running) on the target system.
2. To verify that all SharePlex processes are started on the target system, issue the status command.
sp_ctrl(sysB)> status
The status command summarizes the SharePlex Status Database, showing you processes that are
running and any errors that occurred. The following screen shows a typical status window.
1. Stop the Capture process on the source system to simulate the interruption.
sp_ctrl(sysA)> stop capture
2. Use the script you created for Test 2 to INSERT and COMMIT records in splex.demo_src.
3. Re-start the Capture process on the source system.
sp_ctrl(sysA)> start capture
4. Check the status of the SharePlex processes on the source system to verify that Capture has started.
sp_ctrl(sysA)> status
5. Run SQL*Plus on the target system and verify that all records inserted by the script on the source
system now exist in the target database.
SQL> select * from splex.demo_dest;
1. In SQL*Plus, issue the TRUNCATE TABLE command for splex.demo_src on the source system.
Tip: SharePlex also provides a compare using command to compare all source tables in a configuration to their
target tables.
Important! These demonstrations were created specifically for demonstration purposes and are
intended to introduce you to SharePlex. Do not deploy these in a production environment or use them
as the basis for establishing replication. To properly implement replication, use the SharePlex
Administrators Guide. It is recommended that you run these demonstrations in the order that they
appear in this manual.
Tip: The commands used in these demonstrations are explained in the SharePlex Reference Manual.
l Whether or not you want old demonstration objects from a previous version of SharePlex to be removed.
This requires entering the schema name for those objects, and the script will remove them.
od_employee
Name Null? Type
---------------------------- --------------- -------------
EMP_NO NOT NULL NUMBER
EMP_FIRST_NAME VARCHAR2
EMP_LAST_NAME VARCHAR2
EMP_DOB DATE
EMP_DEPT_NO NUMBER
EMP_TIMESTAMP DATE
od_department
Name Null? Type
--------------------------- --------------- -------------
DEPT_NO NOT NULL NUMBER
DEPT_NAME VARCHAR2
DEPT_CODE VARCHAR2
od_salary
Name Null? Type
--------------------------- --------------- -------------
SALE_EMP_NO NUMBER
SAL_VALUE NUMBER
SAL_CHANGED DATE
od_sales_emp_data
Name Null? Type
------------------------------ --------------- -------------
EMP_NO_KEY NOT NULL NUMBER
EMPLOYEE_NAME VARCHAR2 (70)
SALARY NUMBER
DEPARTMENT VARCHAR2 (50)
oxc_table
Name Null? Type
----------------------------- -------------- -------------
EXC_NO NOT NULL NUMBER
EXC_TYPE VARCHAR2 (6)
EXC_TARGET_TABLE VARCHAR2 (66)
EXC_FIXED VARCHAR2 (3)
EXC_INFO VARCHAR2 (500)
EXC_TIMESTAMP DATE
Starting SharePlex
The following are instructions for starting SharePlex on UNIX and Windows systems. Start SharePlex on the
source and target systems.
UNIX systems
1 Log onto the system as a SharePlex Administrator (a member of the SharePlex Admin group).
From the bin sub-directory of the SharePlex product directory (the one containing the binaries, represented by
the productdir variable in the following syntax), run sp_cop and sp_ctrl.
$ cd /productdir/bin
$ ./sp_cop &
$ . /sp_ctrl
Windows systems
1. Log onto the system as a SharePlex Administrator (a member of the SharePlex Admin group).
2. On the Windows desktop, double-click the SpUtils shortcut to open the SharePlex Utilities dialog box.
3. Click the SharePlex Services tab to display the SharePlex Services dialog box.
4. In the Port list box of the SharePlex Services dialog box, select the SharePlex port number, then
click Start.
5. When the Current State text box shows that the service has started, click Close to close the dialog box.
6. On the Windows desktop, double-click the sp_ctrl shortcut to open the sp_ctrl command prompt
l For source_SID on line 1, use the ORACLE_SID of the source database. The SID is case-sensitive.
l For owner, substitute the owner of the object. The object in column 1 is the source object, and the object
in column 2 is the target object.
l For target_host, substitute the target machines name.
l For target_SID, substitute the ORACLE_SID of the target database. The SID is casesensitive.
datasource:o.source_SID
owner.od_department owner.od_department target_host@o.target_SID
owner.od_salary owner.od_salary target_host@o.target_SID
owner.od_timesheet owner.od_timesheet target_host@o.target_SID
When you are finished making the configuration entries, save the file using either the :wq command (in vi) or
File>Save (WordPad). SharePlex automatically saves the file in the config sub-directory.
Important! Retain this configuration file on your system, since it will be needed for another
demonstration.
1. The target system contains an ON DELETE CASCADE constraint on the od_salary table. The
constraints name is od_sal_emp_no_fk. Disable the constraint on the target table only. SharePlex
replicates the original delete and the cascading deletes from the source system, so if these constraints
are allowed to activate on the target system, SharePlex will return out-of-sync errors.
SQL> alter table od_salary disable constraint od_sal_emp_no_fk;
2. The target system also contains a trigger on the od_timesheet table. The triggers name is od_
timesheet_mod. Since triggers on target tables cause SharePlex to return out-of-sync errors, disable
this trigger on the target table only.
SQL> alter trigger od_timesheet_mod disable;
3. In sp_ctrl, issue the activate config command for the od.config configuration.
sp_ctrl(sysA)> activate config od.config
Verifying synchronization
This demonstrates the compare command. This command compares the source and target tables to ensure
their synchronization. The repair command can then be used to resynchronize out-of-sync rows that are found.
Demonstrating performance
This demonstration allows you to view performance statistics for SharePlex replication.
1. Run the od_add_emps procedure on the source system using an IN value of 2000. This adds 10,000
rows assuming you made no changes to the od_department table.
2. Run the perf_mon.sh script. This script monitors the speed of the Post process. When it runs, it polls the
Post process to determine the number of operations that were processed. It repeats this poll a specified
number of times at specified intervals, and then it computes the number of INSERTs, UPDATEs,
DELETEs, and COMMITs per second that SharePlex posted during that time. The results are printed to
screen. Following are instructions for UNIX and Windows systems.
UNIX systems
Run perf_mon from the util sub-directory of the SharePlex product directory using the following syntax.
You can control the frequency and interval of the poll.
Example:
perf_mon.sh 10 5
In this example, the Post process is polled 10 times at 5-second intervals.
Windows systems
Run sp_perf_mon in the Command Prompt from the bin sub-directory of the Share- Plex product
directory. Use the following syntax. On Windows systems, the poll occurs every second and continues
until you kill it with the control+C command.
Example:
sp_perf_mon -r2100
Note: This script does not work with multiple post queues using the same port.
1. Delete (not TRUNCATE) all rows from the od_employee table on the source system. If the od.config
configuration is still active, the cascading delete constraint on the od_salary table activates as a result of
the deletes on od_employee. SharePlex will replicate all of those deletes and remove all rows from both
target tables. If the od.config configuration is not active, delete all rows from the source and target od_
employee and od_salary tables.
2. To implement horizontally partitioned replication, create a column condition, which is conditional syntax
that directs SharePlex to replicate only certain rows from the source od_employee table, in this case
only the rows for the Sales department. To create the column condition, run SQL*Plus on the source
system and insert the following into the SHAREPLEX_PARTITION table, substituting for the variables the
SHAREPLEX_PARTITION tables owner name, the target system name, and the target database
ORACLE_SID.
SQL> insert into owner.shareplex_partition (partition_scheme, description, route, target_
table_name, ordering, col_conditions) values (sales_partition, Replicate only sales
employees, targetsystem@o.target_SID, OD_EMPLOYEE, 1, EMP_DEPT_NO=1);
datasource:o.srce_SID
owner.od_employee (emp_no, emp_first_name, emp_last_name, emp_dept_no)
owner.od_employee !sales_partition
! target_host@o.target_SID
1. Run ora_cleansp (OraCleanSp on Windows systems) on both systems according to the instructions in
Running ora_cleansp on page 139. This removes the queues from the previous demonstrations and
deactivates the previous configuration.
Note: Prior to running ora_cleansp you must shutdown SharePlex. You can do this using the shutdown
command in sp_ctrl.
2. DELETE (do not TRUNCATE) all rows from the source and target od_employee tables. This table has a
cascading DELETE constraint that deletes all rows from the dependent od_salary tables. DO NOT
delete any rows from the od_department table. This is a look-up table.
3. Grant the demonstration user on the target system privilege to execute the sp_cr package, which was
installed in the SharePlex schema during ora_setup.
SQL> grant execute on sp_cr to user_name
4. Log into SQL*Plus on the target system as the user who owns the SharePlex demonstration objects,
and run the transform.sql script from the util sub-directory of the SharePlex product directory. This
installs the od_transform_employee_insert and od_transform_employee_update demonstration
transformation routines. You are prompted for a schema and tablespace for this procedure and the name
of the Share- Plex Oracle user.
5. To direct SharePlex to call transformation routines instead of posting the SQL operations, you use the
transformation.SID file (where SID is the ORACLE_SID of the target database). Post checks this file to
determine if there is a transformation procedure that it must call. This file was installed with SharePlex in
the data sub-directory in the SharePlex variable-data directory. Open this file on the target system in
either the vi text editor (UNIX) or WordPad (Windows).
6. Follow Template 3 below to create entries in the file, using the target tables and owners. Separate each
column with at least a few spaces or a tab character. Substitute the correct owner names for the owner
variables.
Template 3: Demonstration transformation.SID file
owner.od_employee I owner.od_transform_employee_insert
owner.od_employee U owner.od_transform_employee_update
owner.od_salary I owner.od_transform_employee_insert
owner.od_salary U owner.od_transform_employee_update
SP_OPO_XFORM_EXCLUDE_ROWID
sp_ctrl(sysB)> set param SP_OPO_XFORM_EXCLUDE_ROWID 1
datasource:o.source_SID
owner.od_salary owner.od_salary target_host@o.target_SID
owner.od_employee owner.od_ target_host@o.target_SID
employee
12. [OPTIONAL] To see how transformation works for UPDATEs, you can update the od_employee table
manually. The od_transform_employee_update procedure will make the transformation. To further this
demonstration, you may construct a transformation procedure for DELETEs.
l Timestamp priority This demonstration is based on UPDATEs. Whichever row was updated LAST
takes priority when there is a conflict.
l Source-system priority In the following steps, you will define one system as the trusted source that
takes priority in the event of a conflict. This demonstration is based on INSERTs. All INSERTs that
originate on the trusted source will override INSERTs from the other system, which is referred to as the
secondary system.
There is no conflict-resolution logic in the demonstration procedure for DELETEs. Instead, SharePlex will write
failed DELETE statements to the SID_errlog.sql log and report an error to the Event Log. In addition, information
about the statement will be written to the source.exc_table table. To extend this demonstration, you can add
conflict- resolution logic for DELETEs to conform to your companys business rules.
Warning! This demonstration is intended to introduce you to the concept of peer-to-peer replication
and conflict resolution. Do not use this demonstration as the basis for establishing peer-to-peer
replication, and do not use the provided conflict resolution routines as your own. Peer-to-peer
replication is not necessarily compatible with all business applications. It requires a thorough
understanding of your data, your applications, your business rules, and how conflicts could occur.
When suitable for an environment, it requires careful execution, including the creation of custom
conflict resolution procedures that can be quite complex. Before you consider deployment of peer-to-
peer replication, please read the documentation for establishing this replication strategy in the
SharePlex Administrators Guide.
sp_ctrl(sysB)> shutdown
2. Run ora_cleansp (OraCleanSp on Windows systems) on both systems according to the instructions in
Running ora_cleansp on page 139. This removes the queues from the previous demonstrations and
deactivates the previous configuration.
3. Delete all rows in the od_employee tables on both systems. DO NOT delete any rows from the od_
department table. This is a look-up table for the conflict resolution procedure.
4. Grant the demonstration user on both systems privilege to execute the sp_cr package, which was
installed in the SharePlex schema during ora_setup.
SQL> grant execute on sp_cr to user_name
5. Log into SQL*Plus as the user who owns the SharePlex demonstration objects, and run the p2p.sql
script on both systems from the util sub-directory of the SharePlex product directory. This installs the od_
employee_gen demonstration conflict resolution routine. You are prompted for a schema and
datasource:o.trusted_source_SID
7. Referring to Template 7 below, create another configuration named od.cr_secondary on the secondary
system that is the opposite of the preceding configuration. It replicates the secondary od_employee
datasource:o.secondary_SID
owner.od_employee owner.od_employee trusted_source_host@o.trusted_source_SID
8. Activate both configurations.
sp_ctrl(sysA)> activate config od.cr_trusted_src
sp_ctrl(sysB)> activate config od.cr_secondary
Creating conflicts
Use the od_add_emps procedure to initially populate the od_employee table on the trusted source system.
SharePlex replicates those changes to the od_employee table on the secondary system, and the two are now
synchronized. Now you can create conflicts.
sp_ctrl(sysB)> qstatus
4. Issue COMMITs on both systems simultaneously.
5. Start the Post processes on both systems.
6. Verify the results by selecting the rows that were updated from both tables.
l EXC_NO
This column is the exception number of the conflict.
l EXC_TYPE
This column is the type of SQL statement, whether INSERT, UPDATE or DELETE.
l EXC_TARGET_TABLE
This column is the table on which the conflict occurred.
l EXC_FIXED
This column describes the results of the conflict resolution routine. YES means that the routine was
successful. NO means that the routine failed and the row needs to be manually changed to the
correct value.
l EXC_INFO
This column describes what the conflict resolution routine found.
l EXC_TIMESTAMP
This column shows the time that the conflict occurred on this machine.
l On UNIX and Windows systems, you can query the V$PARAMETER table through SQL*Plus.
SQL> select name, value from V$parameter where name = db_name;
l On a UNIX system, you can view the oratab file.
$ cd /etc
$ more oratab On the Solaris platform, the oratab file is typically located in the
You will see a display similar to this: var/ opt/oracle directory. Sometimes there is an oratab file in
the /etc directory as well. If there is an oratab file in the /etc
directory, remove, rename or relocate it to prevent problems
ora10:/qa/oracle/ora10/app/oracl for SharePlex.
e/ product/10.0
In this example, ora10 is the ORACLE_SID and
/qa/oracle/ora10/ product is the ORACLE_HOME
directory.
Did you receive an ld.so.1: sqlplus: fatal: libsunmath.so.1: can't open file: errno=2 error?
On UNIX systems, this error indicates that ora_setup cannot find the libsunmath and libshareplex libraries,
even though the link exists in the proper place. You can use either of these solutions:
l In the ECXpert/config/bdg.ini file in the [DB_ENV] section add the following line:
LD_LIBRARYPATH=full oracle home path/lib
Read parameters:
Default Value:
SP_ORD_MSGS_CK_FREQ 10000 number Restart Process
SP_ORD_OWNER_O qarun Set Up
Default Value:
SP_ORD_RCM_SKIP_RATIO 2 ratio Restart Process
SP_ORD_RESTART_
0 retries Live
THRESHOLD
SP_ORD_RMSG_LIMIT 1000 readrel Live
SP_ORD_UTILIZATION_
0 Live
TIMERS
You also can verify that ora_setup was performed by querying the database for tables beginning with
SHAREPLEX_, and you can check to see if an Oracle account was established for SharePlex. If these items do
not exist, shut down sp_cop and follow the instructions for running ora_setup.
l The log files in the log sub-directory. The Event log retains one entry reflecting the outcome of the ora_
cleansp procedure.
l The contents of the statusdb file in the data sub-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.
o In the Oracle SID text box, type the ORACLE_SID of the Oracle instance for which you are
running OraCleanSp.
5. Click Clean to execute OraCleanSp. Processing progress is displayed in the text box at the bottom of the
dialog box.
6. Click Close to close the dialog box.
Removing SharePlex
This procedure removes the SharePlex product and variable-data directories, including user-created files such
as configuration files, conflict-resolution files, and hints files. If there are any files you would like to keep, those
files should be backed up, copied, or archived before starting the procedure.
This script does not remove the SharePlex internal tables, their indices, or other Share- Plex database objects.
Use standard Oracle methods to remove those objects.
To run splex_remove
1. Log on as the user that installed SharePlex. (The splex_remove script should be run by the user who
installed SharePlex. Permissions errors may occur and the splex_remove script will not be able to find
installation details if another user attempts to remove SharePlex using the splex_remove script.)
2. Shut down SharePlex using sp_ctrl.
sp_ctrl(system:port)> shutdown
When you have finished with this step, exit out of sp_ctrl.
3. Use the following command to make certain that no other users are running Share- Plex and that there
are no SharePlex processes running, including sp_cop.
l The SharePlex menu items (except for the top-level Program Manager Group folder).
l The SharePlex product directory. The uninstall program also contains a custom uninstall option that
enables you to selectively remove files.
The uninstall program also contains a custom uninstall option that enables you to selectively remove files.
l Files that already existed on the system when the current version of SharePlex was installed.
l Files created by SharePlex or a user in the product or variable-data directory after the current version of
SharePlex was installed. Such files can be removed manually after SharePlex is removed. This is
standard procedure for most Windows applications.
l The SharePlex variable-data directory. To remove this directory, delete it through the operating
system. The uninstall program does not remove this directory because there could be user-created
files, such as configuration files and custom parameter settings, that you want to keep for a future
installation of SharePlex.
Automatic uninstall
In the Perform Uninstall dialog box, click Finish to complete the uninstall, or click Back to perform a
custom uninstall.
The automatic uninstall finishes and exits.
Custom uninstall
o In the Select Private Files to Remove dialog box, select the files that you want to remove by
clicking them. To deselect a file, click it again.
Or...
o Select all of the files by clicking the Select All button. This has the same effect as if you had
o INI files to edit back to the way they were before SharePlex was installed
o Registry keys to edit back to the way they were before SharePlex was installed
o Sub-systems to remove
6. In the Perform Uninstall dialog box, click Finish to begin the uninstall process, or click Back to change
any of your selections. The removal process finishes and exits.
Repair
In the Perform Repair dialog box, click Finish. The repair function detects items needing repair and performs
the repair automatically.
Important! If you intend to reinstall SharePlex or MKS Toolkit, it will not reinstall unless these Registry
entries are removed.
Warning! Do not add, change or remove Registry entries unless you are familiar with the functionality
of the Registry and the Windows platform. Errors when changing Registry settings can adversely
affect the operation of the software or the system itself. If you are not familiar with the Registry,
consult your System Administrator for assistance.
Index D
TCP/IP 38
UNIX 10 O
Windows 33, 40 Oracle user, establishing SharePlex as 29, 44, 54
binaries, version-specific 33 ORACLE_SID 16, 24, 30, 38, 45, 53-54, 63, 66,
68, 71, 75-76, 83-84
C oratab file 13, 83
changing global settings in the MKS toolkit 42 Other Term
cluster environments Subterm 40, 47
package name P
Windows cluster 40
peer-to-peer replication 61, 69
post-installation instructions
Preinstallation Checklist 10, 22, 33, 41
Windows 47
R
pre-installation instructions
read privileges 14, 36
Windows 40
redo logs 6, 11, 35
command authorization levels, assigning
replica database 8
UNIX 28
routing map 54, 67
Windows 50
T
testing replication 55
timestamp priority 72
U
uninstalling
SharePlex
UNIX system 85
Windows system 86
upgrading
database 13, 36
SharePLex 10, 33
V
variable-data directory 11, 30, 35, 40, 42, 44, 68,
71, 82-83, 86
viewer 5
W
Windows
determining ORACLE_SID 76
installing SharePlex 33
page file size 34
partition requirements 33
SharePlex requirements 33
uninstalling SharePlex from 86