VIRTDB_LOCK_AGENTS setting in 17.3
search cancel

VIRTDB_LOCK_AGENTS setting in 17.3

book

Article ID: 273978

calendar_today

Updated On:

Products

CA Service Management - Service Desk Manager CA Service Desk Manager

Issue/Introduction

Please advise what the number of update SQL agents should be for variable VIRTDB_LOCK_AGENTS in 17.3.  

How do you determine which update agent is currently responsible for doing the record lock entries looking at pdm_vdbinfo?  

If this variable is not installed, is the default number of update agents for locks = 1?

If we install this setting and assign more update SQL agents to also assist with lock processing, will this affect the other work that these agents should do?  Will we see more queued transactions on more agents?

 

 

Environment

Release : 17.3

Cause

 

 

Resolution

Q :  What the number of update SQL agents should be for variable VIRTDB_LOCK_AGENTS in 17.3.  

@NX_VIRTDB_LOCK_AGENTS is the dedicated VIRTDB_AGENTS configured on the table usp_record_lock. 

pdm_options_mgr -c -s VIRTDB_LOCK_AGENTS -v <XXX> -a pdm_option.inst
pdm_options_mgr -c -s VIRTDB_LOCK_AGENTS -v <XXX> -a pdm_option.inst -t

XXX = Default value is 1.  It can be set to 2 or max 4. 

Q:  How do you determine which update agent is currently responsible for doing the record lock entries looking at pdm_vdbinfo?  

It would be difficult to determine the exact virtdb Agent details.  The NX.ENV file will have the dedicated VIRTDB_AGENT for specific tables and other tables use the available VIRTDB_AGENT from the pool. 

Q :  If this variable is not installed, is the default number of update agents for locks = 1?   

Unless the option is installed explicitly, no VIRTDB_AGENT is associated to the USP_RECORD_TABLE.

Q : If we install this setting and assign more update SQL agents to assist with lock processing, will this affect the other work that these agents should do?  Will we see more queued transactions on more agents?

There is no limit in configuring VIRTDB_AGENT. For better performance one may add 20 VIRTDB_AGENT and gradually increase . Once an environment reach 40 such agents, then its advisable to alter 
@NX_MIN_DBAGENT=6 @NX_MAX_DBAGENT=24 ( Once VIRTDB_AGENT are 40 , you may set the DBAGENTS to 10) 

How to add VIRTDB_AGENTS: 

Edit NX. ENV

Add the below code :

@NX_VIRTDB_AGENT14=usp_owned_resource

@NX_VIRTDB_AGENT15=ca_contact