When investigating a blocking lock, the blocking session SQL statement that triggers the "SQL Long Running Lock" alarms, is not displayed.
The pop-up window for SQL text shows "There Is No Data To Display".
For the blocked sessions, in every given time it will display the SQL statement that the blocked sessions is running (using SQL_ID column in V$SESSION) due to the fact that the sessions is locked, i.e. waiting for lock (e.g. enq: TX – row lock contention), therefore it is easy to retrieve the SQL statement that the blocked session is running.
However, for the blocker session, the SQL_ID that appears in the V$SESSION is not necessarily related to the lock. Reason could be, that the lock started already some seconds ago and other statements has been executed in between. If that statement will be displayed, it might look like that product is having a bug (displaying the wrong statement). Therefore it has been decided not to show the SQL statement the blockers session is running