The Database Setup utility establishes SharePlex as an Oracle user. The SharePlex processes log into Oracle as this user on the source database to activate configurations and maintain the SharePlex internal replication tables, and they log in as this user on the target database to maintain tables there and apply replicated changes to the database through SQL*Plus.
To verify that the setup was performed on all Oracle instances, view the SP_ORD_OWNER_ and SP_ORD_LOGIN_ parameters. There should be an entry for the SharePlex Oracle user and password (encrypted). Use the following command in sp_ctrl:
sp_ctrl(sysA)> list param all read
You also can verify that the 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 run the Database Setup utility. For more information about Database Setup, see Database Setup Utilities in the SharePlex Reference Guide.
The SharePlex Oracle user requires a DBA role with unlimited privileges. The SharePlex user is created with the default Oracle profile under the assumption that the profile has the unlimited resource privileges assigned by Oracle as the default. If SharePlex is unable to interact with Oracle, check to see if the default was changed. If so, assign SharePlex a DBA role with unlimited privileges for all definitions.
Only a member of the SharePlex administrator group (default name is spadmin) can start sp_cop. A root user that is not a member of this group can start sp_cop, but no users (including root) will be able to connect through sp_ctrl to issue commands. For more information, see Assign SharePlex users to security groups.
In order for the SharePlex processes to issue name lookups and migrate properly in a clustered environment (where a package name supersedes the local system name), the SP_SYS_HOST_NAME parameter must be set to the correct package name. In addition, the host name set by this parameter must be the same on all members of the cluster so that the name can bind to a socket and the /etc/hosts file or nameserver can correctly map the parameter’s value to the correct IP address.
The sp_cop program should only be started through the cluster management software.
On Unix and Linux systems, if the filesystem is mounted as nosuid, SharePlex must be started by the installation owner. In this case, members of the SharePlex administrator group (spadmin by default), other than the installation owner, will not be able to run SharePlex.
Only one SharePlex user, the Administrator who owns the SharePlex binaries and files, is created during SharePlex installation. Other users must be assigned to the appropriate SharePlex user groups. These groups control the authorization levels for various SharePlex functions.
To issue a specific command (such as activate config or stop export), a user must have that command’s authorization level or higher. For example, a SharePlex Administrator (authorization level 1) can issue any command, but a member of the spview group can only issue status commands and a few other commands that do not directly affect the replication processes.
If SharePlex cannot resolve a host name, try creating an alias for it using a simple alphanumeric name. Map the name to the alias in the following locations:
Windows: Local hosts file
In the hosts files, put each entry on an individual line. The following is an example, where sysA and sysB are aliases:
188.8.131.52 sysA.company.com sysA # source system 184.108.40.206 sysB.company.com sysB # target system