Hello Christer,
As I wrote before, please treat all those production.log entries as informational messages.
I don't take those as errors unless there is corresponding message in tema.log.
Pretty often DB2 statistics could be inconsistent depending on the level of database update activity.
To cope with that ILMT runs RUNSTATS command to keep those statistics updated.
Those inconsistent state warnings doesn't influence ILMT behavior in any possible way and should be ignored.
We will update the documentation to make it crystal clear...
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
------------------------------
Original Message:
Sent: Wed May 03, 2023 03:22 AM
From: Christer Borg
Subject: Loads of "No row was found" in production.log
Thanks Oktawian!
I think that the documentation, or a tech note, need to be more clear about this.
The only place I could find any information about the production.log was under the Server Log File entry, in the troubleshooting section, where there is a short section.
It also states "Most of the information that is written in this log is also available in the tema.log.".
This is not true - on one of my systems there are 30.000 lines in production.log, but non of them are in tema.log.
Maybe it is true for real errors, but not for 99.99% of the messages.
If I only have had one system to manage I really had thought there was something wrong!
But now I could see it happened on all systems I checked, which all seamed to work well.
There are also two other messages repeatedly found in production.log:
- Some statistics are in an inconsistent state. The newly collected "TABLE" statistics are inconsistent with the existing
"INDEX" statistics.. SQLCODE=2314, SQLSTATE=01650, DRIVER=4.28.11
- The recursive common table expression "DBO.T" may contain an infinite loop.. SQLCODE=347, SQLSTATE=01605, DRIVER=4.28.11
Not found in tema.log but from my point it looks like a problem.
IMHO, this looks more like a debug log, and there is probably good reasons to have it.
But it most be made clear in the documentation how to interpret the messages in it.
//Christer
------------------------------
Christer Borg
Original Message:
Sent: Tue May 02, 2023 05:19 AM
From: Oktawian Powązka
Subject: Loads of "No row was found" in production.log
Hello Christer,
Actually this is a kind of a informational message which only shows up in production.log.
You don't see a corresponding message in tema.log right ?
Actually, those 'No row was found' entries can be found in any older ILMT version.
I'd check if it's possible to get rid of those particular messages...just not to scary Customers.
Nevertheless, those warnings doesn't influence ILMT behavior in any possible way and should be ignored.
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
Original Message:
Sent: Tue May 02, 2023 04:19 AM
From: Christer Borg
Subject: Loads of "No row was found" in production.log
This happens in 5 different customer installations I have checked, and in my test installation as well.
Starting from version 9.2.29 there are thousands of messages in production.log saying:
"No row was found for FETCH, UPDATE or DELETE; or the result of a query is an empty table.. SQLCODE=100, SQLSTATE=02000, DRIVER=4.28.11"
They are all RedHat 7 with DB2 11.5.8.0.
The only common thing between them is that there are no VMManagers created, due to AIX clients only or agreement with IBM.
Is this a known issue?
Should I open a PMR?
//Christer
------------------------------
Christer Borg
------------------------------