Tidal scheduler stops updating Last Run times in AAI jaws.log shows long running query on TidalDbMessageLog

book

Article ID: 209193

calendar_today

Updated On:

Products

Automic Automation Intelligence

Issue/Introduction

Tidal scheduler stops updating Last Run times in AAI.

The jaws.log shows repetitive messages about a long running query against the Tidal database like below:

100.0%: 1x (avg. time: 1:00.009) query: from TidalDbMessageLog where jobRunId in (:jobRunIds) order by creationDate, id

Environment

Release : 6.0.1

Component : AUTOMIC AUTOMATION INTELLIGENCE ENGINE

Resolution

This likely indicates there are some performance issues on the Tidal Database server, or other database related issues on the Tidaly Database side.

 

To work around this you can restart the AAI service and all the service to come back up, and monitor the jaws.log for reoccurrence of this long running query. 

 

You can verify the system is catching up by looking at the "Last Run Processed" time to see if it is updating over time on the Admin->Schedulers window of the AAI Client.

Attachments