Re: Blocker did not identified

From: Jure Bratina <jure.bratina_at_gmail.com>
Date: Sun, 31 Dec 2017 15:57:58 +0100
Message-ID: <CAC08BHJwyFgDg8UD1eKeFqNsd3WsLuqpMAzYH6ZyfR_-vcm12g_at_mail.gmail.com>



Eriovaldo,

If you haven't done so already, maybe it's worth checking the BLOCKING_* columns of DBA_HIST_ACTIVE_SESS_HISTORY for the problematic period.

Regards,
Jure

On Sat, Dec 30, 2017 at 4:07 AM, Eriovaldo Andrietta <ecandrietta_at_gmail.com> 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:
>
> SELECT ID FROM TABLE_BLA
> 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.
>
> Regards
> Eriovaldo
>
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Sun Dec 31 2017 - 15:57:58 CET

Original text of this message