Hi,
It looks like the element connection from one of the elements is not passing the data to the destination element correctly. I saw that by checking trending on one of those parameters.
From source element:
From destination element:
Element Connections:
“Channel 1” Instance comes from Channel Status table and “Channel 1 Probe” comes from Probes Status table from source Element:
In Element Connections, Display Key is specified for instance, and if we look in ElementConnections.xml configuration file, there I found sParamIndex that comes from Primary Key column:
Does this configuration file look fine? What do we need in sParamIndex, Display Key or Primary Key column? What do we need in "Instance" field in Element Connections from DM Cube, Primary or Display Key column?
10.3.9.0-13347-CU2
Hi,
Based on the screenshot, I'm assuming that the destination element is using the protocol SES S.A. Channel Manager in the 1.0.1.x range? If that is the case then the Channels table with id 1000 is the destination?
If above is correct, then it means that the destination table is using naming. A destination table with naming is only supported since DataMiner 10.3.12, which means that the version that is being used here (10.3.9) is not supported and will result in unexpected behaviour. See RN here
Regards,
Hi Laurens, thank you for your answer. That’s correct protocol that element use. I changed naming option to NamingFormat but that didn’t solve the issue.
Hi Dario, NamingFormat is the same thing in the background like naming, this is just a different syntax of expressing the same. An update to a DataMiner version that supports the mentioned RN will be needed.
Regards,
What is the DataMiner version?