There should be other messages around this one that provide context for the error (maybe these messages will be in daemons.log). For example, in the past, we have seen cases where the device returns the max unsigned 32-bit value for an INTEGER type which does not conform to the RME database schema (typically for flash or memory objects).
Tracking down the problem may require you to enable ICServer debugging which can be tricky, so it would be good to engage TAC at that point.
thank you very much for your response. Unfortunately we do not have a maintenance contract for this product anymore.
If I understand you correctly probably our database is corrupted. Is it an option to start from scratch ? We have exported the inventory as textfile, so we could repopulate our DB quickly. Do you believe it is possible and reasonable to reset the DB ?
I cannot comment on whether or not the database is corrupt without seeing more information from the daemons.log. As I said, typically, this error is caused by device-sided problems. However, it could be a sign or corruption.
As Dave said in his reply, you can reinitialize your database if you'd like, but the problem may very well return.