Go to the table of contents Go to the previous page Go to the next page View or print as PDF
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 | Forcepoint Web Security and Forcepoint URL Filtering | v8.5.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.
*
*
*
*
See this article for a full list of certified versions.
*
(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.
*
*
*
*
You can also use the TestLogServer utility to verify logging behavior. See Using TestLogServer for Troubleshooting.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Troubleshooting > Log Server and Log Database issues > Last successful ETL job ran more than 4 hours ago
Copyright 2018 Forcepoint. All rights reserved.