Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Copy a production database to a development (in different instance) 1

Status
Not open for further replies.

SimonPeh

MIS
Sep 11, 2002
96
SG
Greetings,

Wonder if any guru would advise how to copy the database(let say instance A1) to another database in a different machine (let say instance B1).

I believe we could either export/import using the dump file or there another way to use the raw dbf file which is backup using ufsdump ?

Please advise on what is need to change on the control files and any action need to be done to the database that is copied over so that it would boot up as a instance B1.

Many thanks if you could help as we are conducting an exercise on development server. Thank you.

Regards
SP
 
Simon,

Try this:

1) Create a list of all database files in database A1:
Code:
select name from v$controlfile;
select file_name from dba_data_files;
select file_name from dba_temp_files;
select member from v$logfile;

2) Shutdown database A1.

3) Copy all files from step 1 plus "initA1.ora" to same paths on B1's server machine.

4) Ensure proper ancillary values:
a) Ensure correct values in oratab file.
b) Ensure LISTENER properly supports instance B1
c) Ensure initA1.ora has name initB1.ora and its parameter values are appropriate for instance B1.
d) Ensure $ORACLE_HOME and $ORACLE_SID are appropriate for instance B1.
Note: database name of B1 instance remains A1. This should not cause problems.

5) Startup B1.

Let us know if this works for you.

[santa]Mufasa
(aka Dave of Sandy, Utah, USA @ 17:19 (19Oct04) UTC (aka "GMT" and "Zulu"), 10:19 (19Oct04) Mountain Time)
 
yes, basically it went pretty well.

restore all the dbf file from ufsdump.
Did a backup control trace file in A1 and modify the script and rename it as a sql.
run the sql file in B1 to create back all the databases

and it started up just like that ...

had to modify $ORACLE_HOME/bin to 4755

Thanks Mufasa for the tip.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top