Re: archivelog leads to crashes...?

"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message news:4056e5d6$0$3304$ed9e5944_at_reading.news.pipex.net...
> "Howard J. Rogers" <hjr_at_dizwell.com> wrote in message
> news:4056c3d0$0$27384$afc38c87_at_news.optusnet.com.au...
> >
> > They were just thinking ahead, Niall. With 10g being self-managing,
> there's
> > *got* to be something for the junior DBA to be doing, otherwise it just
> gets
> > embarrassing. There is only so much photocopying that one can do!!
>
> :(
>
> > It is an odd one, though, isn't it. I would have thought that there
would
> be
> > a set-one-thing-and-do-it-all option for such a key piece of database
> > functionality by now. I imagine this is a classic example of 'it's
always
> be
> > done this way' and a commensurate 'unable to think outside the box'
> > mentality. It's easily done. I still remember the sense of shock when I
> > first realised you couldn't create data dictionary managed tablespace in
> > 9iR2 anymore!
>
> I sort of know what you mean but consider this on a non-upgraded database
>
> SQL> show release
> release 902000400
> SQL> create tablespace not_dead_yet
> 2 datafile 'c:\oracle\oradata\nl9204\not_dead_yet.dbf' size 50m
> 3 extent management dictionary;
>
> Tablespace created.
>
> The same requirement (that you have a dictionary managed system
tablespace)
> applies but it is still perfectly possible - as opposed to desirable. Of
> course if you just click your way through dbca and have it create the db
for
> you probably you won't meet this requirement. I'm also sure you know this
> but sooner or later someone will quote you as saying that you can't have
> dictionary managed tablespaces from 9.2 onwards.

I know. I should have mentioned the system=lmt constraint, or added the words "read write".

OK, how's this one then, along the same lines of being gobsmacked at change to old friends: shared_pool_size is an underscore parameter in 10g!!

Regards
HJR Received on Tue Mar 16 2004 - 05:43:44 CST