#2 Bad data in _StmtStat : CPU = 2147483642

[Laurent CHASTEL]

Hello,

I sometime have bad data in statement statistics, procedures statistics,...

I identify that those screen get data from table XXX_StmtStat.
The line that generate the issue are line where StartTime is after EndTime.

In such case, CpuTime, WaitTime, LogicalReads, PacketsSent and/or PacketsReceived contains value which are near max value of in 2147483647

What is the best way to clean those database ?
I don't think that deleting the line is good because we will lose the execution.
Updating the value could be the solution, but I don't know which value to set.

Where should this modification be performed ? As a external treatment ?

ASEMON version is 2.7.6 for both logger and report.
Monitored servers are ASE 15.0.3 and 12.5.0.3

In attachment, you will find the result of next query, that shows the line in error.

select StmtID, BootID, KPID, SPID, BatchID,
StartTime=convert(varchar, StartTime, 109), EndTime=convert(varchar,EndTime, 109), datediff=datediff (ms, StartTime, EndTime),
ExactStat,Login, Application, ClientHost, ClientIP, ClientOSPID, DBID,
ProcName,PlanID,ContextID,LineNumber,CpuTime,WaitTime,MemUsageKB,
PhysicalReads,LogicalReads,PagesModified,PacketsSent,PacketsReceived,NetworkPacketSize,PlansAltered, RowsAffected
from FCE_StmtStat where datediff (ms, StartTime, EndTime) < 0

[Laurent CHASTEL]

The attachment

[Jean-Paul Martin]

I know MDA tables sometimes contains bad data. New ASE versions have fixed many of them, but evn in V15.7 , it's not perfect. Asemon clears some of them, but not everywhere. Yes you can execute a post-treatment on archive tables, there is no way otherwise.