If you installed SharePlex on this system before, and you are re-installing it, the installation will return errors if SharePlex is running on this system. Shut down SharePlex using the shutdown command in sp_ctrl. If you are unable to run sp_ctrl, or if any SharePlex processes will not die, locate the process (using ps -ef | grep sp_ on Unix and Linux systems) and kill it. When all SharePlex processes have been killed, run the installation program again.
Check to see that all systems on which you are loading SharePlex are connected to the network. The network node name and IP address of each system must be established sufficiently to allow SharePlex to perform TCP operations, even though the target machines themselves are not yet configured.
If your environment uses a name service such as NIS or NISPLUS, you need to add the SharePlex groups and services to the nameserver before you run the SharePlex installation program, and the SharePlex Administrator must be named in the SharePlex Admin group on the nameserver before you install SharePlex. Instructions are on page 31. If these procedures are not performed, the installation will generate an error at the point in which it attempts to verify that the groups exist.
The database must be open while you are installing SharePlex.
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.
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.
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:
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. 이용 약관 개인정보 보호정책 Cookie Preference Center
