Re: Database refresh

From: koert54 <koert54_at_nospam.com>
Date: Sat, 29 Sep 2001 09:53:13 GMT
Message-ID: <dSgt7.77666$6x5.16872496@afrodite.telenet-ops.be>

You do not have the archives ? How did you backup the DB - cold backup or hot backup ?
Either you perform a cold backup - and then after restoring and recreating the controlfile you don't need to perform a recovery- you just open the DB using resetlogs ... Or you perform a hot backup - and then of course you need to do a recovery and most probably you'll need your archives ... if you do have the archives laying around on your source machine - just copy them over to the destination machine - configure the archive init.ora parameters to point to the archives or ... heck, you can just type the path+file name of the archive everytime Oracle asks for it ....

I sure hope you did not perform a hotbackup of a database that wasn't running in archivelog mode - or it was running in archivelog mode but your tablespaces were not in begin backup mode ... you definitely might want to check your backup procedure ...

Possible things to do here (depending on the importance of this DB) : 1. contact Oracle support
2. wait for someone else to reply on this thread who can put this in another perspective
3. or (some people might find this bad practice)... if there's absolutely no other way to startup this DB you can put in the parameter of the last hope in your init.ora, being _allow_resetlogs_corruption=TRUE
This parameter allows the opening of your DB in INCONSISTENT STATE ! When the database opens - take a FULL EXPORT, recreate your DB and perform a FULL import. Check if all data is OK... I have seen this fail only once !

But why don't you just take a GOOD backup of the source DB running in archivelog mode (besides the time it takes to do the excercice again) ? I do it all the time to make a test DB for our developers ...

Hope everything works out - just had a rough night myself ... been working a DB since 4 in the morning :-)))
cheers,
Koert

"Night Shade Books" <jasonw_at_nightshadebooks.com> wrote in message news:3800585A27A89837.64188A3DF9CC2361.5DE4EB243A7651ED_at_lp.airnews.net...
> "koert54" <koert54_at_nospam.com> wrote in message
> news:2Tft7.77553$6x5.16843409_at_afrodite.telenet-ops.be...
> > Change the 'recover database' command at the end of the trace to
'recover
> > database using backup controlfile' and then
> > 'alter database open resetlogs' (might have to use until cancel because
> you
> > open with resetlogs ..)
> > I usually throw those commands out and do the recovery myself ...
> >
> > > ORA-00283: recovery session canceled due to errors
> > > ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
> > --> you created a new controlfile - it can not be used anymore as a
> > reference for the other datafiles - that's why you
> > need to specify that it's a backup controlfile in the recovery command
...
> > it does not mean you have to do
> > the 'alter database backup controlfile to trace' again !
> >
> >
> > cheers
> > Koert

>

> First, thanks for your help. I'm going insane here.
>
> Ok, so I whacked all the control files again, and generated a new
tracefile.
> I edited it so it looks like so: (EBDB1 is the new name)

>

> STARTUP NOMOUNT
> CREATE CONTROLFILE SET DATABASE "EBDB1" RESETLOGS NOARCHIVELOG
> MAXLOGFILES 32
> MAXLOGMEMBERS 2
> MAXDATAFILES 500
> MAXINSTANCES 8
> MAXLOGHISTORY 904
> LOGFILE
> GROUP 1 '/u03/oradata/EBQA817/redo01.log' SIZE 10M,
> GROUP 2 '/u03/oradata/EBQA817/redo02.log' SIZE 10M,
> GROUP 3 '/u03/oradata/EBQA817/redo03.log' SIZE 10M
> DATAFILE
> '/u02/oradata/EBDB1/system01.dbf',
> '/u02/oradata/EBDB1/tools01.dbf',
> '/u03/oradata/EBDB1/rbs01.dbf',
> '/u03/oradata/EBDB1/data03_03.dbf',
> '/u02/oradata/EBDB1/users01.dbf',
> '/u02/oradata/EBDB1/indx01.dbf',
> '/u04/oradata/EBDB1/indx01a_01.dbf',
> '/u03/oradata/EBDB1/data01_01.dbf',
> '/u03/oradata/EBDB1/data01_02.dbf',
> '/u04/oradata/EBDB1/indx01a_02.dbf',
> '/u03/oradata/EBDB1/data02_01.dbf',
> '/u04/oradata/EBDB1/indx01b_01.dbf',
> '/u03/oradata/EBDB1/data02_02.dbf',
> '/u04/oradata/EBDB1/indx02a_01.dbf',
> '/u03/oradata/EBDB1/data02_03.dbf',
> '/u04/oradata/EBDB1/indx02a_02.dbf',
> '/u03/oradata/EBDB1/data02_04.dbf',
> '/u04/oradata/EBDB1/indx03a_01.dbf',
> '/u03/oradata/EBDB1/data03_01.dbf',
> '/u04/oradata/EBDB1/indx03a_02.dbf',
> '/u03/oradata/EBDB1/data03_02.dbf',
> '/u04/oradata/EBDB1/indx08a_01.dbf',
> '/u03/oradata/EBDB1/data08_01.dbf',
> '/u04/oradata/EBDB1/indx04a_01.dbf',
> '/u03/oradata/EBDB1/data04_01.dbf',
> '/u04/oradata/EBDB1/indx04a_02.dbf',
> '/u03/oradata/EBDB1/data04_02.dbf',
> '/u04/oradata/EBDB1/indx05a_01.dbf',
> '/u03/oradata/EBDB1/data05_01.dbf',
> '/u04/oradata/EBDB1/indx06a_01.dbf',
> '/u03/oradata/EBDB1/data06_01.dbf',
> '/u04/oradata/EBDB1/indx07a_01.dbf',
> '/u03/oradata/EBDB1/data07_01.dbf',
> '/u02/oradata/EBDB1/tsdef_01.dbf',
> '/u02/oradata/EBDB1/imprbsts01.dbf',
> '/u02/oradata/EBDB1/imprbsts02.dbf',
> '/u04/oradata/EBDB1/indx03a_03.dbf'
> CHARACTER SET WE8ISO8859P9;

>

> RECOVER DATABASE USING BACKUP CONTROLFILE;

>

> ALTER DATABASE OPEN RESETLOGS;

>

> But now I end up with this:

>

> SVRMGR> recover database using backup controlfile until cancel;
> ORA-00279: change 102582082 generated at 09/28/2001 19:30:59 needed for
> thread 1
> ORA-00289: suggestion : /u01/app/oracle/product/8.1.7/dbs/arch1_1.dbf
> ORA-00280: change 102582082 for thread 1 is in sequence #1
> Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
> cancel
> ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error
> below
> ORA-01194: file 1 needs more recovery to be consistent
> ORA-01110: data file 1: '/u02/oradata/EBDB1/system01.dbf'
>
> The problem is that this is on a new machine, and I don't have those
archive
> logs.

>

> And after that, I can't get it to do an 'alter database open resetlogs',
> because it tells me that further recovery is needed.

>

> Thanks,

>

> Jason

>
>
>
>

Received on Sat Sep 29 2001 - 04:53:13 CDT