A Monitoring Process Fails To Start On Linux Or Unix After Changing A .Profile For Root - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

Before you begin
Before completing the steps below, verify with your database administrator that
the following conditions are not the cause of the problem:
v The database manager has not been started on the database server.
v The database manager was stopped.
v The database agent was forced off by the system administrator.
v The database manager has already allocated the maximum number of agents.
v The database agent was terminated due to an abnormal termination of a key
If the problem is not due to any of the above, it is most likely that the application
is using multiple contexts with the local protocol. In this case, the number of
connections is limited by the number of shared memory segments to which a
single process can be attached. For example, on AIX, the limit is ten shared
memory segments per process.
Procedure
1. On the computer with the database that you want to connect to, configure the
2. On the server system, log in as the DB2 instance owner.
3. Set DB2COMM to TPC/IP, for example:
4. Edit the /etc/services file to include both a DB2 connection service port and a
5. Update the database manager configuration, such as, db2 update dbm cfg
6. Start and stop DB2:
What to do next
Restart the portal client.
A monitoring process fails to start on Linux or UNIX after changing a
.profile for root
IBM Tivoli Monitoring processes such as the monitoring server, portal server,
warehouse proxy agent, summarization and pruning agent, and other agents are
all started while you are logged on as a user ID on Linux and UNIX systems.
For many shell environments, the user ID has a .profile file that is run during the
initial processing to ensure a consistent working environment and must satisfy
certain requirements.
The .profile must satisfy these requirements:
database manager process.
database manager to use TCP/IP on AIX.
db2set DB2COMM=tcpip
DB2 interrupt connection if they do not already exist, such as,
db2cDB2 50000/tcp # DB2 connection service port
db2iDB2 50001/tcp # DB2 interrupt connection
# service port
using svcename db2cDB2. The argument after svcename must match the name
of the DB2 connection port service that you placed in /etc/services.
% db2stop
% db2start
Chapter 6. Connectivity troubleshooting
123