Last successful ETL job ran more than 4 hours ago

Troubleshooting > Log Server and Log Database issues > Last successful ETL job ran more than 4 hours ago

Last successful ETL job ran more than 4 hours ago

Administrator Help | TRITON AP-WEB and Web Filter & Security | Version 8.2.x

The ETL (Extract, Transform, and Load) job is responsible for processing data into the partition database. If the job does not run regularly, data is delayed in being written to the Log Database, resulting in reports and Dashboard charts that are out of date.

Typically, the ETL job runs quickly and is scheduled to start again 10 seconds after it completed its last process. If no records are being passed to the database, however, (for example, because there's no traffic due to a network problem, or because Filtering Service or Log Server is not running), the job does not run until it starts receiving data again.

If the job has not run recently:

Make sure Microsoft SQL Server is running (see Log Database is not available), and that no other processes that use significant resources, such as a full backup or antivirus scan, are running.

Also check the disk IO to verify that the machine is able to handle a fast insertion rate into the database.

Use the linked procedure to check for Log Database problems.

Verify that you are using one of the following certified versions of Microsoft SQL Server:

SQL Server 2008 SP4 (or the latest service pack from Microsoft)

SQL Server 2008 R2 SP3 (or the latest service pack from Microsoft)

SQL Server 2012 SP2 (or the latest service pack from Microsoft)

SQL Server 2014 (or the latest service pack from Microsoft)

For very small networks and evaluation environments, SQL Server 2008 R2 Express SP 2 (packaged in the TRITON Unified Installer).

(Microsoft SQL Server Standard and Enterprise) Use the Windows Services tool on the SQL Server machine to verify that the SQL Server Agent service is running.

Use SQL Server Management Studio to make sure the ETL job is running. If it isn't, check for errors in the job history and restart or manually run the job.

Use the following procedures:

Make sure Filtering Service is sending data

Look for problems on the Log Server machine

You can also use the TestLogServer utility to verify logging behavior. See Using TestLogServer for Troubleshooting.

Troubleshooting > Log Server and Log Database issues > Last successful ETL job ran more than 4 hours ago