If SharePlex cannot connect to a source or target database, you can view 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.
To view the correct database setup procedure for the database, see SharePlex utilities
You can use the connection command to update connection properties. For more information, see 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.
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.
For more information, see Assign SharePlex users to security groups.
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:
111.22.33.44 sysA.company.com sysA # source system 55.66.77.88 sysB.company.com sysB # target system
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
