How to Troubleshoot "name not found for ID" errors

Document ID : KB000100461
Last Modified Date : 07/06/2018
Show Technical Document Details
Introduction:
These kind of messages appear in universe.log at some specific times, the cause is unknown:
|ERROR|X|IO |pid=p.t| xn_get_extended_name      | O_TYPE_NODE name not found for ID <WRONG_ID>
|ERROR|X|IO |pid=p.t|| o_io_cache_data_provider_ | Error getting Name for <WRONG_ID>: 600
|ERROR|X|IO |pid=p.t| o_module_exc_cycle_emissi | Error 600 getting node name for id WRONG_ID
Question:
How can we understand the source of the error messages due to missing Objects/Nodes/Management Units like the following one?
|ERROR|X|IO |pid=p.t| xn_get_extended_name      | O_TYPE_NODE name not found for ID <WRONG_ID>
Answer:
This kind of errors come from remote nodes / wrong dependencies, in order to find out more, you have to:

1. In Node Settings of the concerned Dollar Universe node, go to the section Logging - Main log level
Replace 0 by 0,IOSERV,EXCAGENT​
Enabling traces in Main Log Level
2. Wait until the Error message appears again in universe.log and check the Job Runs of that node and other remote nodes around those times, you should be able to find out the guilty Uproc with the traces added in universe.log

2.a In case you are still unable to find the node where the query come from, you need to capture the traffic coming to the IO port of Dollar Universe.
In order to do so, you can use a tool like Wireshark or tcpdump and check the Source IP Address that connect to the IO around the time that these errors appear

3. Fix the wrong Conditions in Uprocs / wrong Management Unit definitions / wrong parameters in Scripts until you get rid of the message.
4. It is possible that you also need to reinitialize the Exchanger Data files of the node, to do so, apply the procedure described in the following article:
https://comm.support.ca.com/kb/Error-600-populating-exchange-data/KB000087151