Message-Id: <10583.114097@fatcity.com> From: "Koivu, Lisa" Date: Tue, 8 Aug 2000 13:00:50 -0400 Subject: RE: locking issues This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0015A.36D06D8C Content-Type: text/plain; charset="iso-8859-1" WHAT? "whenever any row that the bitmap points to is locked" Do you mean that an entire table ends up being locked if I am updating one row and there is a bitmap index on it? -----Original Message----- From: Toepke, Kevin M [mailto:ktoepke@cms.cendant.com] Sent: Tuesday, August 08, 2000 1:37 PM To: Multiple recipients of list ORACLE-L Subject: RE: locking issues Yes. Bitmap indexes are locked whenever any row that the bitmap points to is locked -- which could mean 1000s of rows are locked whenever 1 row is updated! And, yes. This was part of the original problem. When we dropped the bitmap index, we still got deadlocking -- until I rewrote the code to clean up the logic. Kevin > -----Original Message----- > From: Jamadagni, Rajendra [mailto:rajendra.jamadagni@espn.com] > Sent: Tuesday, August 08, 2000 12:33 PM > To: Multiple recipients of list ORACLE-L > Subject: RE: locking issues > > > Isn't it true that Bitmap indexes lock more than necessary > rows ? I mean if > you are updating only one row, when bitmap index gets > updated, it locks all > the rows that are in the same (index) data block. Could this > be one of the > problem? > > I may be wrong, but I know someone will correct me on this ... > > Cheers > Raj > ______________________________________________________ > Rajendra Jamadagni MIS, ESPN Inc. > Rajendra dot Jamadagni at ESPN dot com > QOTD: Any clod can have facts, but having an opinion is an art ! > Any opinion expressed here is personal and doesn't reflect > that of ESPN Inc. > > -- > Author: Jamadagni, Rajendra > INET: rajendra.jamadagni@espn.com > > Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 > San Diego, California -- Public Internet access / Mailing Lists > -------------------------------------------------------------------- > To REMOVE yourself from this mailing list, send an E-Mail message > to: ListGuru@fatcity.com (note EXACT spelling of 'ListGuru') and in > the message BODY, include a line containing: UNSUB ORACLE-L > (or the name of mailing list you want to be removed from). You may > also send the HELP command for other information (like subscribing). > -- Author: Toepke, Kevin M INET: ktoepke@cms.cendant.com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru@fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). ------_=_NextPart_001_01C0015A.36D06D8C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: locking issues

WHAT? 

"whenever any row that the bitmap points to is = locked"

Do you mean that an entire table ends up being locked = if I am updating one row and there is a bitmap index on it?

-----Original Message-----
From: Toepke, Kevin M [mailto:ktoepke@cms.cendant.com]
Sent: Tuesday, August 08, 2000 1:37 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: locking issues


Yes. Bitmap indexes are locked whenever any row that = the bitmap points to is
locked -- which could mean 1000s of rows are locked = whenever 1 row is
updated!

And, yes. This was part of the original problem. When = we dropped the bitmap
index, we still got deadlocking -- until I rewrote = the code to clean up the
logic.

Kevin

> -----Original Message-----
> From: Jamadagni, Rajendra [mailto:rajendra.jamadagni@es= pn.com]
> Sent: Tuesday, August 08, 2000 12:33 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: locking issues
>
>
> Isn't it true that Bitmap indexes lock more = than necessary
> rows ? I mean if
> you are updating only one row, when bitmap = index gets
> updated, it locks all
> the rows that are in the same (index) data = block. Could this
> be one of the
> problem?
>
> I may be wrong, but I know someone will correct = me on this ...
>
> Cheers
> Raj
> = ______________________________________________________
> Rajendra Jamadagni    =         MIS, ESPN Inc.
> Rajendra dot Jamadagni at ESPN dot com
> QOTD: Any clod can have facts, but having an = opinion is an art !
> Any opinion expressed here is personal and = doesn't reflect
> that of ESPN Inc.
>
> --
> Author: Jamadagni, Rajendra
>   INET: = rajendra.jamadagni@espn.com
>
> Fat City Network Services    -- = (858) 538-5051  FAX: (858) 538-5051
> San Diego, = California        -- Public Internet = access / Mailing Lists
> = --------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send = an E-Mail message
> to: ListGuru@fatcity.com (note EXACT spelling = of 'ListGuru') and in
> the message BODY, include a line containing: = UNSUB ORACLE-L
> (or the name of mailing list you want to be = removed from).  You may
> also send the HELP command for other = information (like subscribing).
>
--
Author: Toepke, Kevin M
  INET: ktoepke@cms.cendant.com

Fat City Network Services    -- (858) = 538-5051  FAX: (858) 538-5051
San Diego, = California        -- Public Internet = access / Mailing Lists
---------------------------------------------------------------= -----
To REMOVE yourself from this mailing list, send an = E-Mail message
to: ListGuru@fatcity.com (note EXACT spelling of = 'ListGuru') and in
the message BODY, include a line containing: UNSUB = ORACLE-L
(or the name of mailing list you want to be removed =