It's been a while, and this is from memory, but I don't believe you need to re-create the control file. If I recall correctly, it's as simple as: shutdown immediate (if you need to do an abort above, make sure you startup and shutdown immediate, immediately following. Since you're resetting the on-line redo, you need a clean shutdown.) startup mount recover database until cancel; cancel alter database open resetlogs; I think that will do it...test on a throwaway database first. -Mark On Mon, 2006-04-24 at 19:24 -0500, Schultz, Charles wrote: > I have simply recreated the controlfile in the past, although I am not > sure this is the "best" way to do it. > > backup controlfile to trace, alter the resulting trace file (modify > those annoying comments so they are real sql*plus comments, and anything > else you need/want). There are two scenarios in the backed up > controlfile, the first a noresetlogs, the 2nd with resetlogs. I believe > you will want the 2nd example. No recovery needed, unless (depending on > how you shut down), the database will not start because sys needs "is > not a current copy" and needs to be recovered. Simply point the recovery > to the online redo logs, if this is the case. > > > -----Original Message----- > From: oracle-l-bounce@xxxxxxxxxxxxx > [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Bob > Sent: Monday, April 24, 2006 7:12 PM > To: oracle-l > Subject: RESETLOGS w/o incomplete recovery > > Guys, say I'm in a development environment ,and to be sure I dont have > gaps in my archive log or I just feel like resetting them to 0 , I;d to > to reset the logs without going through the trouble of performing > incomplete recovery. Is there a way to do this? > > Thanks > Bob > > -- > "Oracle error messages being what they are, do not highlight the correct > cause of fault, but will identify some other error located close to > where the real fault lies." > > -- > //www.freelists.org/webpage/oracle-l > > > -- > //www.freelists.org/webpage/oracle-l > > -- //www.freelists.org/webpage/oracle-l