Re: resetlogs

Stuffed up standby due to lost archive?

Fair enough: you've no choice but to blow away the standby, and re-create it from scratch. One of the inherent weaknesses of standby is that a break in the redo stream renders it totally worthless (as you have discovered!).

You could of course upgrade to... (wait for it!) ... 9i, because standby in that version has a whole new infrastructure that is able to hare off to various places looking for missing redo. (They call it 'Data Guard').

Doesn't help you much in your current predicament -but at least it's only the standby that's lost.

Unless....

Given that there's now a gap in your archive sequence, your production database is now vulnerable to a failure which cannot be recovered over. You have immediately started to take a new backup of production, haven't you?

Regards
HJR

--
----------------------------------------------
Resources for Oracle: http://www.hjrdba.com
===============================


"clueless" <ro_cright_at_hotmail.com> wrote in message
news:p8wh8.3456$f5.139607_at_news...


> Yeah,  I re-read my earlier post and I have to say I'm scratching my head

a


> bit.  What I was really want to do is to solve my standby database issue

> (lost an archived log file).  I figured I could start over by 'somehow'

> forcing the db to reset logs to 1, creating another hot backup using the

> ocopy command, then, I thought, I would be able to apply the logs to the

> standby db and voila.

>

> Thanks for everyone's input. Much appreciated.

>

> BTW dig your site Howard.

>

>

> "Howard J. Rogers" <dba_at_hjrdba.com> wrote in message

> news:a65voe$ork$1_at_lust.ihug.co.nz...

> > 1.   If the database is open, it is in a consistent state (or, more

> > precisely, it would be once you issue a clean shutdown command).

> >

> > 2.   What does resetlogs do?  Forces synchronization to allow an

> internally

> > inconsistent database to be opened.

> >

> > Is your database internally inconsistent?  No (see point 1).  Therefore,

> why

> > on Earth would you want to issue resetlogs in the first place?

> >

> > Your step 6 is the one I can't fathom.  Why do you think that you need

to


> > issue a resetlogs simply in order to perform a fresh hot backup?  You

> don't.

> >

> > I saw in another of your posts that having tried to recover your hot

> backup,

> > it asks for archives from before the time the backup started.  That

simply


> > cannot happen... unless you are not taking the backup properly.  I hope

> you

> > have remembered to do the 'alter tablespace blah begin backup' command

> > before attempting to copy the data files.  And I hope you've remembered

to


> > take a consistent backup of the controlfile, using 'alter database

backup


> > command to 'blah.ctl''.  And I hope you aren't trying to hot copy the

> online

> > redo logs.

> >

> > Regards

> > HJR

> > --

> > ----------------------------------------------

> > Resources for Oracle: http://www.hjrdba.com

> > ===============================

> >

> >

> > "clueless" <ro_cright_at_hotmail.com> wrote in message

> > news:snph8.3353$f5.133770_at_news...

> > > I want to issue the resetlog command on a database that is open.

> > >

> > > Why?

> > > 1. production db cannot be shut down.  No coffee, no doughnuts, ...

> > > 2. I'm worried that the server is going to crash. Vendor's app is

flaky


> > and

> > > they are screwing around with it.

> > > 3. I want to create a standby oracle db.  Need to defend myself.

> > > 4. I have created a hot backup and moved the archived redo logs over

to


> > the

> > > standby server.

> > > 5. I lost one of the archive logs. I am a moron.

> > > 6. I can redo the hotbackup but without setting the resetlog I'm

> screwed.

> > I

> > > think?

> > >

> > > Clueless...

> > >

> > >

> > >

> >

> >

>

>