.ora-code.com

Links
Home
Oracle DBA Forum
Frequent Oracle Errors
TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found'>ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated
Open read only after incomplete recovery?

Open read only after incomplete recovery?

2006-06-01       - By Baumgartel, Paul
Reply:     1     2     3     4     5     6     7     8     9     10     >>  

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 (See ORA-00279.ora-code.com): change 5656280046240 generated at 05/31/2006 22:24:13 needed for
thread 1
ORA-00289 (See ORA-00289.ora-code.com): suggestion : /app/oracle/PNYTP102/admin/archive11794.arc
ORA-00280 (See ORA-00280.ora-code.com): 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 (See ORA-00279.ora-code.com): change 5656280047319 generated at 05/31/2006 22:29:22 needed for
thread 1
ORA-00289 (See ORA-00289.ora-code.com): suggestion : /app/oracle/PNYTP102/admin/archive11795.arc
ORA-00280 (See ORA-00280.ora-code.com): change 5656280047319 for thread 1 is in sequence #11795
ORA-00278 (See ORA-00278.ora-code.com): 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 (See ORA-00279.ora-code.com): change 5656563507271 generated at 06/01/2006 07:26:43 needed for
thread 1
ORA-00289 (See ORA-00289.ora-code.com): suggestion : /app/oracle/PNYTP102/admin/archive11796.arc
ORA-00280 (See ORA-00280.ora-code.com): change 5656563507271 for thread 1 is in sequence #11796
ORA-00278 (See ORA-00278.ora-code.com): 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 (See ORA-00279.ora-code.com): change 5656564123418 generated at 06/01/2006 10:10:57 needed for
thread 1
ORA-00289 (See ORA-00289.ora-code.com): suggestion : /app/oracle/PNYTP102/admin/archive11797.arc
ORA-00280 (See ORA-00280.ora-code.com): change 5656564123418 for thread 1 is in sequence #11797
ORA-00278 (See ORA-00278.ora-code.com): 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 (See ORA-01547.ora-code.com): warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194 (See ORA-01194.ora-code.com): file 1 needs more recovery to be consistent
ORA-01110 (See ORA-01110.ora-code.com): data file 1: '/data/oracle/PNYTP102/u01/system_01.dbf'


ORA-01112 (See ORA-01112.ora-code.com): media recovery not started


SQL> alter database open read only;
alter database open read only
*
ERROR at line 1:
ORA-16004 (See ORA-16004.ora-code.com): backup database requires recovery
ORA-01194 (See ORA-01194.ora-code.com): file 1 needs more recovery to be consistent
ORA-01110 (See ORA-01110.ora-code.com): 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@(protected)
www.credit-suisse.com

-- --Original Message-- --
From: David Sharples [mailto:davidsharples@(protected)]
Sent: Thursday, June 01, 2006 4:05 PM
To: paul.baumgartel@(protected)
Cc: oracle-l@(protected)
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@(protected) <mailto:paul
.baumgartel@(protected)> > 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
==============================================================================

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 6.00.2800.1529" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face="Courier New" color=#0000ff size=2><FONT color=#0000ff size=2>
<P><FONT face=Arial>No, not RAC. Here's the transcript of my latest attempt.
Any
suggestions/corrections welcomed.</FONT></P>
<P><FONT face=Arial>Note that I have also tried this without specifying "using
backup controlfile"--same result.</FONT></P></FONT></FONT></DIV>
<DIV><FONT face="Courier New" color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV><FONT face="Courier New" color=#000080 size=2>SQL&gt; recover database
until cancel using backup controlfile<BR>ORA-00279 (See ORA-00279.ora-code.com): change 5656280046240
generated at 05/31/2006 22:24:13 needed for<BR>thread 1<BR>ORA-00289 (See ORA-00289.ora-code.com):
suggestion
: /app/oracle/PNYTP102/admin/archive11794.arc<BR>ORA-00280 (See ORA-00280.ora-code.com): change
5656280046240
for thread 1 is in sequence #11794</FONT></DIV>
<DIV><FONT face="Courier New" color=#000080></FONT>&nbsp;</DIV><FONT face=Arial
color=#0000ff size=2>
<DIV><BR><FONT face="Courier New" color=#000080>Specify log:
{&lt;RET&gt;=suggested | filename | AUTO |
CANCEL}<BR>/db_dumps/oracle/PNYTP102/archive1/11794.arc<BR>ORA-00279 (See ORA-00279.ora-code.com): change
5656280047319 generated at 05/31/2006 22:29:22 needed for<BR>thread
1<BR>ORA-00289 (See ORA-00289.ora-code.com): suggestion :
/app/oracle/PNYTP102/admin/archive11795.arc<BR>ORA-00280 (See ORA-00280.ora-code.com): change 5656280047319
for thread 1 is in sequence #11795<BR>ORA-00278 (See ORA-00278.ora-code.com): log file
'/db_dumps/oracle/PNYTP102/archive1/11794.arc' no longer<BR>needed for this
recovery</FONT></DIV>
<DIV><FONT face="Courier New" color=#000080></FONT>&nbsp;</DIV>
<DIV><BR><FONT face="Courier New" color=#000080>Specify log:
{&lt;RET&gt;=suggested | filename | AUTO |
CANCEL}<BR>/db_dumps/oracle/PNYTP102/archive1/11795.arc<BR>ORA-00279 (See ORA-00279.ora-code.com): change
5656563507271 generated at 06/01/2006 07:26:43 needed for<BR>thread
1<BR>ORA-00289 (See ORA-00289.ora-code.com): suggestion :
/app/oracle/PNYTP102/admin/archive11796.arc<BR>ORA-00280 (See ORA-00280.ora-code.com): change 5656563507271
for thread 1 is in sequence #11796<BR>ORA-00278 (See ORA-00278.ora-code.com): log file
'/db_dumps/oracle/PNYTP102/archive1/11795.arc' no longer<BR>needed for this
recovery</FONT></DIV>
<DIV><FONT face="Courier New" color=#000080></FONT>&nbsp;</DIV>
<DIV><BR><FONT face="Courier New" color=#000080>Specify log:
{&lt;RET&gt;=suggested | filename | AUTO |
CANCEL}<BR>/db_dumps/oracle/PNYTP102/archive1/11796.arc<BR>ORA-00279 (See ORA-00279.ora-code.com): change
5656564123418 generated at 06/01/2006 10:10:57 needed for<BR>thread
1<BR>ORA-00289 (See ORA-00289.ora-code.com): suggestion :
/app/oracle/PNYTP102/admin/archive11797.arc<BR>ORA-00280 (See ORA-00280.ora-code.com): change 5656564123418
for thread 1 is in sequence #11797<BR>ORA-00278 (See ORA-00278.ora-code.com): log file
'/db_dumps/oracle/PNYTP102/archive1/11796.arc' no longer<BR>needed for this
recovery</FONT></DIV>
<DIV><FONT face="Courier New" color=#000080></FONT>&nbsp;</DIV>
<DIV><BR><FONT face="Courier New" color=#000080>Specify log:
{&lt;RET&gt;=suggested | filename | AUTO | CANCEL}<BR>cancel<BR>ORA-01547 (See ORA-01547.ora-code.com):
warning: RECOVER succeeded but OPEN RESETLOGS would get error
below<BR>ORA-01194 (See ORA-01194.ora-code.com): file 1 needs more recovery to be consistent<BR>ORA-01110 (See ORA-01110.ora-code.com):
data file 1: '/data/oracle/PNYTP102/u01/system_01.dbf'</FONT></DIV>
<DIV><FONT face="Courier New" color=#000080></FONT>&nbsp;</DIV>
<DIV><BR><FONT face="Courier New" color=#000080>ORA-01112 (See ORA-01112.ora-code.com): media recovery not
started</FONT></DIV>
<DIV><FONT face="Courier New" color=#000080></FONT>&nbsp;</DIV>
<DIV><BR><FONT face="Courier New" color=#000080>SQL&gt; alter database open
read
only;<BR>alter database open read only<BR>*<BR>ERROR at line 1:<BR>ORA-16004 (See ORA-16004.ora-code.com):
backup database requires recovery<BR>ORA-01194 (See ORA-01194.ora-code.com): file 1 needs more recovery to
be
consistent<BR>ORA-01110 (See ORA-01110.ora-code.com): data file 1:
'/data/oracle/PNYTP102/u01/system_01.dbf'<BR></FONT>&nbsp;</FONT></DIV>
<DIV>&nbsp;</DIV>
<P><B><FONT face=Arial size=2>Paul Baumgartel</FONT></B> <BR><B><FONT face
=Arial
size=2>CREDIT SUISSE</FONT></B> <BR><FONT face=Arial size=2>Information
Technology</FONT> <BR><FONT face=Arial size=2>DBA &amp; Admin - NY, KIGA
1</FONT> <BR><FONT face=Arial size=2>11 Madison Avenue</FONT> <BR><FONT
face=Arial size=2>New York, NY 10010</FONT> <BR><FONT face=Arial
size=2>USA</FONT> <BR><FONT face=Arial size=2>Phone 212.538.1143</FONT>
<BR><FONT face=Arial size=2>paul.baumgartel@(protected)</FONT> <BR><FONT
face=Arial size=2>www.credit-suisse.com</FONT> </P>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
 <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
 size=2>-- --Original Message-- --<BR><B>From:</B> David Sharples
 [mailto:davidsharples@(protected)]<BR><B>Sent:</B> Thursday, June 01, 2006 4:05
 PM<BR><B>To:</B> paul.baumgartel@(protected)<BR><B>Cc:</B>
 oracle-l@(protected)<BR><B>Subject:</B> Re: Open read only after incomplete
 recovery?<BR><BR></FONT></DIV>yes it is possible, can be used to see how far
 down a recovery process you are.&nbsp;&nbsp;Is this a RAC database?<BR><BR>
 <DIV><SPAN class=gmail_quote>On 01/06/06, <B
 class=gmail_sendername>Baumgartel, Paul</B> &lt;<A
 href="mailto:paul.baumgartel@(protected)">paul.baumgartel@(protected)
.com</A>&gt;
 wrote:</SPAN>
 <BLOCKQUOTE class=gmail_quote
 style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px
solid">Oracle
   <A href="http://9.2.0.6">9.2.0.6</A> on 64-bit Solaris 5.8.<BR><BR>We have
a
   BCV setup to maintain a copy of a production database on another
   server.&nbsp;&nbsp;The BCV is updated every night.&nbsp;&nbsp;Tablespaces
   are placed in backup mode beforehand and taken out after. <BR><BR>I am told
   by other DBAs that they have successfully performed the
   following:<BR><BR>startup mount<BR>recover database using backup
controlfile
   until cancel<BR><BR>...apply a few logs<BR>... cancel<BR><BR>alter database
   open read only; <BR><BR>We do NOT want to open resetlogs.&nbsp;&nbsp;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.<BR></BLOCKQUOTE></DIV></BLOCKQUOTE>
<P>============================================================================
==<br>
Please access the attached hyperlink for an important electronic communications
disclaimer: <br>
<br>
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html<br>
==============================================================================
<br>
</P></BODY></HTML>