
|
[oracle-l]
||
[Date Prev]
[06-2006 Date Index]
[Date Next]
||
[Thread Prev]
[06-2006 Thread Index]
[Thread Next]
RE: Open read only after incomplete recovery?
- From: "Baumgartel, Paul" <paul.baumgartel@xxxxxxxxxxxxxxxxx>
- To: "'David Sharples'" <davidsharples@xxxxxxxxx>
- Date: Thu, 1 Jun 2006 16:23:43 -0400
No, not RAC. Here's the transcript of my latest attempt. Any
suggestions/corrections welcomed.
Note that I have also tried this without specifying "using backup
controlfile"--same result.
SQL> recover database until cancel using backup controlfile
ORA-00279: change 5656280046240 generated at 05/31/2006 22:24:13 needed for
thread 1
ORA-00289: suggestion : /app/oracle/PNYTP102/admin/archive11794.arc
ORA-00280: change 5656280046240 for thread 1 is in sequence #11794
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/db_dumps/oracle/PNYTP102/archive1/11794.arc
ORA-00279: change 5656280047319 generated at 05/31/2006 22:29:22 needed for
thread 1
ORA-00289: suggestion : /app/oracle/PNYTP102/admin/archive11795.arc
ORA-00280: change 5656280047319 for thread 1 is in sequence #11795
ORA-00278: log file '/db_dumps/oracle/PNYTP102/archive1/11794.arc' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/db_dumps/oracle/PNYTP102/archive1/11795.arc
ORA-00279: change 5656563507271 generated at 06/01/2006 07:26:43 needed for
thread 1
ORA-00289: suggestion : /app/oracle/PNYTP102/admin/archive11796.arc
ORA-00280: change 5656563507271 for thread 1 is in sequence #11796
ORA-00278: log file '/db_dumps/oracle/PNYTP102/archive1/11795.arc' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/db_dumps/oracle/PNYTP102/archive1/11796.arc
ORA-00279: change 5656564123418 generated at 06/01/2006 10:10:57 needed for
thread 1
ORA-00289: suggestion : /app/oracle/PNYTP102/admin/archive11797.arc
ORA-00280: change 5656564123418 for thread 1 is in sequence #11797
ORA-00278: log file '/db_dumps/oracle/PNYTP102/archive1/11796.arc' no longer
needed for this recovery
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: '/data/oracle/PNYTP102/u01/system_01.dbf'
ORA-01112: media recovery not started
SQL> alter database open read only;
alter database open read only
*
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/data/oracle/PNYTP102/u01/system_01.dbf'
Paul Baumgartel
CREDIT SUISSE
Information Technology
DBA & Admin - NY, KIGA 1
11 Madison Avenue
New York, NY 10010
USA
Phone 212.538.1143
paul.baumgartel@xxxxxxxxxxxxxxxxx
www.credit-suisse.com
-----Original Message-----
From: David Sharples [mailto:davidsharples@xxxxxxxxx]
Sent: Thursday, June 01, 2006 4:05 PM
To: paul.baumgartel@xxxxxxxxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Open read only after incomplete recovery?
yes it is possible, can be used to see how far down a recovery process you are.
Is this a RAC database?
On 01/06/06, Baumgartel, Paul < paul.baumgartel@xxxxxxxxxxxxxxxxx
<mailto:paul.baumgartel@xxxxxxxxxxxxxxxxx> > wrote:
Oracle 9.2.0.6 <http://9.2.0.6> on 64-bit Solaris 5.8.
We have a BCV setup to maintain a copy of a production database on another
server. The BCV is updated every night. Tablespaces are placed in backup mode
beforehand and taken out after.
I am told by other DBAs that they have successfully performed the following:
startup mount
recover database using backup controlfile until cancel
...apply a few logs
... cancel
alter database open read only;
We do NOT want to open resetlogs. The purpose of this exercise is to see if we
can use the BCV copy for reporting, but still be able to recover it further if
need be.
==============================================================================
Please access the attached hyperlink for an important electronic communications
disclaimer:
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
==============================================================================
|

|