I'm trying to edit some AF templates and getting this error:
I would like to know if set the autogrowth is the recomended for this situation. Where can I get this information?
Ok, after you stop your analyses from writing to static attributes, the next thing you want to do is trim your FindChange tables. You can do that yourself via afdiag or if you need help, please contact tech support. That should get you back to a better state.
As per the error reported, database file size is full and request you to contact your database administrator to increase the file size. Looks like your database db file and log file size is limited and can be set to autogrowth at DB level based on space availability.
Any database changes should be coordinated with your database administrator.
Before changing the database settings, perform some size checks:
what was the size when the database was created?
how big is it now? what is causing it to grow?
if you are using event frames, they stay in the database until deleted; can any be deleted?
Setting the autogrowth may help, but also ensure that regular maintenance is being completed.
This should include backing up the database and possibly shrinking it.
Are you using a full version of SQL Server or an express version? From memory, I believe the express version has a maximum size limit; check the size limit if appropriate.
Hi Carmichael and Shaik! Thanks for the help.
I'm from Brazil, so sorry for the english mistakes.
I'm the first one configuring the AF on this client. They already have de PI data archive and PI AF instaled for years, but they didn't use the AF. I have created some elements, analysis and event frames, and backfill it for one year.
I don't have access to the PI Data Archive machine or the AF server machine, or SQL Server Machine. I'm working with a remote machine with PI System Explorer instaled and that is all. I'm not accostom to work like this, so I wold like to know if is possible with this configuration analyse the logs or same indices to make sure there the problem whas not the creation or the backfilling, and also know where the database got full. What osisoft manual or relese notes can help me?
I have opened a tiket to de Client IT Department to analyse the database but they will take longer to answer.
Thanks for the help!
I will try to answer your questions.
From your statement: I have created some elements, analysis and event frames, and backfill it for one year.
Elements and analyses do not take much space in the SQL database; event frames can take a large amount of space.
If you backfilled event frames for a year, I think that is what is causing database issues.
In PI System Explorer, you can go to the Event Frames menu and search for them, and then delete them if you need to.
When you backfill the PI Data Archive, AF will calculate the values and send the results to the PI Data Archive, but that does not greatly affect the size of the SQL Database.
Since you are the first to create the event frames, I would suggest deleting the event frames you have created and backfill for only a short period of time, such as a week or a month, and check the event frames. When the results are what you expect and you have worked with your IT department, then you can backfill the event frames for a longer period of time.
This is likely something that has to be managed from the server side. Deleting the event frames will not decrease the size of the PIFD database until a shrink operation is performed. You can try to shrink the database, and then to avoid performance cost associated with fragmented indexes you should run AFDiag /reindex to rebuild the indexes.
Your AF database is small based on the screen shot of the Database Properties - 3500 event frames, 567 elements should take up very little space. Looking at your initial screen shot, it is very apparent to me what the problems are:
1) you have analyses that are writing to static (non-PI Point) output attributes. Every time these analyses execute, you create a row in your FindChanges table. You should avoid configuring your analyses to write outputs to static (non-PI Point) attributes, especially at high rate. Please search our tech support website for KB article on this.
2) looks like you turned on auditing in your AF Server. This, in combination with 1) about, is generating a LOT of SQL writes to tables that apparently have exceeded your disk allocation.
To correct your problem, you need to stop configuring your analyses to write (output) to static (non-PI Point) attributes. Then you need to trim your audit tables to reclaim your disk space. If you don't know how to do this, please consult the AF documentation on how to reduce the size of your AF audit tables, or contact tech support. They can help you.
I suspect 1) and 2) together is really slowing down your AF system. If you correct these problems, you should have a much more responsive AF system. Lastly, if you do not have a great need for AF audits, I would suggest you simply turn it off.
There was SQC Analysis mapped to Static output attributes. I had removed them, because they were not really necessary rigth now, but in the future they will probably be.
I didn't turn on Auditing Trail.
Are you using SQL Express?
No, we aren't using SQL Express.
Retrieving data ...