Ansicht
Dokumentation

Lock entries are not displayed
Tip-No.: 1677 ( INFO1677 )

Short text

Lock entries are not displayed
Tip-No.: 1677

Symptom

Transaction SM12 does not display existing lock entires.

Cause

1) Configuration error
2) No WRITE permission on Enqueue-Backup-File
3) Operating system error, NFS timeouts, display hangs.

Solution

Lock entries are write for reporting purposes to the central Enqueue-
Backup-File and can be read there by external workstations via NFS
(Network File System) and displayed.
The Enqueue Backup-File ENQBCK is in the global directory. It is export-
ed by the NFS server and mount by the de-central workstations.
( Global-Directory in Unix: "/usr/sap//SYS/global")

Determine cause of error:
1) Enqueue-Server requires WRITE permission on the global directory
and on File ENQBCK
2) decentral workstations need READ permission
3) Check SysLog: the message "Connection Timeout" indicates NFS or
network problems or overloading of the NFS server.

Remedy error:
1) , 2) Get operating system administrator to set up permissions
correctly. Must then startup the Enqueue server.
3) NFS write accesses on Enqueue-Backup-File must be avoided by
positioning the Enqueue-Backup-File on a local disk of the
Enqueue server.
Use Hard mounts between Enqueue server and NFS server, if required.
Determine causes of network or server overloading and deal with them.
Startup Enqueue server again.