Re: Blocker did not identified

From: Dominic Brooks <>
Date: Sat, 30 Dec 2017 11:22:15 +0000
Message-ID: <HE1P190MB0250EF8B214B0F946E217DB9A11A0_at_HE1P190MB0250.EURP190.PROD.OUTLOOK.COM>

Also... technically it’s transactions not sessions which hold locks. In some niche circumstances, that can make a difference in how to identify.

Sent from my iPhone

On 30 Dec 2017, at 11:02, Niall Litchfield <<>> wrote:

Is this a RAC database? You'll need to look also at the instance and blocking_status columns in v$session to rely on the blocking_session column in v$session.<> IIRC EM12c also is not RAC aware in its blocking sessions page.

On Sat, Dec 30, 2017 at 3:07 AM, Eriovaldo Andrietta <<>> wrote: ​​​Hello,

I got an issue related to lock.
Now the daabase was re-started and the issue is solved. But during investigation I did not get sucess to identify who were locking a table.

A table is used like this:

where id = :1
for upate;

The query did not return the result and looking for lock using this query :

 select s.sid, s.blocking_session, do.object_name,

    row_wait_obj#, row_wait_file#, row_wait_block#, row_wait_row#,     dbms_rowid.rowid_create ( 1, ROW_WAIT_OBJ#, ROW_WAIT_FILE#, ROW_WAIT_BLOCK#, ROW_WAIT_ROW# )     from v$session s, dba_objects do
    where s.ROW_WAIT_OBJ# = do.OBJECT_ID

I saw the row_wait_obj#, ROW_WAIT_FILE#, ROW_WAIT_BLOCK# and ROW_WAIT_ROW# values.

In this situation how can I find the blocker? or
I used a lot of queries that show blocker and locked but without sucess to see the blocker.



Niall Litchfield
Oracle DBA<>
-- Received on Sat Dec 30 2017 - 12:22:15 CET

Original text of this message