CA Service Management

  • 1.  Reuse of Existing VirtDB Update Agents

    Posted Aug 23, 2018 10:18 PM

    We are running r12.6.

     

    We have a record type (Attached_Event) which we are using more heavily than we suspect the average site is.

     

    Looking at the output of the pdm_vdbinfo command we can see that it is putting an awful lot of work on the "00" Virtual DB Update Agent.

     

    We can see discussion where new dedicated agents are added (via @NX_VIRTDB_AGENTxx entries in the NX.ENV file) but we are wondering if we can use an under-utilised existing Agent? We have almost no activity of KPI records so is it safe for us to update the entry:

    @NX_VIRTDB_AGENT10=Kpi_Ticket_Data, Kpi_Data

    to:

    @NX_VIRTDB_AGENT10=Kpi_Ticket_Data, Kpi_Data,Attached_Event

    ?

     

    Thanks,

     

    Alan



  • 2.  Re: Reuse of Existing VirtDB Update Agents

    Broadcom Employee
    Posted Aug 24, 2018 09:23 AM

    Alan_Eth 

     

    As I am sure you are aware, CA SDM 12.6 has been End of Support for some time.

     

    What are the values of the DB Agent parameters in the NX.ENV file?

     

    Perhaps you need to allocate more DB Agents to the environment.



  • 3.  Re: Reuse of Existing VirtDB Update Agents

    Posted Aug 28, 2018 04:48 PM

    Hi Paul,

     

    We are talking about just the Update DB Agents at the moment. We have Agents 1 - 12 defined right now, the standard set plus one that was added for Animator quite some time ago. We can add another one but since every Agent defined must consume some resources, we wonder if we can safely re-use one of the existing ones that doesn't do much work right now.

     

    Thanks,

    Alan