Overview

After a certain date, the ETL jobs have started taking a much longer time to run. The following query, in particular, has been noticed as long-running by your database administration team:

• UPDATE jivedw_activity_fact SET day_id = ( SELECT day_id FROM jivedw_day WHERE activity_ts BETWEEN begin_ts AND end_ts ) WHERE day_id != ( SELECT day_id FROM jivedw_day WHERE activity_ts BETWEEN begin_ts AND end_ts )

This article provides more information on a possible cause of this issue.

Environment

Jive On-Premise.

Information

This issue can appear after an upgrade has taken place, as there are tasks that may take a long time to run in that scenario.

If no upgrade has taken place recently, or the ETL jobs continue to take a much longer time to run after several days have passed, please contact us so that ATLAS can assist you. If you are not satisfied with the solution provided by ATLAS, then it will create a ticket for you on which you can attach the web server SBS logs (located in /usr/local/jive/var/logs).