Database Errors
Hi,
We are running BT 10.1 SR4 Enterprise Automation. Commander is running on a dedicated Windows Server 2008 and the system database is on our SQL-Server. Layouts and logs go to the database.
Two days ago I noticed that History Explorer has become sluggish and print logging is about 30mins behind real time. Printing however works without delays.
The messages log has started showing loads of errors and from the SQL-database we can see that there are tasks which seem to lock the database and time out eventially.
Logging has started 1.1.2015 and so far our database has grown significantly. To fix the problem we ran the database maintenance script directly from the database and defined to remove all records older than two weeks. Now no messages older than two weeks are present but the database file size is still at 13,5GB and the logs show multiple error messages. For a normal database the size shouldn't be a problem. Since the labels printed are somewhat production critical and the sequence is important we would like to have a backlog where we can check what was printed and when. Initially we wanted to have a backlog of six weeks but now we seem to get problems at four weeks.
What are these errors and what can be done to rectify the problem?
Kind Regars
Pete
[attachment=1418:error_log.JPG] [attachment=1419:database_size.JPG]
-
Pete,
I see that you reported this already to our EMEA tech-support team.
Please confirm that this is indeed the case and feel free to post an update on the case here.
0 -
Hi Domingo,
This is indeed reported to support and with your help we have managed to find out what causes the problem.
As it seems there is a limit to how much a database can hold data before it starts to slow down while processing it. When we reduced the ammount of information to be logged to the database and "cleaned up" the database no more locks have appeared.
Kind Regards
Pete
0
請登入寫評論。
評論
2 條評論