Menu

#23 Illegal Pie Plot

open
nobody
None
1
2012-09-23
2012-05-04
Scavenger
No

See attached screenshot

I should warn you that this could be self inflicted. We're running ASEMON in a test environment where we keep running
the same day over and over. In our case it's a March 14th batch run. In order to distinguish one days March 14 run from
the next days March 14 run in ASEMON, I have to add an offset to the timestamp data in the ASEMON_ARCHIVE database after
each batch run. For example, when we ran a March 14th batch on 'real date' April 27th, I added an offset to the timestamp
data so my data looks like it was run on April 27th. Is that clear?

Anyway, maybe I missed adding the timestamp to one of the ASEMON tables. What's the underlying ASEMON_ARCHIVE table that the Pie
Chart is being built from?. I'll look at my data in that table to make sure the date is correct.

Discussion

  • Scavenger

    Scavenger - 2012-05-04
     
  • Jean-Paul Martin

    So I understand that you update the archive tables. The only two tables involved in the query are "xxx_Cnx" and "xxxx_CnxActive". You can see the source code in "graphPieProcess.php. You can also remove the commented line "// JpGraphError::Raise($query);" in this file and requery your page and see the SQL statement for each of the 3 pies. May be the join does not retrieve info for the "logical reads" pie. In that case I don't understand why it does work for the two other graphs.

     
  • Scavenger

    Scavenger - 2012-06-04

    JP. I see in the latest ASE 15.7 EBF (released May 31) that Logical Reads are zero if "statement statistics active" is off. The workaround is to turn it on.

    Here's the text from the EBF.

    CR 686604 : Incorrect LogicalReads value in various MDA Tables

    The LogicalReads columns in the following MDA tables will always be 0 if
    "statement statistics active" is off:
    
        monOpenObjectActivity 
        monOpenPartitionActivity 
        monProcessActivity 
        monProcessStatement
    
    To workaround this issue, turn "statement statistics active" on if you need
    to use the LogicalReads value from the above MDA tables.
    
     
  • Scavenger

    Scavenger - 2012-06-04

    That would explain the illegal pie plot error I think.

     
  • Jean-Paul Martin

    you are right, I did a test with V15.7ESD#1 with "statement statistics active"=0 and logical reads are all zero in monProcessActivity. This was not the case before V15.7. So it explains why your pie plot has no data

     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB