Entering content frame

500: Lock request timeout Locate the document in its SAP Library structure

Explanation:

  1. The lock request or an implicit lock conflicts with the locks of another user. The maximum waiting time for granting the lock has elapsed (installation parameter REQUEST_TIMEOUT).
  2. SHUTDOWN could not be performed in a certain period of time (installation parameter LOCK_TIMEOUT) because transactions with SQL statements for data modification are still open. The serverdb has not been shut down.

User Action:

  1. In some cases, the error message contains a more detailed description of the error. The lock request can be reissued. To avoid possible deadlock situations, it is advisable to roll back the transaction using the <ROLLBACK statement>.
  2. Do without the SHUTDOWN or force a shutdown of the serverdb using the QUICK option.

 

 

 

Leaving content frame