This topic has been locked.
3 replies Latest Post - 2012-09-20T18:06:36Z by CarlBrown
Pinned topic Missing TERMINAL string on csr file from collector
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Has anyone experienced this issue: For CPU usage rate codes LLF119 and LLF122 we used to get a string in the csr file that identified what instance a database was on for the server. The string no longer shows up so we have a problem doing a chargeback for CPU on the server. Any ideas where to look for the cause?
Updated on 2012-09-20T18:06:36Z at 2012-09-20T18:06:36Z by CarlBrown
Re: Missing TERMINAL string on csr file from collector2012-06-14T17:52:21Z in response to CarlBrownUpdate: It appears that we introduced this problem when we upgraded our DB2 LUW agent. We no longer get instance names for the databases. Has anybody else experienced this?
asmcleod 2700004QE897 PostsACCEPTED ANSWER
Re: Missing TERMINAL string on csr file from collector2012-06-28T14:58:43Z in response to CarlBrownCarl,
Seems like the database instance might be crucial to proper accountability? Probably worth opening a PMR (service request?) to have the TUAM dev team investigate.
ISTR your installation might have a complex database collection scheme (multiple DBs/versions on a single server?) - this might be related to any special configurations required in that setup.