Troubleshooting
Problem
In Sterling MCF - How to avoid long running getPendingJobs queries fired by health monitor?
Symptom
Health Monitor fires select queries to collect the pending job statistics of a monitor. Sometimes these queries take a long time depending on the data in the table.
For
example, the following query is fired by Health Monitor while
monitoring Shipment Monitor Agent. This will take long time if there are many
records in YFS_SHIPMENT table.
2008-06-10 17:05:17,486:DEBUG
:Timer-8: WhereClause For getting Shipments For monitoring WHERE ( (
YFS_SHIPMENT.SHIPMENT_CLOSED_FLAG <> 'Y' ) AND ( YFS_SHIPMENT.DOCUMENT_TYPE =
'0006' ) AND ( YFS_SHIPMENT.NEXT_ALERT_TS <= '20080610170517' ) ) </em>:
YDMShipmentMonitor</span>
Resolving The Problem
To avoid this long running queries set 'CollectPendingJobs' parameter as 'N' in Agent configuration
The number of pending tasks of every agent is recorded during every
persist interval. This pending job information is used for monitoring the
agent. All Business Process Time-Triggered Transactions have a
CollectPendingJobs criteria parameter. If this parameter is set to N, the agent
does not collect information on the pending jobs for that time-triggered
transaction. It can be helpful to set it to N if one particular time-triggered
transaction is performing a significant amount of getPendingJobs queries, and
the overhead cost is too high
For more information please
refer to Platform configuration guide; section ‘Business Process
Time-Triggered Transactions.’
[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Historical Number
NFX3963
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21555708