Solution : https://service.sap.com/sap/support/notes/920234 (SAP Service marketplace login required)
Summary :
SAP systems may experience performance issues or complete standstills due to processes waiting for semaphore 8 in SM50, primarily associated with the "SAPSYS" user performing "DIRECT READ" on the NRIV table. Additional symptoms include exclusive database locks on the same table in DB01 and processes stuck in the "Stopped NUM" status in SM50, awaiting responses for number range buffer requests. This is caused by an overburdened system preventing the number range server from operating within 30 seconds, often due to DIA processes being overwhelmed by RFCs. To mitigate, adjustments on parameters such as rdisp/rfc_min_wait_dia_wp and nobuf/max_attempts are recommended, alongside ensuring an adequate number of DIA processes to reduce direct database access and enlarge the number range buffer contents.
Key words :
cli/obj/subobj/range = 400/bu_partner/ /zc, terms nriv semaphore 8 performance dp_hprio_timeout reason, /saphelp_nw70ehp1/helpdata/en/47/d5659d167e3c84e10000000a42189c/frameset, find exclusive database locks, specific number range object, symptom bad performance, htma typical reason, number range buffer, number range buffer, number range server
Related Notes :
| 1683036 | |
| 1545612 | Banking Serv. - System standstill due to number range buffer |
| 1445374 | Number range buffering for earmarked funds (IRW_BELEG) |
| 919785 |