Database (ETL) jobs are not running

If the ETL job (Websense_ETL_Job_wslogdb70) is not running:

Steps

  1. Use SQL Server Management Studio to make sure the current, active logging partition is not flagged as “suspect.”
    If the “suspect” flag appears, notify your Database Administrator or IT department and request that data and disk recovery be performed, if necessary. When the recovery process is complete, start the ETL job.
  2. Use SQL Management Studio to see if records exist in the dbo.incomingbuffer table under wslogdb70.
    If there are records in dbo.incomingbuffer:
    1. Locate the dbo.wse_etl_config table.
    2. Right click the table name and select Edit top 200 rows or Select top 1000 rows.
    3. Check the value under max_buffer_size. If the value is negative, revert it to a positive value.