From: "Howard J. Rogers" <howardjr@www.com>
Newsgroups: comp.databases.oracle.server
References: <3af3108a$0$27218@reader4> <3af360d6@news.iprimus.com.au> <3AF3A020.5C4F4D0D@home.com> <3af3e580@news.iprimus.com.au> <3AF42AA1.68555258@home.com>
Subject: Re: alter rollback segment
Lines: 63
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Original-NNTP-Posting-Host: 203.134.155.11
Message-ID: <3af434b5@news.iprimus.com.au>
X-Original-Trace: 6 May 2001 03:13:25 +1000, 203.134.155.11
Date: Sun, 6 May 2001 03:13:22 +1000
NNTP-Posting-Host: 203.134.64.67
X-Trace: news0.optus.net.au 989082805 203.134.64.67 (Sun, 06 May 2001 03:13:25 EST)
NNTP-Posting-Date: Sun, 06 May 2001 03:13:25 EST
Organization: CWO Customer - reports relating to abuse should be sent to abuse@cwo.net.au



"Paul Drake" <paled@home.com> wrote in message
news:3AF42AA1.68555258@home.com...
> "Howard J. Rogers" wrote: (some content removed)
> >
> > Hi Paul,
> >
> > No real gotchas that I can think of, except that you have to use the
> > 'uniform size' version, not the autoallocate (anecdotally, anyway -I've
> > never bothered wth autoallocate in the first place, so I've never
 tried).
> >
> > There is only one nasty with LM Rollback tablespace: you can't create
 the
> > first rollback segment in it unless there is one non-system dictionary
> > managed rollback segment (because creating that first one requires you
 to do
> > DML on the bitmap at the header of the tablespace -and that's DML on a
> > non-system tablespace, and hence if all you've got is the system
 rollback
> > segment, you'll get that infamous ORA error to the effect that 'you
 can't
> > use system rollback segment for updates in non-system tablespace'). So,
 you
> > need to create one small rollback segment first in boring old dictionary
> > tablespace (the SYSTEM tablespace will do fine -the fact that a rollback
> > segment is housed in SYSTEM doesn't make it the system rollback
 segment).
> > Once that is brought online, *then* you can create your first rollback
> > segment in a locally managed tablespace.  And once *that's* created and
> > brought online, you can drop the temporary, dictionary-managed one,
 because
> > now you *do* have a non-system rollback segment to handle all subsequent
> > updates to the tablespace's bitmap.
> >
> > Regards
> > HJR
>
> Howard,
>
> Thanks much for the detailed info.
> I upgraded the DEV server last night from 8.1.6.3.4 to 8.1.7.1.2 (on NT)
> - so once my exports and backups are finished, I'll give it a go.
>
> In seeing a demo of LogMiner - I'd like to reduce as much as possible
> the recursive SQL to uet$ and fet$ (and others). It would be nice to
> have SYSTEM as the only non-LMT.
>

Absolutely, and that's one biggie plus in favour of LMT, of course.  Good
luck.  Let me know how it goes (or if it doesn't!)

Regards
HJR




> thanks again.
>
> Paul