Chat now with support
Chat with Support

SharePlex 9.0.1 - Preinstallation Checklist

Unix/Linux system checklist

Requirement Completed? (Y/N)

Confirm that the platform is supported.

For more information, see Basic system requirements.


Allocate at least 4 GB of memory for SharePlex processes.

Plan for per-process memory up to 256 MB. This recommendation enables the Post and Read processes to allocate larger sets of memory when necessary.


Disable the disk cache option.

(Source system) Place the redo logs, archive logs, and SharePlex files on a file system that does not have a cache option. Disk caching may interfere with the capture process. For more information, see the SharePlex Knowledge Base article 30895.


Set the number of semaphores per process.

Semaphores help ensure the stability of the SharePlex processes. The required SharePlex settings depend on the platform, as follows:


  • semmnu: 255
  • shmmax: 60 MB

Oracle Solaris:

  • semmni: 70
  • semmns: 255
  • semmnu: 255
  • semmsl: 128
  • semume: 255
  • shmmax: 60 MB
  • shmmni: 100

Red Hat Linux:

  • semmni*: 70
  • semmns*: 255
  • semmnu: 255
  • semmsl: 128
  • semopm: 64
  • semume: 255
  • shmmax: 60 MB
  • shmmin: 1MB
  • shmmni: 100
  • shmseg: 26

    *These are additive. Add the Oracle minimum values to the SharePlex minimum values to determine the correct setting.

An alternative is to set the value to the number of queues you will be using plus 2. For more information about SharePlex queues, see the SharePlex Administrator Guide.


Set the ulimit (number of system file descriptors) to as close to 1024 as possible.

The ulimit can be set either as a system hard limit or a session-based soft limit, as follows:

  • Set a hard limit: (Recommended) A root user and system restart are required to change the hard limit, but the value remains fixed at the correct level to support SharePlex. Consult your System Administrator for assistance.
  • Set a soft limit: A soft limit setting stays in effect only for the duration of the sp_cop session for which it was set, and then it reverts back to a default value that may be lower than the hard limit and too low for SharePlex.

Set soft and hard limits for the SharePlex user

Set a soft limit and a hard limit for nproc and nofile for the SharePlex O/S user in the /etc/security/limits.conf file.

  • shareplex O/S user soft nproc 2048
  • shareplex O/S user hard nproc 16384 '
  • shareplex O/S user soft nofile 1024
  • shareplex O/S user hard nofile 65536

As an alternative, you can simply use the setting for the Oracle O/S user.


Set core file parameters.

  • Set the system core dump block size as large as system resources can accommodate, at minimum 1.5 million blocks. The default is usually 0. Core files help Quest support representatives resolve SharePlex support cases. Higher size settings ensure that enough data is captured to be useful.
  • Set the core file output location to the dump sub-directory of the SharePlex variable-data directory.
  • Set the naming convention of core files to either core or Note: SharePlex renames all core files named core to, except for those generated by sp_cop.

If these requirements are not met, the SharePlex event log might report that a core file was not generated, even though a file exists.


Install the ksh shell.

Install the ksh shell before you install SharePlex. The SharePlex monitoring scripts and other features required this shell.

A version of ksh called pdksh is included with the Red Hat Linux builds. Refer to the Red Hat Linux documentation for more information.


Install Native POSIX Threading Library (NPTL)

Quest recommends using the Native POSIX Threading Library (NPTL) on Linux. NPTL is faster and behaves more like other Unix operating systems than LinuxThreads. Although LinuxThreads can be enabled per process by using the LD_ASSUME_KERNEL environment variable, setting that variable adversely affects the performance of SharePlex. If LD_ASSUME_KERNEL is employed, use a setting of 2.4.21.


Set the UNIX account that installs SharePlex to -rwsr-s--x using set-user-id.

The value of -rwsr-s--x enables the Database Setup utility to connect to an Oracle database through SQL*Plus to install the SharePlex database account and objects during installation. The UNIX account that installs SharePlex owns this program.


(Debian Linux)

Create a symbolic link to the /lib64/ library path.

On Debian Linux, the / library files are not in the /lib64/ location that SharePlex expects. Before installing SharePlex on Debian Linux, create a symbolic link to /lib64/


(Oracle Database) Configure the oratab file.

Make sure that the correct ORACLE_SID and ORACLE_HOME values are explicitly listed in the oratab file. SharePlex refers to this file to set its environment.

On Sun machines, SharePlex only uses the oratab file that is 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.


Windows system checklist

Requirement Completed? (Y/N)

Confirm that the Windows version is supported.

For more information, see Basic system requirements.


Address FAT security issues.

The SharePlex user groups determine who can control the SharePlex processes. These groups only function as designed on an NTFS partition. A FAT partition lacks file security, and any user who logs onto a FAT partition has full control of SharePlex.

If SharePlex must be installed on a FAT partition, allow the SharePlex admin group to log in locally, and allow the spopr and spview groups to log in remotely only. Remote logins to a FAT partition preserve group assignments. For more information, see Assign SharePlex users to security groups.


Be prepared to restart the system.

On the Windows platform, SharePlex installs the MKS Toolkit® operating environment from Parametric Technology Corporation (PTC). The default folder for the MKS Toolkit® is C:\Program Files\MKS Toolkit.

Set system permissions so that the MKS Toolkit files cannot be moved or removed after they are installed.

If this is a first-time MKS Toolkit installation, you will be prompted to restart the system.


Adjust the page size.

SharePlex needs an additional 200 MB of page file size if more than 80 percent of the current total page file size is being used. Greater page size enables SharePlex to process large transactions more quickly.


Assign a user who will own the SharePlex directories.

Assign a member of the Windows Administrator group to own the SharePlex installation and variable-data directories. This user must exist before you run the SharePlex installer and must have system privileges to read the Oracle redo logs.


(Oracle Database) Verify the Oracle Registry entries.

(Test machines only) On machines where Oracle has been installed and uninstalled many times, the Oracle entries in the Registry may be corrupted. Before you install SharePlex on a test machine, uninstall all Oracle software and delete all Oracle Registry entries. Then, re-install Oracle by using the Oracle installation program, which creates Registry entries correctly. SharePlex relies on these entries to obtain database environment information.


(Oracle Database) Set ORACLE_HOME as the first entry in the PATH variable.

SharePlex expects the path to the Oracle binaries to be the first entry in the Windows PATH system variable. Change the variable, if needed, and verify that the path is correct.


Oracle checklist

Requirement Completed? (Y/N)

Perform any required database upgrades.

Perform any required database upgrades before you install SharePlex. This ensures that SharePlex gets the most current object definitions when you run Database setup during the installation and setup steps.


Confirm the Oracle release version and processor type.

(source and target databases)

Verify that the Oracle release version is supported by SharePlex. For more information, see Basic system requirements.

Note: SharePlex does not support 32-bit Oracle versions.


Set up Oracle online and archive logging.

(source databases)

  • Enable archive logging to avoid the need to resynchronize data after a log wrap.
  • Enable minimum supplemental logging.
  • Enable supplemental logging of primary and unique keys.
  • Configure the logs to support replication.

For more information, see the SharePlex Installation Guide.


Set up database objects to support replication.

(source and target databases)

Set up Oracle objects to support replication properly, including:

  • Log primary and unique keys.
  • Handle tables that do not have keys.
  • Handle indexes, triggers, constraints, and sequences.

For more information, see the SharePlex Installation Guide.


Configure database properties to support replication

(source databases)

Make the recommended database settings to support SharePlex processes:

  • Verify character sets are compatible with SharePlex.
  • Adjust log buffer size.
  • Adjust open cursors and processes parameters.
  • Adjust initrans setting of SHAREPLEX_TRANS table.

For more information, see the SharePlex Installation Guide.


Set privileges to capture TDE-protected data.

(source databases)

To decrypt TDE-protected data from the redo log, the SharePlex Administrator must open the Oracle Wallet with the wallet password. By default, only the Oracle Wallet owner-user has read and write permissions for this file. To enable SharePlex to open the wallet, you can either of the following:

Grant read permission to the wallet file to the dba group, because the SharePlex Administrator user is a member of that group.


Have the owner of the wallet start SharePlex.

For more information, see the SharePlex Installation Guide.


Plan the SharePlex Oracle account.

(source and target databases)

During SharePlex installation, you will run the Database Setup utility to create a database account (user and schema) for SharePlex. The following is a list of privileges required for the database user who runs the this utility:

Non-multitenant (standard) database

The user who runs the setup utility must have DBA privileges, but if support for TDE is required, then this user must have SYSDBA privileges.

Multitenant database

The user who runs the setup utility should have SYSDBA privileges (recommended), but at minimum the user should be a DBA user with privileges for sys.users$ and sys.enc$. The minimum following grants are required for the SharePlex user:

create user c##sp_admin identified by sp_admin;

grant dba to c##sp_admin container=ALL;

grant select on sys.user$ to c##sp_admin with grant option container=ALL;

If TDE support is required for the CDB, then the following additional priviledge is required:

grant select on sys.enc$ to c##sp_admin with grant option container=ALL;


Plan the SharePlex objects tablespace.

(source and target databases)

The Database Setup utility installs some tables into a tablespace of your choosing. All but the SHAREPLEX_LOBMAP table use the default storage settings of the tablespace.

The SHAREPLEX_LOBMAP table contains entries for LOBs stored out-of-row. It is created with a 1 MB INITIAL extent, 1 MB NEXT extent, and PCTINCREASE of 10. The MAXEXTENTS is 120, allowing the table to grow to 120 MB.

Preferred action: If you enable supplemental logging for primary and unique keys, you can set the SP_OCT_ENABLE_LOBMAP parameter to 0, and nothing will be stored in the SHAREPLEX_LOBMAP table. In this case, you do not have to consider its size growth. It is recommended that you enable supplemental logging for primary and unique keys to maximize the performance of the Read process.

Alternate action: The default storage usually is sufficient for SHAREPLEX_LOBMAP, permitting more than 4 million LOB entries. If the Oracle tables to be replicated have numerous LOB columns that are inserted or updated frequently, consider increasing the size the SharePlex tablespace accordingly. Take into account that this table shares the tablespace with other SharePlex tables.

If the database uses the cost-based optimizer (CBO) and the tables that SharePlex processes include numerous LOBs, incorporate the SHAREPLEX_LOBMAP table into the analysis schedule.

Note: A new installation of SharePlex does not change storage parameters from a previous installation.


Plan the SharePlex temporary tablespace.

(source and target databases)

The Database Setup utility prompts for a temporary tablespace for SharePlex to use for sorts and other operations, including sorts performed by the compare commands. The default temporary tablespace is the one where the SharePlex objects are installed. If you plan to use the compare commands to compare large tables, especially those without a primary or unique key, specify a dedicated temporary tablespace for SharePlex.


Plan for theSharePlexindex tablespace.

(source and target databases)

The Database Setup utility prompts for a tablespace to store the indexes for the SharePlex tables. The default index tablespace is the one where the SharePlex objects are installed. To minimize I/O contention, specify a different index tablespace from the one where the tables are installed.

Note: If indexes from a previous version of SharePlex are installed in the SharePlex objects tablespace, you can move them to a different tablespace and then specify that tablespace when you run the setup utility.


Install the Oracle client.

(source and target databases)

The Oracle client libraries are needed both for installation and setup as well as for the operation of SharePlex.


Consider Case if replicating to an Open Target database

To support replication between a source of one database type and a target of another type, the letter case of the names of the source and target columns must be the same, for example the column names on both sides in lower case or both sides in upper case. If the case differs between the source and target column names, use the column mapping feature to map the column names in the configuration file.


Amazon EC2 checklist

Requirement Completed? (Y/N)

Install on multiple EBS volumes

  • Install the database and SharePlex on Amazon Elastic Block Storage (EBS). An EBS volume is persistent storage, whereas the default Amazon storage is non-persistent and data is lost when the instance shuts down. EBS volumes also provide better performance. Minimum size for a volume is 1GB.
  • To optimize disk performance, create multiple EBS volumes and combine them by using software RAID. According to benchmarks, the optimal number of EBS volumes is 8.

Assign Elastic IP addresses

Amazon Elastic IP addresses are static, which satisfy SharePlex requirements. An Elastic IP must be created and assigned to both the source and target machines that will be used with SharePlex.


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating