Failed Query messages for ujo_batch_move_event - should we adjust dblibwaittime
Article ID: 213928
Updated On:
Products
Issue/Introduction
We have an AutoSys instance that is experiencing Failed Query messages on function ujo_batch_move_event.
This leads to an extreme degradation of performance.
The ujo_batch_move_event code, it moves events from ujo_event table to ujo_proc_event table.
When the Failed Query message occurs for ujo_batch_move_event, it is actually the event_demon timing out waiting for ujo_batch_move_event to complete, and then the event_demon submits a second occurrence of ujo_batch_move_event which contends with the first occurrence, causing the second occurrence to also time out and then a third, fourth, etc. etc. occurrences are submitted leading to no good.
Environment
Release : 11.3.6
Component : CA Workload Automation AE (AutoSys)
Resolution
Adjusted DBLibWaitTime to a higher value and restart the scheduler and the problem has not been seen since.
Factors such as the size of the tables and database performance may also be factors.
See DBMaint for details regarding the table sizes.
And work with the DBA to review items like explain plans and Oracle AWR reports as needed.
Feedback
