Signiant Support

Vacuum recommended after Maintenance removes a large number of runs Print


Summary

If the Maintenance task has not run for a long period of time, or if a Maintenance task removes an unusually large number of runs from the manager, a vacuum of critical database tables should be performed.


Discussion

Starting with version 7.1 of the Signiant manager, job records are kept in the database until removed by the Maintenance task.  This is a change from previous versions, where the scheduler maintained a set number of runs per job.

The Maintenance task is scheduled from Administration / Manager / Maintenance.  If this task has not run for a long period of time, it can remove a large amount of data from the database in one execution.  This may result in more free space being created than the regular vacuum processes can handle, and could leave the database with unusable space.  A large amount of such space may impact database performace and is likely to use more storeage space on disk.

As such, should any run of the Maintenance task remove a large amount of data, a vacuum of the following critical tables should be considered if storage space is an issue or manager performance has degraded:

dds_statistic
job_run_stat
job_run_stat_interval
scheduled_job
scheduled_job_arg
scheduled_job_run
web_log

After vacuuming the tables, perform a reindex on them as well.

Additional Information

To vacuum and reindex the tables, follow this procedure:
1.Log onto the manager as root, through the console or SSH session.
2.Stop all Signiant manager servicess.
     Linux:  /etc/init.d/siginit stop
     Windows:  use the Control Panel 'Services' applet to stop all services, except the Database service
3.Linux only: Start the Signiant PostgreSQL database service.
     /etc/init.d/siginit start dbpostgres
4.Connect to the database using PSQL:
      psql DTM_DB -U postgres
      Windows:  This will be located in the db/pgsql/bin subdirectory of the Manager's base install directory.
5.Vacuum the desired table (eg, dds_statistic):
      vacuum full analyze dds_statistic;
6.Reindex the desired table (eg, dds_statistic):
      reindex table dds_statistic;
7.Repeat steps 5 and 6 for the remaining tables.
8.Exit the SQL prompt with the \q command.
9.Linux only:  Stop the Signiant PostgreSQL database service.
      /etc/init.d/siginit stop dbpostgres
10.Start all Signiant manager services.
     Linux:  /etc/init.d/siginit start
     Windows:  use the Control Panel 'Services' applet to start the remainingSigniant services

Copyright © 2014 Signiant Inc, all rights reserved.