RE: Cloning Question
Scott - I think that Rachel offered better advice, and I'm sure you've read her note by now. I have some experience with missing files when cloning a database :-), but I haven't had the rollback tablespace missing, and that would be different. One thought would be to create an extra rollback tablespace on production, so that when you perform the clone operation, Oracle still has some rollback segments available. Dennis Williams DBA Lifetouch, Inc. [EMAIL PROTECTED] -Original Message- Sent: Thursday, May 09, 2002 12:03 PM To: Multiple recipients of list ORACLE-L Dennis, No. I did a create controlfile set database... I commented out the rollback_segments line in the init.ora and removed the reference to the file in the create controlfile statement. With no reference (that I know of) to the rollback segments or tablespace, I thought that the database should have come up, then I could create a new one. I must have missed something, but I don't know what that was. DENNIS WILLIAMS wrote: Scott - Let's see if I understand specifically what you did. You ran the CREATE DATABASE script that was generated from your production system. Now, since the datafile for rollback tablespace isn't there, Oracle will come up without it. Once your new instance was up, then you did a DROP TABLESPACE on the rollback tablespace, followed by a CREATE TABLESPACE. I've done that scenario quite a few times on Oracle 8.1.6, just yesterday, as a matter of fact (that was a temp tablespace). If those weren't your steps, then provide more details. Dennis Williams DBA Lifetouch, Inc. [EMAIL PROTECTED] -Original Message- Sent: Thursday, May 09, 2002 8:48 AM To: Multiple recipients of list ORACLE-L I spent a long time trying to clone our production data warehouse into test, to refresh it. I do this frequently, as both a way to refresh test instances and to test the backups. After fighting through 2 bad backups, I finally got a good one. However, the problem I had was that the production rollback tablespace is larger than the disk on test. My thought was that I could restore everything except the rollback tablespace, which is not the way I usually do it. I commented out the rollback_segments line in the init.ora and created a script that would create a new rollback tablespace and rollback segments, smaller than those in production. This didn't work, even though Oracle support said it should have. When I did the clone, the database would not open. I kept getting the following error: ORA-00600: internal error code, arguments: [25012], [1], [2], [], [], [], [], [] Does anyone know what I was doing wrong? I can't figure it out, and Oracle support couldn't figure it out, either. I was able to get the database up by getting more disk added, so that there was enough space to restore the rollback tablespace file. Thank you. -- Scott Canaan ([EMAIL PROTECTED]) (585) 475-7886 Life is like a sewer, what you get out of it depends on what you put into it - Tom Lehrer -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Scott Canaan INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists 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.com -- Author: DENNIS WILLIAMS INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists 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). -- Scott Canaan ([EMAIL PROTECTED]) (585) 475-7886 Life is like a sewer, what you get out of it depends on what you put into it - Tom Lehrer -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Scott Canaan INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the
Re: Cloning Question
I thought there was a rollback segment in system that would be there. It should be enough to get things started. After all, there isn't a separate one when you create a database, until you create it. DENNIS WILLIAMS wrote: Scott - I think that Rachel offered better advice, and I'm sure you've read her note by now. I have some experience with missing files when cloning a database :-), but I haven't had the rollback tablespace missing, and that would be different. One thought would be to create an extra rollback tablespace on production, so that when you perform the clone operation, Oracle still has some rollback segments available. Dennis Williams DBA Lifetouch, Inc. [EMAIL PROTECTED] -Original Message- Sent: Thursday, May 09, 2002 12:03 PM To: Multiple recipients of list ORACLE-L Dennis, No. I did a create controlfile set database... I commented out the rollback_segments line in the init.ora and removed the reference to the file in the create controlfile statement. With no reference (that I know of) to the rollback segments or tablespace, I thought that the database should have come up, then I could create a new one. I must have missed something, but I don't know what that was. DENNIS WILLIAMS wrote: Scott - Let's see if I understand specifically what you did. You ran the CREATE DATABASE script that was generated from your production system. Now, since the datafile for rollback tablespace isn't there, Oracle will come up without it. Once your new instance was up, then you did a DROP TABLESPACE on the rollback tablespace, followed by a CREATE TABLESPACE. I've done that scenario quite a few times on Oracle 8.1.6, just yesterday, as a matter of fact (that was a temp tablespace). If those weren't your steps, then provide more details. Dennis Williams DBA Lifetouch, Inc. [EMAIL PROTECTED] -Original Message- Sent: Thursday, May 09, 2002 8:48 AM To: Multiple recipients of list ORACLE-L I spent a long time trying to clone our production data warehouse into test, to refresh it. I do this frequently, as both a way to refresh test instances and to test the backups. After fighting through 2 bad backups, I finally got a good one. However, the problem I had was that the production rollback tablespace is larger than the disk on test. My thought was that I could restore everything except the rollback tablespace, which is not the way I usually do it. I commented out the rollback_segments line in the init.ora and created a script that would create a new rollback tablespace and rollback segments, smaller than those in production. This didn't work, even though Oracle support said it should have. When I did the clone, the database would not open. I kept getting the following error: ORA-00600: internal error code, arguments: [25012], [1], [2], [], [], [], [], [] Does anyone know what I was doing wrong? I can't figure it out, and Oracle support couldn't figure it out, either. I was able to get the database up by getting more disk added, so that there was enough space to restore the rollback tablespace file. Thank you. -- Scott Canaan ([EMAIL PROTECTED]) (585) 475-7886 Life is like a sewer, what you get out of it depends on what you put into it - Tom Lehrer -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Scott Canaan INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists 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.com -- Author: DENNIS WILLIAMS INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists 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). -- Scott Canaan ([EMAIL PROTECTED]) (585) 475-7886 Life is like a sewer, what you get out of it depends on what you put into it - Tom Lehrer -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Scott Canaan INET: [EMAIL PROTECTED] Fat City
Re: Cloning Question
In some versions of Oracle, you need a SECOND rollback segment created in the SYSTEM tablespace in order to create another tablespace. It can't hurt to add it (you can drop it immediately after you get the rollback tablespace created) but it could be the solution. Since you didn't include the version of the database you are working with, we have to be somewhat generic in our answers Rachel |+--- || | || | || srcdco@ritvax| || .rit.edu | || | || 05/09/2002 | || 02:28 PM | || Please | || respond to | || ORACLE-L | || | |+--- | || | To: [EMAIL PROTECTED] | | cc: (bcc: Rachel Carmichael) | | Subject: Re: Cloning Question| | I thought there was a rollback segment in system that would be there. It should be enough to get things started. After all, there isn't a separate one when you create a database, until you create it. DENNIS WILLIAMS wrote: Scott - I think that Rachel offered better advice, and I'm sure you've read her note by now. I have some experience with missing files when cloning a database :-), but I haven't had the rollback tablespace missing, and that would be different. One thought would be to create an extra rollback tablespace on production, so that when you perform the clone operation, Oracle still has some rollback segments available. Dennis Williams DBA Lifetouch, Inc. [EMAIL PROTECTED] -Original Message- Sent: Thursday, May 09, 2002 12:03 PM To: Multiple recipients of list ORACLE-L Dennis, No. I did a create controlfile set database... I commented out the rollback_segments line in the init.ora and removed the reference to the file in the create controlfile statement. With no reference (that I know of) to the rollback segments or tablespace, I thought that the database should have come up, then I could create a new one. I must have missed something, but I don't know what that was. DENNIS WILLIAMS wrote: Scott - Let's see if I understand specifically what you did. You ran the CREATE DATABASE script that was generated from your production system. Now, since the datafile for rollback tablespace isn't there, Oracle will come up without it. Once your new instance was up, then you did a DROP TABLESPACE on the rollback tablespace, followed by a CREATE TABLESPACE. I've done that scenario quite a few times on Oracle 8.1.6, just yesterday, as a matter of fact (that was a temp tablespace). If those weren't your steps, then provide more details. Dennis Williams DBA Lifetouch, Inc. [EMAIL PROTECTED] -Original Message- Sent: Thursday, May 09, 2002 8:48 AM To: Multiple recipients of list ORACLE-L I spent a long time trying to clone our production data warehouse into test, to refresh it. I do this frequently, as both a way to refresh test instances and to test the backups. After fighting through 2 bad backups, I finally got a good one. However, the problem I had was that the production rollback tablespace is larger than the disk on test. My thought was that I could restore everything except the rollback tablespace, which is not the way I usually do it. I commented out the rollback_segments line in the init.ora and created a script that would create a new rollback tablespace and rollback segments, smaller than those in production. This didn't work, even though Oracle support said it should have. When I did the clone, the database would not open. I kept getting the following error: ORA-00600: internal error code, arguments: [25012], [1], [2], [], [], [], [], [] Does anyone know what I was doing wrong? I can't figure it out, and Oracle support couldn't figure it out, either. I was able to get the database up by getting more disk added, so that there was enough space to restore the rollback tablespace file. Thank you. -- Scott Canaan ([EMAIL PROTECTED]) (585) 475-7886 Life is like a sewer, what you get out of it depends on what you put into it - Tom Lehrer -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Scott Canaan INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note
Re: Cloning Question
I'm sorry, and I should know better. We are on 8.1.7.0.0 on Sun Solaris 2.6. [EMAIL PROTECTED] wrote: In some versions of Oracle, you need a SECOND rollback segment created in the SYSTEM tablespace in order to create another tablespace. It can't hurt to add it (you can drop it immediately after you get the rollback tablespace created) but it could be the solution. Since you didn't include the version of the database you are working with, we have to be somewhat generic in our answers Rachel |+--- || | || | || srcdco@ritvax| || .rit.edu | || | || 05/09/2002 | || 02:28 PM | || Please | || respond to | || ORACLE-L | || | |+--- | || | To: [EMAIL PROTECTED] | | cc: (bcc: Rachel Carmichael) | | Subject: Re: Cloning Question| | I thought there was a rollback segment in system that would be there. It should be enough to get things started. After all, there isn't a separate one when you create a database, until you create it. DENNIS WILLIAMS wrote: Scott - I think that Rachel offered better advice, and I'm sure you've read her note by now. I have some experience with missing files when cloning a database :-), but I haven't had the rollback tablespace missing, and that would be different. One thought would be to create an extra rollback tablespace on production, so that when you perform the clone operation, Oracle still has some rollback segments available. Dennis Williams DBA Lifetouch, Inc. [EMAIL PROTECTED] -Original Message- Sent: Thursday, May 09, 2002 12:03 PM To: Multiple recipients of list ORACLE-L Dennis, No. I did a create controlfile set database... I commented out the rollback_segments line in the init.ora and removed the reference to the file in the create controlfile statement. With no reference (that I know of) to the rollback segments or tablespace, I thought that the database should have come up, then I could create a new one. I must have missed something, but I don't know what that was. DENNIS WILLIAMS wrote: Scott - Let's see if I understand specifically what you did. You ran the CREATE DATABASE script that was generated from your production system. Now, since the datafile for rollback tablespace isn't there, Oracle will come up without it. Once your new instance was up, then you did a DROP TABLESPACE on the rollback tablespace, followed by a CREATE TABLESPACE. I've done that scenario quite a few times on Oracle 8.1.6, just yesterday, as a matter of fact (that was a temp tablespace). If those weren't your steps, then provide more details. Dennis Williams DBA Lifetouch, Inc. [EMAIL PROTECTED] -Original Message- Sent: Thursday, May 09, 2002 8:48 AM To: Multiple recipients of list ORACLE-L I spent a long time trying to clone our production data warehouse into test, to refresh it. I do this frequently, as both a way to refresh test instances and to test the backups. After fighting through 2 bad backups, I finally got a good one. However, the problem I had was that the production rollback tablespace is larger than the disk on test. My thought was that I could restore everything except the rollback tablespace, which is not the way I usually do it. I commented out the rollback_segments line in the init.ora and created a script that would create a new rollback tablespace and rollback segments, smaller than those in production. This didn't work, even though Oracle support said it should have. When I did the clone, the database would not open. I kept getting the following error: ORA-00600: internal error code, arguments: [25012], [1], [2], [], [], [], [], [] Does anyone know what I was doing wrong? I can't figure it out, and Oracle support couldn't figure it out, either. I was able to get the database up by getting more disk added, so that there was enough space to restore the rollback tablespace file. Thank you. -- Scott Canaan ([EMAIL PROTECTED]) (585) 475-7886 Life is like a sewer, what you get out of it depends on what you put into it - Tom Lehrer -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Scott Canaan INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California