Re: Creating a controlfile - language needed?

There are several alternatives for moving databases. The method chosen will depend on several factors:

• Amount of downtime allowed.
• Size of the database.
• Whether the two servers are compatible.
• Level of DBA experience. Stick to your comfort zone.
• Don't forget to perform the chosen method in test first. In my opinion, the simplest method is to create a controlfile to trace, edit it, etc. This is good if you are inexperienced at these methods and there is plenty of downtime available. There are several documents on the web that describe this process, for example: http://www.jlcomp.demon.co.uk/faq/db_move.html.

Dennis Williams

On 10/4/05, Mark Bole <makbo_at_pacbell.net> wrote:
> Goulet, Dick wrote:
>
> > Depends. Was the database shutdown cleanly before you rebuilt the
> > control file? If not then you need it.
>
> Not exactly. If instance recovery is required, it is the online redo
> log files that you will need, not the original control file.
>
> >
> > I am copying a database to a new server and all of the 200+ files will
> > have
> > a new directory structure (but will keep the same SID) so that is why I
> > am
> > creating a new controlfile.
> >
>
> Why create a new controlfile and open resetlogs when you don't need to?
> Shutdown the database, copy all the files to the new locations,
> startup nomount, then use a series of ALTER DATABASE RENAME FILE
> commands to update the location of datafiles and online log files. Then
> create/drop tempfiles as appropriate. You still have to do the same
> amount of text file editing in either case.
>
> In fact, you might even get away with simply using DB_FILE_NAME_CONVERT
> and LOG_FILE_NAME_CONVERT parameters.
>
> --
> Mark Bole
> http://www.bincomputing.com
>
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>

--
http://www.freelists.org/webpage/oracle-l