.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
standbys and unrecoverable operations

standbys and unrecoverable operations

2005-11-15       - By Bobak, Mark
Reply:     1     2     3  

Josh,

I'm not a standby or DataGuard expert, but, think about what the
unrecoverable change # represents.  It's the SCN at which  the last
unrecoverable operation occurred on that datafile.  So, if the primary
is ahead of the standby, that means there are operations which have
occurred on the primary which did not propogate to the standby.  This is
a corruption waiting to happen.  If you activate the standby and a
datablock is accessed that was loaded unrecoverable on the primary,
you'll encounter an ORA-26040 (See ORA-26040.ora-code.com).

So, I assume (don't have a standby setup handy to confirm it) that the
default safe position is that they are equal, since, when you clone from
the primary to initially create the standby, they'd (presumably) be
equal.  At that point, the only way for them to get out of sync is if
you do an unrecoverable (aka nologging) load in the primary database.

Corrections welcome from those with actual DG and standby experience!
;-)

Hope that helps,

-Mark

PS  Note that in 9i (can't remember if it was 9.0.1 or 9.2.0
intorduction) you can do ALTER DATABASE FORCE_LOGGING=TRUE; and
everything will log, even if people try to do nologging loads.

__ ____ ____ ____ ____ ____ ____

From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)] On Behalf Of Josh Collier
Sent: Tuesday, November 15, 2005 4:52 PM
To: oracle-l@(protected)
Subject: standbys and unrecoverable operations


Greetings,

The Oracle documentation says that if the unrecoverable_change# for a
datafile reported (v$datafile) by the primary is greater than that
reported by the standby then you will need to recover that datafile (by
copying it over from the primary) in order to avoid block corruption
errors if the standby is activated.

Does this also hold if the unrecoverable_change# are identical?

have a good day,

Josh C.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2769" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=375435221-15112005><FONT face=Arial
color=#0000ff size=2>Josh,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=375435221-15112005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=375435221-15112005><FONT face=Arial
color=#0000ff size=2>I'm not a standby or DataGuard expert, but, think about
what the unrecoverable change # represents.&nbsp; It's the SCN at which&nbsp;
the last unrecoverable operation occurred on that datafile.&nbsp; So, if the
primary is ahead of the standby, that means there are operations which have
occurred on the primary which did not propogate to the standby.&nbsp; This is a
corruption waiting to happen.&nbsp; If you activate the standby and a datablock
is accessed that was loaded unrecoverable on the primary, you'll encounter an
ORA-26040 (See ORA-26040.ora-code.com).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=375435221-15112005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=375435221-15112005><FONT face=Arial
color=#0000ff size=2>So, I assume (don't have a standby setup handy to confirm
it) that the default safe position is that they are equal, since, when you
clone
from the primary to initially create the standby, they'd (presumably) be
equal.&nbsp; At that point, the only way for them to get out of sync is if you
do an unrecoverable (aka nologging) load in the primary
database.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=375435221-15112005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=375435221-15112005><FONT face=Arial
color=#0000ff size=2>Corrections welcome from those with actual DG and standby
experience! ;-)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=375435221-15112005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=375435221-15112005><FONT face=Arial
color=#0000ff size=2>Hope that helps,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=375435221-15112005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=375435221-15112005><FONT face=Arial
color=#0000ff size=2>-Mark</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=375435221-15112005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=375435221-15112005><FONT face=Arial
color=#0000ff size=2>PS&nbsp; Note that in 9i (can't remember if it was 9.0.1
or
9.2.0 intorduction) you can do ALTER DATABASE FORCE_LOGGING=TRUE; and
everything
will log, even if people try to do nologging loads.</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)] <B>On Behalf Of </B>Josh
Collier<BR><B>Sent:</B> Tuesday, November 15, 2005 4:52 PM<BR><B>To:</B>
oracle-l@(protected)<BR><B>Subject:</B> standbys and unrecoverable
operations<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=513324921-15112005><FONT face=Arial
size=2>Greetings,</FONT></SPAN></DIV>
<DIV><SPAN class=513324921-15112005><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=513324921-15112005><FONT face=Arial size=2>The Oracle
documentation says that if the unrecoverable_change# for a datafile reported
(v$datafile)&nbsp;by the primary is greater than that reported by the standby
then you will need to recover that datafile (by copying it over from the
primary) in order to avoid block corruption errors if the standby is activated.
</FONT></SPAN></DIV>
<DIV><SPAN class=513324921-15112005><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=513324921-15112005><FONT face=Arial size=2>Does this also hold
if the unrecoverable_change# are identical? </FONT></SPAN></DIV>
<DIV><SPAN class=513324921-15112005><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=513324921-15112005><FONT face=Arial size=2>have a good
day,</FONT></SPAN></DIV>
<DIV><SPAN class=513324921-15112005><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=513324921-15112005><FONT face=Arial size=2>Josh C.
</FONT></SPAN></DIV></BODY></HTML>