Meaning of "Num Agents running" in pdm_vdbinfo output

Article Id: 15097
Status: Published
Updated On: 14-02-2018 07:48
Legacy Id: TEC1395936
Products:
SUPPORT AUTOMATION- SERVER , CA Service Desk Manager - Unified Self Service , KNOWLEDGE TOOLS , CA Service Management - Asset Portfolio Management , CA Service Management - Service Desk Manager
Issue/Introduction:

Pdm_vdbinfo is one of the best tools for determining when to increase the number of database agents. The pdm_vdbinfo command produces a report that shows you what each database agent is currently doing in your CA Service Management environment.

 

There are two variable shown in the output which could provoke confusion: "Num Agents running" vs "Max Config Agents"

 



What is the meaning of the value for "Num Agents running" in pdm_vdbinfo output?

 

========================================
VDBINFO invoked at MM/DD/YYY HH:MM:SS
========================================
Min Config Agents    = 6
Max Config Agents    = 6
Max DB Agents        = 6
Tgt num idle         = 2
Num Agents running   = 20
Num Agents starting  = 0
Num Requests pending = 0
Actual num idle      = 5

 

Agent #0 - (UPD) prov#4288_bpvirtdb_srvr @07/06/2017 20:57:17 with 0 in work
Agent #1 - (UPD) prov#7820_bpvirtdb_srvr @12/31/1969 18:00:00 with 0 in work
Agent #2 - (UPD) prov#6864_bpvirtdb_srvr @12/31/1969 18:00:00 with 0 in work
Agent #3 - (UPD) prov#7420_bpvirtdb_srvr @12/31/1969 18:00:00 with 0 in work
Agent #4 - (UPD) prov#7164_bpvirtdb_srvr @12/31/1969 18:00:00 with 0 in work
Agent #5 - (UPD) prov#5684_bpvirtdb_srvr @12/31/1969 18:00:00 with 0 in work
Agent #6 - (UPD) prov#4892_bpvirtdb_srvr @12/31/1969 18:00:00 with 0 in work
Agent #7 - (UPD) prov#7228_bpvirtdb_srvr @07/06/2017 20:57:20 with 0 in work
Agent #8 - (UPD) prov#4812_bpvirtdb_srvr @12/31/1969 18:00:00 with 0 in work
Agent #9 - (UPD) prov#4972_bpvirtdb_srvr @12/31/1969 18:00:00 with 0 in work
Agent #10 - (UPD) prov#4440_bpvirtdb_srvr @12/31/1969 18:00:00 with 0 in work
Agent #11 - (UPD) prov#7644_bpvirtdb_srvr @12/31/1969 18:00:00 with 0 in work
Agent #12 - (UPD) prov#4468_bpvirtdb_srvr @07/06/2017 20:57:16 with 0 in work
Agent #13 - (UPD) prov#7080_bpvirtdb_srvr @07/06/2017 21:12:05 with 0 in work
Agent #14 - (SEL) prov#5232_bpvirtdb_srvr @07/06/2017 21:07:11 with 0 in work
Agent #15 - (SEL) prov#3368_bpvirtdb_srvr @07/06/2017 21:07:11 with 0 in work
Agent #16 - (SEL) prov#1888_bpvirtdb_srvr @07/06/2017 21:07:11 with 0 in work
Agent #17 - (SEL) prov#4264_bpvirtdb_srvr @07/06/2017 21:07:11 with 0 in work
Agent #18 - (SEL) prov#7192_bpvirtdb_srvr @07/06/2017 21:07:11 with 0 in work
Agent #19 - (SEL) prov#5964_bpvirtdb_srvr @07/06/2017 21:07:11 with 4 in work

Environment:

Release: SMITAM99000-14.1-Service Management-IT Asset Manager Package
Component:

Resolution:

Open NX.env file and look for MAX_DBAGENT and  NX_VIRTDB_AGENTn variables:

@NX_MAX_DBAGENT=6                      <=Define SELECT Agents

@NX_VIRTDB_AGENT1=                      <=Define UPDATE Agents, AGENT#0 is not shown in NX.env.

...

@NX_VIRTDB_AGENTN=

 

Max Config Agents : Specifies the maximum number of Select agents to start. The NX_MAX_DBAGENT variable sets this value. In this example, the bpvirtdb_srvr is configured to start up a maximum of 6 SELECT database agents. 

 

Num Agents running :Identifies the total number of UPDATE agents currently connected to the bpvirtdb_srvr process.  It is the sum of SELECT and UPDATE agents: MAX_DBAGENT +  NX_VIRTDB_AGENTn values.