Procedure to expire database from Reporter 9 via CLI
search cancel

Procedure to expire database from Reporter 9 via CLI


Article ID: 166405


Updated On:




A Reporter server stopped because it ran out of disk space. Reporter not accessible through the Web interface to expire old data.



As the Reporter failed to properly startup, perform the following steps to change the Reporter configuration and perform database expiration:

1. Stop Blue Coat Reporter service.

2. Go to the directory to which Reporter is installed. For example: C:\Program Files\Blue Coat Reporter 9.

3. Browse to Settings folder and then the Databases folder.

4. Open each database_xxxxx.cfg file in a text editor. Change the value in Days under keep and change the Time Frequency to the current time. The following example configures the database Salomie to expire data older than 30 days at 14:00 daily.

database_b5068ca08dd511dfabf5f1ae476312c2 = {
  label = "Salomie"   ===> Database Name
  type = "main"
  state = "enable"
  version = ""
  creation = "1278953474"
  database = {
    options = {
      database_type = "v9_1"
      database_directory = "C:/Program Files/Blue Coat Reporter 9/databases"
      archive_directory = "C:/Program Files/Blue Coat Reporter 9/archive"
      database_root_directory = ""
      expiration = {
        keep = "30"    ===> Data Expiration for 30 days
        frequency = {
          type = "day"
          minute = {
            0 = "0"
          } # minute
          hour = {
            0 = "14"   ===> Perform expiration at 14:00           } # hour
        } # frequency
      } # expiration

5. Start Blue Coat Reporter service.


NOTES: The above steps assumed you have already set database expiry up on each database, and are reducing the days you want to expire they database from a value greater than 30.   This is may not work, as you may have completely run out of disk space even to load Reporter.   You may need to add disk space temporarily to enable Reporter to load successfully, and expire the data out of the database.   The above steps assume that the Reporter service is down while editing these files. If your reporter service is still up the cfg edits you perform will be overwritten when the service is restarted, as Reporter caches all it's CFG files in memory.