Re: move datefiles (almost) online

Hi Hermann,

I would prefer to set only the file which is moved offline, because if you have
a tablespace with more than one file, you will get less errors. Don't forget to remove the old file (could take some time to free the space because it will be kept open by some shadow processes till they be terminated
or they try to use the file).

Regards
Ralph

"Hermann Schlösser" <hschloes_at_gmx.de> wrote in message news:3E614D30.8020103_at_gmx.de...
> Hi everybody,
>
> on 8.1.7 SE Solaris several datafiles (size 2-6GB)
> shall be moved to other disks for load balancing.
> System tablespace stays untouched.
>
> Though there are times of very low transactions
> NO DOWNTIME is available. Restart of the database
> would mean restart of several connected applicationservers.
>
> I testet this on an idle db (works fine) and would like
> to hear your opinions before going "live".
>
>
> > alter tablespace $TABLESPACE begin backup;
> > host cp -p $SOURCEFILE $TARGETFILE
> > alter tablespace $TABLESPACE end backup;
>
> (provides dirty copy of datafile in the disired place)
>
> > alter tablespace $TABLESPACE read only;
> > alter tablespace $TABLESPACE offline;
> > alter database rename file '$SOURCEFILE' to '$TARGETFILE';
> > alter database recover automatic datafile '$TARGETFILE';
> > alter tablespace $TABLESPACE online;
> > alter tablespace $TABLESPACE read write;
>
>
> Applicationservers should stay connected but will produce
> some errors during the (hopefully short) recovery time.
>
> Any ideas how to perform this task with less off-time?
>
> Thanks for your attention
> Hermann
>
Received on Sun Mar 02 2003 - 02:14:29 CST