DX Infrastructure Management

The probe_discovery queue is filling up with data and sending out alerts of being bigger that 1Gb.

low Java Memory setting for the discovery_server probe

table indexes needs to be rebuild regularly

To allocate more (e.g. double) Java Memory for the discovery server probe open the raw configuration with Shift - right mouse click on the probe in IM.

select startup - opt

updating the following:

java_mem_max = -Xmx1024m

The above is the default what ever your value please double then deactivate and activate the probe to have it take affect.

We also recommend setting up a sql Job to run the following queries on a nightly basis:

ALTER INDEX ALL ON S_QOS_DATA REBUILD;
ALTER INDEX ALL ON CM_GROUP REBUILD;
ALTER INDEX ALL ON CM_COMPUTER_SYSTEM REBUILD;
ALTER INDEX ALL ON CM_COMPUTER_SYSTEM_ATTR REBUILD;
ALTER INDEX ALL ON CM_DEVICE REBUILD;
ALTER INDEX ALL ON CM_DEVICE_ATTRIBUTE REBUILD;
ALTER INDEX ALL ON CM_CONFIGURATION_ITEM REBUILD;
ALTER INDEX ALL ON CM_CONFIGURATION_ITEM_METRIC REBUILD;
ALTER INDEX ALL ON CM_CONFIGURATION_ITEM_ATTRIBUTE REBUILD;
ALTER INDEX ALL ON CM_CONFIGURATION_ITEM_DEFINITION REBUILD;
ALTER INDEX ALL ON CM_CONFIGURATION_ITEM_METRIC_DEFINITION REBUILD;
ALTER INDEX ALL ON NAS_ALARMS REBUILD;
ALTER INDEX ALL ON NAS_TRANSACTION_SUMMARY REBUILD;
ALTER INDEX ALL ON NAS_TRANSACTION_LOG REBUILD;

Next, in udm_manager.cfg:

1.)In the " Raw Configure" setup, add the following key under the " Setup" section: " schema_transact_retries" and set the value to 5000.

2.) Also change the "schema_connection_timeout_minutes" value to 30

https://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.TEC1974379.html