Logical Standby Database Question 2006-06-12 - By Mark Strickland
Followup: Cascaded standby vs non-cascaded standby configuration:
This is just a followup to let the list know that we chose a Cascaded
configuration and implemented it in Production Saturday evening. So far,
all is well. Ran into one bug that seems to be specific to 10.1.0.3 -- if
the Standby Redo Logs in the physical standby have more than one log member,
the alert log will report ORA-00322 (See ORA-00322.ora-code.com) and ORA-00312 (See ORA-00312.ora-code.com). The solution was simply
to re-create the Standby Redo Logs with a single member. It will be some
weeks before reporting users get migrated over so, at the moment, our new
logical standby database is just running along happily hoovering in the
archived logs. 10g Data Guard is a wonderful thing.
Regards,
Mark Strickland
Next Online Technologies
Seattle, WA
On 6/2/06, Mark Strickland <strickland.mark@(protected)> wrote:
>
> Thank you for the responses: Yes, we've considered the impact if the
> physical standby is out of commission for an extended time. The end-users
> can live without their reporting database for a day. Mission-critical
> reporting is going to stay on the primary. I'm looking for a best practice
> if there is one and, if anyone has actually implemented a cascaded
> configuration, have there been any gotchas.
>
> Mark
>
>
> On 6/2/06, David Sharples <davidsharples@(protected)> wrote:
>
> > well yes that's what I implied, ab it useless for reporting purposes if
> > you dont have all the data to report on.
> >
> >
> > On 02/06/06, Ghassan Salem <salem.ghassan@(protected) > wrote:
> > >
> > > David,
> > > the log stdby will still be available, but not updated, until the
> > > physical one resumes sending it's redologs.
> > >
> >
>
Followup: Cascaded standby vs non-cascaded standby configuration:<br>
<br>
This is just a followup to let the list know that we chose a Cascaded
configuration and implemented it in Production Saturday evening.
So far, all is well. Ran into one bug that seems to be specific
to <a href="http://10.1.0.3">10.1.0.3</a> -- if the Standby Redo Logs in the
physical standby have
more than one log member, the alert log will report ORA-00322 (See ORA-00322.ora-code.com) and
ORA-00312 (See ORA-00312.ora-code.com). The solution was simply to re-create the Standby Redo
Logs with a single member. It will be some weeks before reporting
users get migrated over so, at the moment, our new logical standby
database is just running along happily hoovering in the archived
logs. 10g Data Guard is a wonderful thing.<br>
<br>
Regards,<br>
Mark Strickland<br>
Next Online Technologies<br>
Seattle, WA<br><br>
<br><div><span class="gmail_quote">On 6/2/06, <b class="gmail_sendername">Mark
Strickland</b> <<a href="mailto:strickland.mark@(protected)">strickland.mark
@(protected)</a>> wrote:</span><blockquote class="gmail_quote" style="border
-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;">
<div>Thank you for the responses: Yes, we've considered the impact if
the physical standby is out of commission for an extended time.
The end-users can live without their reporting database for a
day. Mission-critical reporting is going to stay on the
primary. I'm looking for a best practice if there is one and, if
anyone has actually implemented a cascaded configuration, have there
been any gotchas.<br></div><div><span class="sg">
<br>
Mark<br>
<br><br></span></div><div><div></div><div><span class="q"><span class="gmail
_quote">On 6/2/06, <b class="gmail_sendername">David Sharples</b> <<a href=
"mailto:davidsharples@(protected)" target="_blank" onclick="return top.js
.OpenExtLink(window,event,this)">
davidsharples@(protected)</a>> wrote:</span></span></div><div><span class="e"
id="q_10b9501764a8e18d_4"><blockquote class="gmail_quote" style="border-left:
1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>well yes that's what I implied, ab it useless for reporting purposes if
you dont have all the data to report on.</div><div><span><br><br>
<div><span class="gmail_quote">On 02/06/06, <b class="gmail_sendername">Ghassan
Salem</b> <<a href="mailto:salem.ghassan@(protected)" target="_blank" onclick=
"return top.js.OpenExtLink(window,event,this)">salem.ghassan@(protected)
</a>> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204
); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">
<div>David,<br>the log stdby will still be available, but not updated, until
the physical one resumes sending it's redologs.</div></blockquote></div>
</span></div></blockquote></span></div><div></div><br>
</div></blockquote></div><br>
|
|
