Click the flag for your language.

You can combine the update routine with system maintenance.


Old rundowns are usually no longer used. Please use broadcast reports from the stations for history research.
Cleaning up old rundowns makes sense for two reasons:

  1. Rundowns can contain news bulletins and traffic information. These “External” items are also refreshed in old rundowns. The more rundowns there are, the more External items must be refreshed. As a result, the renewal will eventually become slower and slower.
  2. Items that are still in rundowns will not be removed from the Trash. To make the Trash as empty as possible, it is best to first remove old rundowns.

Start the GML Manager and go to Options> Rundown cleanup. Choose a Station or leave [All stations], choose an End date (for example 14 days before today), click ALL at the bottom and then CLEANUP. Depending on the amount of rundowns, this can take some time.


Delete (if possible) Logger items, raw recordings, items in the Dropbox etc.

Deleted items are moved to the Trash. If you delete a Category, its items will also appear in the Trash, however, these items will only be visible after a restart of the ONE Server. Therefore, always first move all items to the Trash or other categories before you permanently delete a category.


Only an administrator can permanently delete the items in the Trash from the database. Use the GML-Manager for this, go to Options> DB tools. There is the “Empty trash” function. Associated audio files on the storage are also deleted.


  • Shutdown the ONE-Server (clients can remain active!)
  • Use the Explorer to navigate to the Live folder where the database is located
  • Use the ONE_DbManager application to open the ONE_Base.abs file
  • At the Database menu, select Change Database Params

Make shure that Max connections shows: ‘4’ and confirm with OK.

  • At the Database menu, select Repair

This cleans up empty ‘pages’ that arise over time and the indexes on the various tables are rebuilt. Repair can take a long time!

Close the ONE_DbManager when the repair action is ready. The ONE_Base.abs file will have become a lot smaller in most cases. The update and maintenance is now complete, restart the ONE-Server, all clients will reconnect automatically.

Was this article helpful?

Related Articles