Re: hot backup mode question

Don't forget - you can't do an 'alter tablespace' on a locally managed temporary tablespace :-)

By locally managed temporary tablespace I mean tablespaces created like this :
'create temporary tablespace <x> extent management local uniform size <y>M tempfile 'z' size <a>M;'
and NOT

'create tablespace <x> extent management local uniform size <y>M datafile
'z' size <a>M;'
'alter tablespace <x> temporary;'

"Jim Kennedy" <kennedy-family_at_attbi.com> wrote in message news:_oAO7.3297$TZ1.1460_at_rwcrnsc51...
> Yes, you need to do this before you backup each tablespace. Also remember
> to take them out of backup mode once you have backed one up. Preferred
> method is to do each tablespace one at a time.
> Jim
> "Tom Hoffmann" <tom.hoffmann_at_worldnet.att.net> wrote in message
> news:Xns916BCB59D583Ftomhoffmannworldneta_at_204.127.36.1...
> > I am an SA by trade who must now learn the trade of DBA. In reading the
> > Oracle documentation on 'hot backup' mode, it states that tablespaces
> > must be placed in 'hot backup' mode with a:
> >
> > alter tablespace <tablespacename> begin backup;
> >
> > statement before being backed up. But is this the case for all
> > tablespaces? It seems obvious [to me] that the data and index
> > tablespaces should be, it is not so obvious that the tools, temp, rbs,
> > and user tablespaces must be. Must I execute an 'alter tablespace ...'
> > on these tablespaces also before backing them up in 'hot backup' mode?
>
>
Received on Mon Dec 03 2001 - 11:55:35 CST