Events are not pruned and the das database is increasing in size

Events are not pruned and the das database is increasing in size

Version

7.0.1.2053 (P15) and 7.0.1.2139 (P16)

 

Issue

Events, that should have been pruned by the DailyPrune Task based on the Event Log Management settings, are still showing in the Bit9 Console.

 

Symptoms

  • The das database is increasing in size
  • The Events table is increasing in size and in records number:

The following query will show the count of events:

select count(*) from Events (nolock)

 

The following query will show the minimum timestamp for events that exist in the database:

select min(ReceivedTimestamp) from eventsGUI (1033)

 

  • The DailyPrune Task shows a successful execution each night
  • No errors, related to the DailyPrune task, are logged in the Reporter log.

 

Cause

This will happen only on versions 7.0.1.2053 (P15) and 7.0.1.2139(P16).

The ProcessDailyStats stored procedure refers to a DB table that does not exist in this version and therefore fails to execute.

Being the first stored procedure to execute on the DailyPrune task, it stops the entire task execution, without logging additional errors.

 

Solution

To resolve the issue, choose one of the following options:

 

- Upgrade to the latest version of 7.0.1 or 7.2.

 

OR

 

- Recreate the ProcessDailyStats stored procedure in the das database, using the attached sql script:

    • For 7.0.1.2053 (P15) use: ProcessDailyStats_P15Fix.sql
    • For 7.0.1.2139 (P16) use: ProcessDailyStats_P16Fix.sql
Labels (1)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎08-28-2015
Views:
504
Contributors