This task describes how to enable communication between the database partition servers that participate in your partitioned database system. Communication between database partition servers is handled by the Fast Communications Manager (FCM). To enable FCM, a port or port range must be reserved in the /etc/services file on each computer in your partitioned database system.
The number of ports to reserve for FCM is equal to the maximum number of database partitions hosted, or potentially hosted, by any computer in the instance.
0 server1 0
1 server1 1
2 server2 0
3 server2 1
4 server2 2
5 server3 0
6 server3 1
7 server3 2
8 server3 3
Assume that the FCM ports are numbered starting
at 60000. In this situation: If you use a high availability solution such as IBM® PowerHA® SystemMirror for AIX® or Tivoli® System Automation to fail over database partitions from one computer to another, you must account for potential port requirements. For example, if a computer normally hosts four database partitions, but another computer's two database partitions could potentially fail over to it, six ports must be planned for that computer.
When you create an instance, a port range is reserved on the primary computer. The primary computer is also known as the instance-owning computer. However, if the port range originally added to the /etc/services file is not sufficient for your needs, you will need to extend the range of reserved ports by manually adding additional entries.
You must have a user ID with root user authority.
You must perform this task on all computers that participate in the instance.
To enable communications between servers in a partitioned database environment using /etc/services: