125 gig tmp file?!
Just noticed today that our Analysis Disk Storage had somehow jumped up to 75% full. Since it's a fairly new box, we knew it couldn't be just from regular reporting.
After some inspection, we found a 125 gb tmp file called asat0003.tmp located in E:\nic\3501\INACNCR-AS1\tmp (with E: being the path to our NAS device).
Does anyone know how this file was created, and whether it is OK to remove it?
Thanks in advance.
Sadly, this is an issue we are very familiar with, as should all enVision users. We have complained about this file as it has run our AS out of disk space severasl times. I believe it is something they are looking to remedy in the new version, but I am not certain.
This temp file can be cleared safely by restarting the nic web server service.
It appears to me that this tmp file increments when reports are run (i have seen this with ad-hoc reports. i have not looked at the behavior with scheduled reports) and enVision never cleans this up.
I HOPE this is resolved with 4.x. We run 3.5.2 and have experienced the same disk space issue.
Thats funny i too ran into this very issue tonight and just happened to remeber to search the forum for it just by chance someone else posted on the issue. same file, same location. Thanks for the posts.
Bah - that's lightweight - I've seen it get much bigger than that
The root cause of this is execution of reports that need to load zillions of events into the temporary reporting tables before running SQL to pare down the results. It's usually the ASAT0003.tmp file that is the culprit.
Preventative measures (and I realize sometimes you can't always do these):
- Try to avoid reports that are little more than massive "lists" of data
- Fine-tune reports to better-use indexing by MessageID
The ASAT3.tmp file size can be reset by restarting the NIC WebServer Service
If you find that this is caused by reports you have scheduled to run overnight, you can perhaps schedule a restart of the WebServer service sometime after your reports have executed. Just keep in mind, particularly if your enVision user base straddles time zones, that restarting the WebServer service will force people out of the GUI and kill anything they are currently working on...