You are viewing limited content. For full access, please sign in.

Question

Question

Audit trail totals are constantly changing

asked on July 15, 2013 Show version history

The reports for the client are all static in nature (i.e. they only include data that should be unchanging from past dates). 

For example, he's looking for documents created on or between 7/8/13 and 7/12/13 in xyz folder. 

When he runs the report and then clicks update the total number keeps growing everytime he hits update for a few minutes. If he waits 10-15 minutes and hits update again the number starts decreasing. 

I wasn't able to login to his Db server directly (the tech I was working with is not part of their DBA team and he doesn't have rights on that server) but he did confirm via chat with one of his DBA's that the model of the server is set to simple recovery model. 

One thing that threw me off though is that he said the total size is 20 gigs - 18 gig for the mdb and 2 gigs for the t-log. The t-log max size is set to 2 gigs so it's at it's limit. I am the first to admit that I'm not a database expert but 2 gigs on a simple recovery model didn't seem right to me. 

We will check on this tomorrow to see what reducing the size does - in the meantime can anyone give me any clues as to where to go with this if neither of these issues help?

 

 

(I posted this on the regular forums as well since that's where most traffic is currently, but thought I'd post it here to help build the answers kb.)

 

0 0

Answer

APPROVED ANSWER
replied on December 3, 2013

It sounds like Audit Trail was importing an audit log, encountered an error, and rolled back the insertion transaction.  There should be an error message reported in the event log and the problematic log file should be identified in the date range configuration page.  I think you are right that the limit on the file size was the underlying impediment.  Audit Trail should detect that and attempt to reimport the failed audit log file at a later time, so it's possible to see this sort of behavior (row count increasing and decreasing) several times, especially if there are multiple audit logs that are requested to load.

1 0

Replies

replied on July 15, 2013

Hi Chris-

 

I'm afraid I don't have a good answer for you at this point. If you can reproduce his error, I would recommend opening a case with Support. However, you should see it yourself--either in person or via remote session--prior to bringing Support in.

0 0
replied on July 16, 2013

Thank you.

 

It seemed to have  fixed itself when he shrank the record set down. I am fairly sure it was the transaction log size.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.