NetIQ AppManager Performance Profiler 4.1.2
This issue has been corrected and will be included in the 4.5 release of NetIQ AppManager Performance Profiler.
For customers that experience this issue, please contact NetIQ Technical Support and reference this Knowledge Base article and we can provide a script that will clean up existing stream ids.
By convention, the CreateDataHeader procedure does this by finding the current lowest StreamID (this process is only followed when a Stream Name is used). The seed for this is -1 so each new stream would be sequentially lower (-1, -2, -3 etc). The AMPP mod is not following that convention when using NEWID function.
The problem is that when data is being marked for delete - the stream ID created by the AMPP mod can result in a value that when processed in the delete becomes bigger than an integer (since the delete process includes a calculation that applies the mod time).