Re: Row Locking on Oracle 8

Karen Abgarian wrote:

> I admit I missed row_wait_row#. But it is only ONE rowid. What about others?

Well, a waiter gets hung up on the first row it encounters that is locked. Since that is only one row, Oracle's internal structures are designed only to provide a row at a time as the row_wait_row# in
v$session.
--
Jeremiah

> Jeremiah Wilton wrote:
>
> > Karen Abgarian wrote:
> >
> > > You cannot get the information about the locked rows from v$ tables, because
> > > it's not there. The locking information is stored in the database along with
> > > rows.
> >
> > If someone is really being blocked, the row number is in
> > v$session(row_wait_row#) for the session being blocked. The blocker is
> > available from v$lock by joining the waiter's v$session(taddr) with
> > v$transaction(addr). So if there is a real blocking situation, you can get all
> > the information mentioned in the original message. You can make Oracle8 rowids
> > out of this data with the dbms_rowid built in package.
> > --
> > Jeremiah
> >
> > >
> > > Juan Carlos Alonso Lafuente wrote:
> > >
> > > > The question is that we would like to know who is blocking one row in a
> > > > table and which particular row (its rowid).
> > > >
> > > > Using v$session and v$lock we get to know who is blocking a particular
> > > > object (a table) but we do not know the row being blocked.
Received on Sat Sep 18 1999 - 17:55:53 CDT