From: "Billy Verreynne" Newsgroups: comp.databases.oracle.server Subject: Re: Copy database in Oracle 8.1.6 Date: Wed, 8 Aug 2001 14:23:18 +0200 Organization: The South African Internet Exchange Lines: 33 Message-ID: <9krb7c$5un$1@ctb-nnrp1.saix.net> References: <9kotu3$ulm$1@sunce.iskon.hr> <2a676b39.0108070918.3fbee6ee@posting.google.com> <9kr8o8$64v$1@sunce.iskon.hr> NNTP-Posting-Host: 198.54.202.209 X-Trace: ctb-nnrp1.saix.net 997273644 6103 198.54.202.209 (8 Aug 2001 12:27:24 GMT) X-Complaints-To: abuse@saix.net NNTP-Posting-Date: 8 Aug 2001 12:27:24 GMT 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 "Hinet News" wrote > What about talbespaces ? If I run full database export, are they included > too, or not ? Yes and no. Yes, the tablespace and storage clauses are included to be used for re-creating the objects (indexes, tables, etc) on the new database. No, the import will not recreate the tablespace for you. To import, you need a database already created and configured. If you want to copy the _physical_ database across, then you need a physical backup of the complete database. If you have the same file system layout on the other (destination) machine, no problems. Do the restore and start up the database. Should be as simple as that. You will need to change the IP address/hostname in the listener.ora file though. If the file systems are different, then you will need to recreate the control file(s) on the destination machine. Dump the control file to trace on the source machine. Do not restore the control files on the destination machine (restore everything else). Edit the control file recreation script to point to the restored files on new filesystems and run that via server manager on the destination machine. -- Billy