UCMDB Touching Mechanism
We have uCMDB 8.02 installed on Windows platform in production and development environment.
In dev region, last access time is getting updated properly for the CIs. If run a TQL for this it, I see little variance in the numbers for CIs. But in production region, the number of CIs' last access time getting updated is not regular.
The condtion in the query is "last access time >= date passed as parameter". I change the date to see the count. In production today it might be 10, some 6-7 days back it could be 800.
How can troubleshoot the batch job which updates last access time. What are the log files involved in this.
Thanks in Advance!
P.S. This thread has been moevd from Application Perf Mgmt (BAC / BSM) Support and News Forum to CMS and Discovery Support and News Forum. - Hp forum Moderator
My opinion is don't try to debug this "last access time", but spend more time trying to understand why the CI isn't discovered by the probe. The "last access time" is done by the reconciliation engine of uCMDB, therefore you don't have access to it as a normal administrator.
Anyway, let's refocus: take the example of one CI which has the problem. Try to redicover it and see if you have any errors with it.
Thanks for the reply.
I think the CIs are all getting discovered fine. The issuse is their last access time is not getting updated daily in the production region. The same is working fine in lower region.
Last access time is updated either by the discovery probe if there is some change in the attributes of the CIs or by touching mechanism. Since the changes in CIs not very frequent last access time is not updated by the probe frequently.
For enabling aging mechanism, touching mechansim should work properly otherwise CIs would abnormally become candidate for deletion.
Unfortunately, you can't have a "I think" here, you have to be sure. Check that the CI is discovered correctly. Once again, it's not the probe who change the last access date but the uCMDB server. Therefore, if the probe doesn't send the CI to the server, the last access time can't be changed.