Printable View
I have an assignment to create a Staging server, I copied all the datafiles & archive logs from the production to staging server.. I have init & control file of production server. The database name is different in staging server and also the locations of the datafiles.
Then what should I do? please help me..
re-create the control file and start it up
DAV can u plz tell me how to create staging database ????
Its like that or not... ???
Create a database on staging server
Stop the database on the staging server.
Backup the staging database in case it is required later.
Create an offline backup of the production database.
Restore the production database backup on the staging server, overwriting the staging database.
Start the database on the staging server.
I would recommend using DBCA.
1)At the source database, start dbca
2)enter "Manage Templates"
3)Create template from the source database INCLUDING Structure as well as data
4)go to the $ORACLE_HOME/assistants/dbca/templates
identify all the files, containng in their name the template name you gave during the template creation and copy them to the destination machine
$ORACLE_HOME/assistants/dbca/templates
5) At the destination machine start DBCA
6) Select create database. In the list of templates, bellow OLTP, DWH, general purpose, you will see your template name. Select it
7) Follow the wizard, complete the database creation
8) Check if all the data users etc are ok and be happy :-)
NOTE: That works only if the source and destination OS is same
P.S.
Some more details about DBCA templates here
http://download-uk.oracle.com/docs/c...te.htm#1000144
I mounted the destination database with source control file, and then run the commands to rename datafiles as "alter database rename file from .. to ..."
and the recover the database applying archive logs.
There is no need to rename the datafile in staging.
eh? have you actually read the thread?Quote:
Originally Posted by ams-jamali
Staging database is a copy of production database, with all the schema. Its a test environment where one test the code before deplying into the production.
There are many different explanations in the net.
Easy in exporting all the schema from production into staging or do a full import.
I'm in agreement this exp/imp strategy is fine to refresh your staging environment -depending on the size of this environment- but, you missed a small detail, as per original poster "I have an assignment to create a Staging server" therefore, database has to be created; exp/imp strategy wouldn't do itQuote:
Originally Posted by dbasan
OP is doing well.
Also did you notice, OP says staging server db name is different from production db and he is finding it difficult to make it from the production datafiles and arc logs.Quote:
Originally Posted by PAVB
Instead create a database in staging server, create all the tablespaces as in production, then import the production dump in staging and its all done. Simple isn't. :D
I didn't see any "create a database in staging server" in your original post; you added it after I pointed your strategy wouldn't do it.
Duplicating a database from datafiles/archivelogs/controlfiles/... works all the time; I will love to see you working out your exp/imp strategy in a medium size database... lets say as small as 500Gig in size.
If you want to suggest a solution that has a size constraint, better to ask OP for the size of the database, then, if applies, suggest it. Simple isn't :D
I cannot assume sizes and give solution for all options. Its the responsibility of the OP to get the solution by providing the data in the forum.
I give suggestions and clues by which the OP has to decide what is best for him/her. :)
Thanks for pointing, i expected this from the OP, are they paying attention. I dont like to spoon feed unless the baby asks.Quote:
you added it after I pointed your strategy wouldn't do it.
Some one told me they copy the phy file from PROD DB by CA (without shutdown PROD DB coz 24*7 inv),and PLACE the phy file to staging database
and staging database using for backup and reporting purpose.
THEY r using HP-UX.
Its not clear,WHT the CA??,how to copy ?? ....anybody give the details information???
My eyes! my eyes!
can you PLEASE post in legible English using real words - it makes your posts so hard to readQuote:
Originally Posted by liakat
Will it be work with 24*7 DB?
Take hot backup of production database.
Copy datafiles to staging server.
Create controlfile script from production database.
Transfer archive logs to staging server.
Rename database by creating controlfile. The script is created from production database.
recover database.
Open DB with resetlogs.
Thanks Dave.,but iam too late to say.
only after seeing your post, i read the thread second time.
Just a couple of minor changes... in the blue color
Quote:
Originally Posted by bhattnirav
Thanks PAVB