db2sysc is the DB2 engine (instance). Each agent maps to a client process or
one of the processes in the list below. Do you have db2ptree installed? To see
the real process names, use db2ptree - this should map the db2agents to the
real process names:
db2agent - DB2 agent. Handles requests from applications.
db2agnta - Associated (but idle) subagent.
db2agntp - Active subagent. Used for SMP parallelism.
db2dlock - Local deadlock detector. One per database partition.
db2fcmdm - FCM daemon (EEE only). One per machine per instance.
db2gds - Generic daemon spawner. One per database partition.
db2glock - Global deadlock detector (EEE only). One per database (on
catalog node).
db2ipccm - IPC communication manager. One per database partition.
db2loggr - Used to manipulating log files to handle transaction
processing and recovery.
db2panic - The panic agent. Handles urgent requests after agent limits
have been reached at a particular node. (EEE only)
db2pclnr - Page Cleaner.
db2pdbc - PDB (Parallel Database) Controller. Handles parallel requests
from remote nodes. (EEE only).
db2pfchr - Prefetcher.
db2resyn - Used for two phase commit.
db2srvlst - Used to manage lists of addresses for systems such as O/S
390.
db2sysc - DB2 system controller.
db2wdog - DB2 watchdog. Handles abnormal terminations.
db2tcpcm - TCP communication manager.
Joe Philip wrote:
What is the relationship between db2sysc and db2agents? When I do a ps -ef,
I see only one db2sysc process and the rest are db2agent. I run HP-UX 11.
When I monitor through HP monitoring tool Glance, these processes show up
db2sysc.
