suddenly I found this message in eHealth one-click
"Pgm nhiPoller[Net]: Unable to add 'network element' data to the database, dropping this poll"
"Pgm nhiPoller[Net]: Sql Error occurred during operation: 'ORA-01426: numeric overflow '; possible problem data is: element id: 1246533, sampleTime: 1502629238 for table nh_stats0_1502632799."
I Don't know what happened and what to do
attached sample of the messages.
Please try to do the following and let me know how it goes.
$NH_HOME/bin/sys/nhisql "select name from nh_element whereelement_id=1246533;"
Then in OneClick, disable polling for this element or an entire device, ifyou can afford.
nhServer stopnhStopDb immediateIf possible, just reboot the system at this point, if not, ensurenhiServer.exe, nhiPoller, nhiDbServer and Oracle.exe are not running. Onceconfirmed, start eHealth and DB.
Well, checking ehealth system I see this:
]$ oerr ORA 142601426, 00000, "numeric overflow"// *Cause: Evaluation of an value expression causes an overflow/underflow.// *Action: Reduce the operands.
Not to helpful
How many devices is this affecting. Is it only a few?
If you can;t turn off polling for those devices, I would say get SNMP/StatisticsPoller/Database server advanced logging from a time when the issue occurs and an nhGetSupportInfo -type "configuration,database,databaseServer" to capture the logging and open an issue for this one
thank you Joseph for you reply, but how to reduce operands ???
my server contains around 105,000 elements and it has been like this for a while, but this message is new. I did not see it before.
Currently following are the element counts supported in ehealth configuration
The maximum Number of elements in the eHealth Database on Windows is 50K Elements.The maximum Number of elements in the eHealth Database on Linux is 75K Elements.The maximum Number of elements in the eHealth Database on Solaris is 100K Elements.
1) From the element count mentioned above you gave exceeded the element count. It might work but can lead to performance issues like these.
2) Could you check the Database Status under - Database Management -> Tasks and Information in Oneclick and see if any datafiles have any issues
3) There was also a defect also which was fixed in 6.3.3.03 if you are on ehealth 6.3.3