Clone standby database without rman
Hi guys!
I need to clone a standby database without using rman (have no disk space).
Here is the setup:
OS: HPUX
Oracle9i Enterprise Edition Release 9.2.0.6.0
Server S has standby db
Server C has mounted /oradata disk from standby
What I intend to do (if it's possible) is kinda similar to "cloning" a database from an OS hot backup:
1) QUIESCE the standby (can it be done?) :confused:
2) Copy db files from /oradata/standby to /oradata/clone
3) UNQUIESCE the standby
4) Re-create clone control file + open reset logs
Q1: Can I stop managed recovery and quiesce the standby? .. And then unquiesce and restart managed recovery?
Q2: Will copying the files be enough to clone db or do I need something else like redo/archive logs?
It's been a very looooooong time since I cloned a db from hot/cold backup.
:p
The old, olD, oLD, OLD procedure to clone a database
Quote:
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)...
:cool:
Thanks for your help!
.
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! :p
.