SharePlex 8.6.6 - Installation Guide

If users cannot run sp_cop or sp_ctrl

Was the initiating user an authorized SharePlex user?

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.

Is this a cluster environment?

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.

Was the filesystem mounted as nosuid?

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.

If users cannot issue commands in sp_ctrl

Did you assign them to the SharePlex groups?

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.

See Assign SharePlex users to security groups for more information.

If SharePlex cannot connect to a host

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:

• Network: The NIS and DNS servers
• UNIX: Local /etc/hosts file

• 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:

111.22.33.44   sysA.company.com   sysA   # source system
55.66.77.88    sysB.company.com   sysB   # target system

If SharePlex cannot connect to the database

If SharePlex cannot connect to a source or target database, you can verify the login credentials that are being used for that database by using the connection command with the show option. For example:

sp_ctrl> connection r.mydb show

or...

sp_ctrl> connection o.mydb show

You can also view connection settings in the connections.yaml file, which is stored in the data sub-directory of the SharePlex variable-data directory. If there are no settings in this file, it means that the SharePlex database setup procedure was not performed on this database. See the SharePlex Installation Guide for the appropriate database setup utility to run for your database type.

To update connection information

If you need to update the connection information, use the connection command with the appropriate options. For more information, see the SharePlex Reference Guide.