Warning about the parallel_max_servers parameter in ewa reports

[Former Member]

Hi gurus,

We produce ewa reports using our solution manager system. The health and performance of the systems are evaluated using these reports.

For all our sap systems, although the database parameter settings are configured correctly according to the oss note 830576, in the section 9.2, it gives warning for the parameter parallel_max_servers. We are almost sure that the value of the parameter parallel_max_servers is also set correctly. Whatever we did, we couldn't set it green.

Is there a way to turn it green, or as the sentence says in the report "If it is configured correctly, then ignore the yellow rating for this parameter." means that there is no way, although the parameter is set correctly, it will stay in yellow?

Best Regards,

Tolga

[Former Member · Accepted solution]

Hi,

The optimal value for PARALLEL_MAX_SERVERS depends on the CPU cores in the database server available for database ( total CPU cores on database server minus CPU requirements of other applications including SAP central instance). As the CPU requirements for all applications other

than database cannot be determined automatically by the EarlyWatch Alert tool, it doesnt have a reference value to compare the current setting and comment on it. The optimal setting has to be determined manually. If the PARALLEL_MAX_SERVERS is set correctly then please ignore the

alert generated in the EarlyWatch Alert report

Just because the rating is yellow in the report doesnt mean that the setting is incorrect. The report just tries to alert you that the optimal setting for this parameter could not be determined and asks

you to ensure it is set optimally.

Cheers!

[Former Member · Accepted solution]

Thanks alot for you reply.

Everthing is clear now.

[Former Member]

Hi.

What is your ST-SER component version?

Regards

[Former Member]

Hi,

ST_SER 700_2008_1 Support Package Level 5.

[Former Member]

Hm... it should be corrected then.

In an older version of ST-SER "# of CPUs * 8" (which is an old recommendation) was taken as correct value and therefor "# of CPUs * 10" was reported as warning.

But this has been fixed already.