SMQR - qRFC Monitor: Qin Scheduler status error: Ressource Error

[Former Member]

Hi all,

We have a problem with the PI inbound queue and hope you can advice in this.

When I send eg. an MATMAS-IDoc from the ECC-backend to the PI 7.3 (dual stack), the message gets stuck in the inbound Queue of PI. In other words, it is not processed automatically from there. I can unlock the message manually from SMQ2, and then it is processed correctly conform the created PI scenario.

If I check SMQR, it shows the following error (With double 's' !!!):

Scheduler Status : RESSOURCE ERROR

Then I check the Resource of the particular Server Group, by going to: -> Goto -> QRFC Resources, it says:

<xxxxxx>_P01_00 1 1 Not OK

I have also already checked the AS group using RZ12, and there is the status 'OK' (green).

Can anyone help out in this please?

Thank you, Walter.

[Former Member · Accepted solution]

Hello,

Could you check if there are enough DIA work processes in SM50?

Has the number of DIA processes been reduced?

You could also check SAP notes 74141 & 527481

Kind regards,

Sarah

[Former Member · Accepted solution]

Hello Sarah,

Thanks for your input, that could be the cause.

I checked with tr.cod. SARFC and it showed the message: 'Too few free dialog work processes'.

It is a Demo environment, hardly used until now and recently updated to 7.3, and there where only 2 active dialog work processes configured.

In the document u2018PI Performance Checku2019 I read:

As a rule of thumb for the initial configuration, the number of DIA work processes

should be around six times the value of CPU in your PI system (rdisp/wp_no_dia =

6*#CPUs + 10 based on SAP Note 1375656 - SAP Netweaver PI System Parameters ).

Does that mean there should be at least 16 DIA processes configured?

Our Basisteam will increase the number (I think it will be 6 for now) and restart it after business hours.

Thank you, Walter.

[Former Member · Accepted solution]

Hi Walter,

Yes there should be minimum 16.

Hopefully there will be an improvement once you increase the number of processes.

Kind regards,

Sarah

[Former Member · Accepted solution]

Hi Sarah,

Now it's working again!

The error has gone and messages are processed automatically again.

Thank you again, Walter.