Re: Moving Oracle 8i DB from /abc to /def

Steve N. <steven_nospam_at_yahoo.ca> schreef in berichtnieuws a7f2ae7e.0308041012.53b1dd80_at_posting.google.com...
| Hi All,
|
| I have an Oracle 8.1.6 (Enterprise Ed.) database that has a UNIX
| datafile-based configuration. Its laid out in a directory structure
| that starts with /live. I want to take a copy of that database and
| place it in /save. We are not using RMAN.
|
| At present, we know of two ways to do this:
|
| 1) Export all the data, then import it into another database.
|
| 2) Use exp with TRANSPORT_TABLESPACE, copy all the files into the new
| directory, then imp the metadata.
|
| Both of these are very time consuming. I was wondering if there was a
| way to shutdown the database, simply copy all the data files to the
| new directory, then somehow tell the control file to find the data
| files in the new directory instead of where they were previously.
|
| Does anyone know how this might be done? I've had to recover from a
| lost controlfile before so I know we can recreate that using trace
| files, so I was thinking it may be possible to alter the file paths so
| that it finds the new files in the new location in the process...
|
| Thanks in advance for any ideas...
|
| Regards,
|
| SteveN.

In addition to the other posters. When you clone the database as described by the others you *must* give the database a new name (db_name), assuming it wil run in the same $ORACLE_HOME. Otherwise you will get problems with the lkSID file with the result that the original and the clone can't run at the same time. I'am afraid this is not sufficiently clear from the other posts. You must use "create controlfile SET database <newname> .....". In advance add this new sid to oratab file and prepare an init.ora file. When you copy it from the original init.ora don't forget to change the control_files parameter. If you forget it, it will overwrite the controlfiles of the original db, making it to crash. Just to warn you..... You don't use RMAN don't you? Because you will not be able to register the clone db in the same catalog because the DBID did not change. There is an (undocumented) solution for this too: dbms_backup_restore.zerodbid. Received on Mon Aug 04 2003 - 15:21:34 CDT