Ansicht
Dokumentation

Requirements for enqueue handling
Tip-No.: 651 ( INFO651 )

Short text

Requirements for enqueue handling
Tip-No.: 651

Symptom

Exception SYSTEM-FAILURE when blocking

Cause

Misfunction of central enqueue handler or of the communication path to
the central enqueue handler.
Block table full.
Possible causes:
1) communication problems (network)
2) central message server
- not running, Executable msg_server or ms.sap
- outdated program version, made terminated because text file is busy
3) central enqueue server (usually also the updater)
- not started
- enqueue function parameterized incorrectly
( rdisp/myname =( VB_ )
rdisp/wp_no_enq = (>=1)
enque/process_location =REMOTE_TASKHANDLER or LOCAL

4) local application server
- falsch parametrisiert
rdisp/enqname =
rdisp/mshost =
enque/process_location =REMOTE_TASKHANDLER

5) Block table full

The syslog contains more information.
The parameterization of the central enqueue server and the local
application servers can be checked using Report RSPFPAR. SM12 contains
tips and a diagnosis function.

Solution

Enqueue text/diagnosis:
Transaction SM12 contains a self-diagnosis function for the block
management. SM12 -> jump -> diagnosis.
This determines and displays the most important error causes.
SM12 -> jump -> function notes displays a text that describes
the functionality of the block management in a distributed SAP
environment.

Transaction SM12 contains a text mode, which you activate with OK
code TEST and which offers a menu enhancement, "error handling".
Functions in "error handling":
- Long text for error situations
- Diagnosis of the parameterization,
availability of communications links and of the enqueue server
display sum statistic of previous enqueue operations
- turn on/off enqueue logging
- enqueue function can be completely turned on/shut off for emergency
operation
- test tools for enqueue operations below the function module level.

Limit causes of errors:
- examine the syslog in the dialog server and in the enqueue server
(the enqueue server name is displayed in SM12 -> diagnosis)
- error notes in DM12 -> error handling -> read error notes
- enqueue diagnosis in SM12 -> error handling -> execute diagnosis
- check enqueue in central enqueue server with SM12 OK code TEST
- check parameterization with Report RSPFPAR.

Emergency operation in local application server:
- shurt off enqueue completely with SM12 -> block -> turn off
- as soon as the central enqueue server can be reached again,
turn on the enqueue again with SM12 -> block -> turn on