udm inventory queue builds and errors are seen in discovery server logs

Document ID : KB000107701
Last Modified Date : 25/07/2018
Show Technical Document Details
Issue:
The following error messages are being seen in the discovery_server probe logs:

[probeTask-4] ERROR com.nimsoft.discovery.common.util.ExceptionUtil - Error trying to convert from CTD to UDM entity: %sjava.lang.IllegalArgumentException: Invalid UDM entity: null
[probeTask-4] ERROR com.nimsoft.discovery.common.util.ExceptionUtil - java.lang.IllegalArgumentException: Invalid UDM entity: null

and the udm_inventory queue is backing up.
 
Resolution:
This is usually an indication that the discovery_server probe has, at some point, exhausted the memory that it sets aside for udm.
The discovery_server probe memory should be increased and as part of that process the following steps done:

1. Deactivate discovery_server and select it.
CTRL+Right Click to get to Raw configure...
In the startup/opt section increase the memory settings for java_mem_max and java_mem_init
(up to 4GB for java_mem_max if required)

2. Deactivate the udm_manager probe

3. Run the SQL query DROP TABLE DATOMIC_KVS;

4. Activate the discovery_server and udm_manager probes.

The DATOMIC_KVS table will be recreated with the activation of the probes.