RE: recovery question

He need to use a control file which is at least 2006-05-10:09:15:00.
Also, check the alert log file to what logs have been applied.

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Sweetser, Joe
Sent: Wednesday, May 10, 2006 3:17 PM
To: Oracle-L@xxxxxxxxxxxxx
Subject: recovery question


In the middle of researching for a colleague, but thought I'd check here
too.

Database 9.2.0.4.0
OS HP-UX B11.00

Wanted to restore database to 9:15am server time this morning (5/10/06).
Last hot backup was (5/7/06).  All database files and controlfiles were
restored and then he did this:

<snip>

> sqlplus

SQL*Plus: Release 9.2.0.4.0 - Production on Wed May 10 12:37:58 2006
Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

Enter user-name: sys as sysdba
Enter password:
Connected to an idle instance.

SQL> startup mount
ORACLE instance started.
Total System Global Area  162525384 bytes
Fixed Size                   737480 bytes
Variable Size             109051904 bytes
Database Buffers           52428800 bytes
Redo Buffers                 307200 bytes
Database mounted.

SQL> Recover database until time '2006-05-10:09:15:00';
Media recovery complete.
SQL> alter database open;
alter database open
* 
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

SQL> alter database open noresetlogs;
Database altered.

<snip>

Customer said they did not see changes after 5/7.  I had my guy run the
following query to check on the archive logs timestamps:

select to_char(first_time, 'DD-MON-YYYY HH:MI:SS') from v$loghist;

and the last few lines returned were:

04-MAY-2006 11:07:37
04-MAY-2006 11:08:24
05-MAY-2006 07:41:00
06-MAY-2006 10:01:17
07-MAY-2006 12:00:26
07-MAY-2006 03:00:09

It seems that the database was not rolled forward to the time he wanted.
And, of course, a new archive log has over-written the old archive log
because the database was opened noresetlogs and blah, blah, blah.  

He has all the old archive logs and is now restoring the Sunday backup
again for attempt #2 and I am trying to help make this one successful.

Questions:
1.  Should he see the archive logs being applied as it occurs? (I would
think yes)
2.  Should he open resetlogs to avoid any archive/redo issues when
opening the database in the future?  (Again, I lean towards yes given
what just happened to him :-) )
3.  It seems to me the real problem is that he restored the Sunday
controlfile which only know about archive logs up to the time the backup
was taken.  Therefore, the recover command completed almost immediately
without applying logs because there were no logs to apply.  Soo, does he
recreate the controlfile and then issue the same command plus "using
backup controlfile"?  Any other suggestions?

Thanks,
-joe   
--
http://www.freelists.org/webpage/oracle-l



This e-mail is intended solely for the person or entity to which it is 
addressed and may contain confidential and/or privileged information. Any 
review, dissemination, copying, printing or other use of this e-mail by persons 
or entities other than the addressee is prohibited. If you have received this 
e-mail in error, please contact the sender immediately and delete the material. 
____________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email Security 
System. Any questions please call 972-721-8257 or email your request to 
tech_support@xxxxxxxxxxxx
--
http://www.freelists.org/webpage/oracle-l


Other related posts: