| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> c.d.o.server -> Re: how to test locks
If you have access to Metalink, there is a good faq on locking.
Go to the Advanced Search and put this in the search field:
Note:15476.1
and click on the "Doc ID" thingy.
mngong_at_yahoo.com (michael ngong) wrote in message news:<ecf365d5.0201231046.542aef6c_at_posting.google.com>...
> "Stephen B" <stephen.bell_at_cgi.ca> wrote in message news:<Coz38.13816$KC1.2314744_at_news20.bellglobal.com>...
> day:> > > block may contain invalid information and be scheduled for "delayed
> > > you find the database block for that record (rowid contains file and block
> > > id), dump the block from oradebug and see whether the row header contains
> > > the pointer to a valid ITL in that block. The very first byte of the row
> > > header is the offset into the ITL table. ITLs are 23 bytes in size and
> > > contain a XID of the transaction that is interested in the block. After
> > > you do that, ask yourself whether the obtained information was worth the
> > > trouble. Oh yes, and exact descriptions on the database blocks can be
> > > obtained only in the Scott Gosset's "top gun" class.
> > > Oh, did I forget to mention that you have to check whether the block is in
> > > SGA (v$bh) and if it is, then you have to look there. ITLs in the disk
> > Could we make our answers a little bit clear and simpler for > those who may really need our help.? > ThanksReceived on Wed Jan 23 2002 - 17:01:35 CST
![]() |
![]() |