IBM Support

Queries on YFS_SHIPMENT even after setting ‘Collect Pending Jobs = N’ for SHIPMENT_MONITOR agent.

Troubleshooting


Problem

Queries on YFS_SHIPMENT even after setting ‘Collect Pending Jobs = N’ for SHIPMENT_MONITOR agent.

Symptom

Queries on YFS_SHIPMENT even after setting ‘Collect Pending Jobs = N’ for SHIPMENT_MONITOR agent.
Error Message
Queries on YFS_SHIPMENT even after setting ‘Collect Pending Jobs = N’ for SHIPMENT_MONITOR agent.
Similar behavior is observed for other agents as well.

Resolving The Problem

In the AWR or at DB level, it is not clear what is the exact query that the application fires.
The only details obtained are as below:
SELECT /*YANTRA*/ count(:"SYS_B_0") from YFS_SHIPMENT WHERE ( ( YFS_SHIPMENT.SHIPMENT_CLOSED_FLAG <> :"SYS_B_1" ) AND ( YFS_SHIPMENT.DOCUMENT_TYPE = :"SYS_B_2" ) AND ( YFS_SHIPMENT.NEXT_ALERT_TS <= :"SYS_B_3" ) )</span></div> <div> </div> <div>
By making “Collect Pending Jobs = N" on any transaction, HealthMonitor will not fire any queries to collect stats for that transaction.
For the above scenario, the application queries for SHIPMENT_MONITOR, SHIPMENT_MONITOR.003, SHIPMENT_MONITOR.005 and SHIPMENT_MONITOR.006 transactions with specific DOCUMENT_TYPE.
If one sees the same query even after setting ‘Collect Pending Jobs = N’ on one agent, there is a possibility that a similar agent exists for other document types.
Therefore, one needs to set ‘Collect Pending Jobs = N’ on all relevant agents to avoid the problem.

[{"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

NFX8000

Product Synonym

[<p><b>]Severity[</b><p>];Normal;[<p><b>]Type[</b><p>];NormalFix

Document Information

Modified date:
16 June 2018

UID

swg21558207