-
-
Hi
You need to just copy the datafile from the standby database to the server where you want the clone to be.
Just use the rman copy command to do this its very simple something like
RMAN> run{
backup as copy datafile 1 format 'D:\ORADATA\CLONEDB\SYSTEM01.DBF';
.....
}
take a backup of the controlfile to trace edit and to change the paths and then use it to recreate the controlfile on the clone database.
make sure you edit the first few lines to
create controlfile set database 'dbname' resetlogs
once the controlfile is created and the database mounted
recover datbase using backupcontrolfile until cancel
apply archivelogs if any to make it consistent and then open the database with alter database open resetlogs
hope you get the idea
regards
Hrishy
-
-
Hi
There are no other ideas you need to NFS mount the clone server and copy the datafiles.
If thats not possible then you need to copy over the files to temp location on the standby server on a file by file basis and scp teh files over to the clone server .
Only in 11g you can clone from a live database and in all other versions you need to use the copy of the backup to clone and you need space for that.
regards
Hrishy
-
Hot
If I just stop the managed recovery and copy the files, would this be equivalent to hot backup?
"The person who says it cannot be done should not interrupt the person doing it." --Chinese Proverb
-
Hi
Yes but you need to apply the archivelogs to make the datafiles consistent.
But why would you go that route ? and disturb scheme of things RMAN copy command is simple and non-intrusive and most important standby database dont ahev to play catch up with primary
regards
Hrishy
-
The old, olD, oLD, OLD procedure to clone a database
Originally Posted by hrishy
Hi
Yes but you need to apply the archivelogs to make the datafiles consistent.
But why would you go that route ? and disturb scheme of things RMAN copy command is simple and non-intrusive and most important standby database dont ahev to play catch up with primary
regards
Hrishy
I know, every backup/clone/etc.. here I do with RMAN.
Unfortunately on this particular server we have no space for an rman backup (1.2T) therefore I have mounted the data files (mp) unto the target server where I can copy to other locations, create the controlfile and start the clone (like the old, olD, oLD, OLD procedure to clone databases)...
Thanks for your help!
.
"The person who says it cannot be done should not interrupt the person doing it." --Chinese Proverb
-
Ta-ra-rara-tara!!! (trumpets blaring)
And the solution is:
1) Stop managed recovery on the standby:
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
2) Copy the files from standby mp to clone mp.
3) Re-start managed recovery on the standby:
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
DISCONNECT FROM SESSION;
4) Re-create the controlfile on the clone:
STARTUP NOMOUNT
CREATE CONTROLFILE SET DATABASE "CLONEDB" RESETLOGS FORCE LOGGING NOARCHIVELOG
-- Etc --
5) Open clone database with resetlogs
And ALL is OK!
.
"The person who says it cannot be done should not interrupt the person doing it." --Chinese Proverb
-
Hi
Congrajulations Dont just sit there its time you open a blog and blog about this :-) and tell the whole world ;-)
regards
Hrishy
-
Nicely done LKBrwn_DBA, congrats!
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|