Re: What use is OCP? they did it again!

Apart from the ambiguity of B, and the fact that the bitmap is not 64K, (it is 64K less 2 blocks), and the ambiguity of C pointed out by Niall, you should also note that E is wrong.

If you allocate an extent, then you don't seem to generate UNDO for the change to the BIT, but you generate UNDO for the file space header block (the block before the bitmap) and for the update to the extent map of the segment that is acquiring the extent, and for the update to the obj$ table as the mtime is updated, and for the changes to tsq$ if you have tablespace quotas in place.

--
Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

Next Seminar dates:
(see http://www.jlcomp.demon.co.uk/seminar.html )

____England______January 21/23


The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html





mario wrote in message ...


>From the last issue (November/December 2002) of

>Oracle Magazine, page 134:

>

>" Select two characteristics of locally managed tablespaces:

>

>A. extents are managed by the data dictionary.

>

>B. a bitmap in the datafile keeps track of the free

>   or used status of blocks (sic!) in the datafile.

>

>C. Each segment stored in the tablespace can have a

>   different storage clause.

>

>D. no coalescing is required.

>

>E. UNDO is not generated when allocation or

>   deallocation of extents occurs.

>

>For locally managed tablespaces, the correct answers

>are B (sic!), D and E. "

>

>Each bit in the 64K bitmap corresponds to one extent in the file,

>and not, as stated, a single block.

>

>

>Mario from Rome