Yeah, went through the standard cloning process. My first line of trace file looked like this...
CREATE CONTROLFILE SET DATABASE "DM8" RESETLOGS NOARCHIVELOG I am wondering if I should have stated NORESETLOGS here instead, that way the data in the redo logs would be available and then the cloned instance could have performed instance recovery. I have always used the method above and never had any problems but that is likely because I have always done a SHUTDOWN NORMAL instead of SHUTDOWN IMMEDIATE. While the SHUTDOWN immediate performs a checkpoint it looks like there can still be stuff out there in the logs that will require instance recovery. Since I did a RESETLOGS I am guessing this necessary info is missing. Wondering if everything will be OK if I try to find another way to get the clone opened, like setting the hidden allow corrupt logs parameter. Ethan Post perotdba (AIM), epost1 (Yahoo) -------------------------------------------------------------------- -----Original Message----- Sent: Monday, July 29, 2002 12:59 PM To: Multiple recipients of list ORACLE-L Did you recover the database using backup controlfile? Try that. HTH, Ruth -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Post, Ethan 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).
