SAP Note 23754 - Exclusive lockwaits for table display SE16

Symptom:

If several users in the SAP system want to display the contents of a table (for example BSEG) via transaction SE16, exclusive lockwaits can occur on table D010LINF, with the result that one user has to wait for another. This can also occur if two users want to display different tables at the same time.

Cause and prerequisites

When you execute transaction SE16, an update lock is set up in table D010LINF on the generic ABAP/4 programs 'RSLOCK01', 'RSLOCK02' and so on. Due to an index access to table D010LINF that is not fully classified when executing transaction SE16, wait situations (exclusive lockwaits) can occur, so that one session must wait until the other one releases the update lock again.

Solution
Download the newest version of the script 'D010LINF.SH.23754' from sapservX.

This script is stored on sapservX in the directory '/general/3rdparty/informix/ddic', with the name 'D010LINF.SH.23754'.

Stop the R/3 System (stopsap r3) and execute the script; An informix specific index is created on table D010LINF.