Export and import Oracle 10G database

Question

Hello all
Can anyone tell me once for all how can i backup oracle 10G database and restore it in other computer (export and import)
thanks alot
Ron

Answer 1

Do you can access to metalink?
If not, I copy an paste this doc's....
Doc ID: Note:10767.1
Subject: How to perform FULL System Export/Imports
Type: BULLETIN
Status: PUBLISHED
Content Type: TEXT/X-HTML
Creation Date: 18-APR-1994
Last Revision Date: 30-AUG-2002
Purpose
This article highlights some important points to consider when performing
a Full System Export and Import.
Scope and Application
It is intended to assist users performing FULL System Exports and Imports.
A Full System Export and Import is a useful way to replicate or clean up
a database. Please note the following guidelines when performing a Full
System Export and Import:
1. When performing the import, ensure you are pointing at the correct
instance. Always check values for the SID and two task driver before
proceeding.
*Note:   On Unix systems, just entering a sub-shell, such as using
C-shell, can change the database that the import would work
against.
2. When possible, it is advisable to take a physical copy of the
exported database and the database you intend to import into before
starting the import. This ensures any mistakes are reversible.
3. NEVER run a FULL SYSTEM IMPORT on a machine that has more than one
database UNLESS you are 100% sure all tablespaces have been
pre-created. A full import will create any undefined tablespaces
using the same datafile names as the exported database. There are
situations where this is very dangerous:
-> If the datafiles belong to ANY other database, they will be
CORRUPTED. This is especially true if the exported database is
on the same machine, because its datafiles will be re-used by
the database you are importing into.
-> If the datafiles have names that clash with existing operating
system files.
4. When exporting, it is advisable to also produce a report showing
information you may need before / after the import:
-> List the tablespaces and datafiles
-> List the rollback segments
-> List a count, by user, of each object type such as tables,
indexes, etc.
This enables you to ensure that tablespaces have been pre-created
and to check the success of the import after it is complete.
5. If you are creating a completely new database from an export, remember
to create an extra rollback segment in SYSTEM, and make this available
in the init.ora file before proceeding with the import.
6. There are some versions of export that do not retain sequence numbers
correctly. It is advisable to select next_value for each sequence
after the export so that these can be checked after import.
Following these guidelines will help you to avoid major problems.
Doc ID: Note:174226.1
Subject: How To Copy an Oracle Database To Another Machine
Type: HOWTO
Status: PUBLISHED
Content Type: TEXT/X-HTML
Creation Date: 12-OCT-2001
Last Revision Date: 01-OCT-2003
goal: How to copy an Oracle database to another machine
fact: Oracle Server - Enterprise Edition
fix:
Pre-requisites: The copy is between 2 machines, both have to be on the same OS
and have to have exactly the same database version installed.
1. Make sure the database you want to copy was closed with a SHUTDOWN IMMEDIATE,
SHUTDOWN NORMAL or SHUTDOWN TRANSACTIONAL.
2. Copy init.ora and control files to create instance and be able to go in
mount mode. Check the init.ora for the locations where the controlfiles have
to be, if those locations are not valid on the machine put the control files on
different places and adjust the init.ora accordingly.
3.a. Copy the datafiles (all of them).
b. Copy the redo-logfiles (all of them).
4.a. (Unix only) Set the environment variables:
ORACLE_SID - set to the database name you wish to create
ORACLE_HOME - set to full pathname of the Oracle system home directory
PATH - needs to include $ORACLE_HOME/bin
b. (NT/2000 only) Do 'set ORACLE_SID=<SID>'
Use oradim to create the service for the instance. For more information
on oradim please refer to (the part that refers to creating a new instance):
Note:68720.1 Creating a new 7.3, 8.0, 8.1 Instance/Database
5. Use servermanager (check the name to use for your version of oracle) or
sqlplus (version 9i and above) to startup the database in mount mode.
Do
CONNECT INTERNAL/<PASSWORD>
then
STARTUP MOUNT
Then do a rename of the copied datafiles if they are not in the same path as on
the other machine. For all the files that are in the result of the query:
SELECT NAME FROM V$DATAFILE;
do
ALTER DATABASE RENAME FILE '<oldfullpath>\<filename>' to <
newfullpath>\<filename>';
6. Query the datadictionary for the old location of the redolog files using:
SELECT MEMBER FROM V$LOGFILE;
If the new place is not the same as the old do:
ALTER DATABASE RENAME FILE '<oldfullpath>\<redologfilename>' to &
lt;newfullpath>\<redologfilename>';
7. Now open the database:
ALTER DATBASE OPEN;
******************************************************************