Re: locally managed tablespace & dictionary managed tablespace

"Howard J. Rogers" <howardjr2000_at_yahoo.com.au> wrote in message news:<BbQP9.12506$jM5.34484_at_newsfeeds.bigpond.com>...
> You don't have to worry
> about the number of extents acquired by a segment, so you don't have to sit
> there for a week worrying about whether you should go for 64K extents or 64M
> ones. If you pick 64K ones, and the table goes beserk acquiring thousands of
> extents as a result, who cares? LMTs certainly don't.

All the rest of the post was excellent, but there's a bit of a nit-pick with the above. See metalink Note:61997.1.

Basically, SMON can spin the heck out of your CPU's when coalescing. Not normally a problem, but can be a bit of a mess when you can't shutdown, or shutdown abort and then can't come up... just be aware, as the rest of the post illustrated, _some_ thought must be put into the defaults.

For those with metalink access, this is pretty handy (if it works):

http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=131854.1

jg

--
@home is bogus.
For a good time, chmod 222 /etc/passwd; finger; whoami