Environment
NetIQ AppManager 6.x
NetIQ AppManager 7.0.x
NetIQ AppManager Report Agent
Situation
Resolution
The solution involves locating the corrupt data stream and removing it from the repository. Locating the offending DataID can take some time. Following are a couple of suggestions for locating an incorrect ArchiveDataHeader record:
1. If the knowledge script name is known, the following SQL Query will return a list of all data streams created by that knowledge script. Compare the KPName to the Legend, to make sure they make sense. The following example assumes the name of the knowledge script is NT_CPULoaded:
select DataID,JobID,MachineName,KPName,Legend From ArchiveDataHeader where KPName LIKE '%NT_CPULoaded%'
2. Assuming the DataID (n) of the offending data stream is known, to remove this invalid data stream, use the following SQL Query Statement:
DELETE ArchiveData where DataID = n
DELETE ArchiveDataHeader where DataID = n
Cause
The ArchiveDataHeader table of the AppManager Reposiotry contains an invalid record for a data stream that is being called by the report.
For example, a DATA STREAM which apparently lists NT_CPULoaded as the KPName, but PDiskQueue (1 D:)^^# as the legend, was causing the report to fail when setting the UNITS value, which doesn't match.