Queues stay in status READY in SMQ2
If you observe a situation where many queues are in READY status, the following
situations can apply:
1. A resource bottleneck with regard to RFC resources. Confirm with transaction
SARFC.
2. Long DB loading times for RFC tables. If using Oracle, ensure that SAP Note
1020260 - Delivery of Oracle statistics is applied.
3. To avoid overloading a system with RFC load, the QIN scheduler only reloads
LUWs from the queues after a certain amount of DIA WPs have finished their
work. This can lead to long waiting times in the queues as explained in SAP Note
1115861 - Behaviour of Inbound Scheduler after Resource Bottleneck. Since PI is
a non-user system, we recommend setting rfc/inb_sched_resource_threshold to 3.
4. Additional overhead during this step occurs due to every message being blocked
during processing. This is no longer necessary and should be switched off by
setting the parameter LOCK_MESSAGE of category RUNTIME to 0 as per SAP Note 1058915.
If you observe a situation where many queues are in READY status, the following
situations can apply:
1. A resource bottleneck with regard to RFC resources. Confirm with transaction
SARFC.
2. Long DB loading times for RFC tables. If using Oracle, ensure that SAP Note
1020260 - Delivery of Oracle statistics is applied.
3. To avoid overloading a system with RFC load, the QIN scheduler only reloads
LUWs from the queues after a certain amount of DIA WPs have finished their
work. This can lead to long waiting times in the queues as explained in SAP Note
1115861 - Behaviour of Inbound Scheduler after Resource Bottleneck. Since PI is
a non-user system, we recommend setting rfc/inb_sched_resource_threshold to 3.
4. Additional overhead during this step occurs due to every message being blocked
during processing. This is no longer necessary and should be switched off by
setting the parameter LOCK_MESSAGE of category RUNTIME to 0 as per SAP Note 1058915.
