RE: Database Cloning
But you still need to do a cold copy of the database files, right? -Original Message- Sent: 15 September 2003 22:30 To: Multiple recipients of list ORACLE-L >Your belief was wrong. Actually, the belief was correct for some versions of oracle and some platforms. Case in point was Oracle 7 on an HP server. The source must be down in order to bring up the clone and recreate the control file. Ron Thomas Hypercom, Inc [EMAIL PROTECTED] Each new user of a new system uncovers a new class of bugs. -- Kernighan [EMAIL PROTECTED] om To: [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED]Subject: Re: Database Cloning .com 09/15/2003 02:39 PM Please respond to ORACLE-L "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). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Ron Thomas 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 &
RE: Database Cloning
Thank you! I thought I was going to have to quit drinking. Or drink more. Ron -Original Message- Sent: Monday, September 15, 2003 4:30 PM To: Multiple recipients of list ORACLE-L >Your belief was wrong. Actually, the belief was correct for some versions of oracle and some platforms. Case in point was Oracle 7 on an HP server. The source must be down in order to bring up the clone and recreate the control file. Ron Thomas Hypercom, Inc [EMAIL PROTECTED] Each new user of a new system uncovers a new class of bugs. -- Kernighan [EMAIL PROTECTED] om To: [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED]Subject: Re: Database Cloning .com 09/15/2003 02:39 PM Please respond to ORACLE-L "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). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Ron Thomas 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). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Smith, Ron L. 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).
Re: Database Cloning
>Your belief was wrong. Actually, the belief was correct for some versions of oracle and some platforms. Case in point was Oracle 7 on an HP server. The source must be down in order to bring up the clone and recreate the control file. Ron Thomas Hypercom, Inc [EMAIL PROTECTED] Each new user of a new system uncovers a new class of bugs. -- Kernighan [EMAIL PROTECTED] om To: [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED]Subject: Re: Database Cloning .com 09/15/2003 02:39 PM Please respond to ORACLE-L "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). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Ron Thomas 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).
Re: Database Cloning
"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).
RE: Database Cloning
Ron, I believe it was a misinterpretation of Oracle's documentation. I regret to say that I've been there, done that only to learn better later. The problem is that we confuse the relationship between the Oracle SID and the DB_NAME. It is totally possible to start an instance with a SID of DEVL where the DB_NAME in the init.ora file is "PROD' on the same server. I agree with you that you want to change the DB_NAME as quickly as possible before letting everyone in, but it does work. All of the OS processes are related to each other by the SID and the db_files by the DB_NAME. Dick Goulet Senior Oracle DBA Oracle Certified 8i DBA -Original Message- Sent: Monday, September 15, 2003 4:14 PM To: Multiple recipients of list ORACLE-L 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 -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Smith, Ron L. 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). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Goulet, Dick 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).
