"Smith, Ron L." wrote: > > Whenever we clone a database on the same server we have always had the > understanding that the original database must be down until the new > database is renamed by running the control file script. > > I am going through the Oracle Recovery 101 book in an effort to > understand RMAN and one chapters in the book is cloning a database on > the same server. I just went through the steps to create a clone of a > hot database. I created the new database on the same server with a new > name while the original database was up and running. I had no problems. > Was our belief that the original database had to be down, incorrect, or > was this just a restriction of older version like 7.3.4? > > Thanks! > Ron Smith
Ron, When you clone a database, you start with : 1) changing db_name in the init.ora file and most paths 2) defining a new ORACLE_SID and renaming init.ora accordingly 3) starting the instance without mounting it - your init.ora file is opened and read. Where do you want anything to interact (badly) with an existing database? You have allocated some shared memory, have started a few processes and read a file. Big deal. Your belief was wrong. -- Regards, Stephane Faroult Oriole Software -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Stephane Faroult INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
