Logical standby problem 2005-09-02 - By Johnson, George
You need to look at the DBMS_LOGSTDBY package it has lots of
functionality to help you deal with "troublesome" statements. We spent about
5-6 weeks on our first logical writing a custom package to be called by the
logical apply processes to attempt deal all sorts of re-occurring
statements, like tablespaces going in and out backups, missing object alerts
on the various skip statements. Prior to this we were spending about 2-3
hours a day fighting with the logical and stuck statements! It's well worth
trying to automate the logical apply process as much as possible if you can
using the DBMS_LOGSTDBY, we now spend about 30 secs a day, just making sure
it's OK.
Rgds
-- --Original Message-- --
From: rjamya [mailto:rjamya@(protected)]
Sent: 01 Sep 2005 19:59
To: Oracle Discussion List
Subject: Logical standby problem
A colleague is trying to create a logical standby database. During apply, it
is getting stuck on
LOGSTDBY stmt: grant select,insert on sys.ora_temp_1_ds_24148 to "SYSTEM"
LOGSTDBY status: ORA-00942 (See ORA-00942.ora-code.com): table or view does not exist
LOGSTDBY Apply process P004 pid=27 OS id=913594 stopped
Now we all know that this temp tablename is generated when collecting stats.
System owns the package that generated the stats in the actual database. Is
there a way to resolve this? I have no clue about it and Metalink has been
less than helpful. A TAR has been loggged, but I needed it to be run by you
all.
Any pointers are greatly appreciated.
Raj
-- ---- ---- ---- ---- ---- --
select standard_disclaimer from company_requirements where category =
'MANDATORY';
****************************************************************************
This message contains confidential information and is intended only
for the individual or entity named. If you are not the named addressee
you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the contents of this
message which arise as a result of e-mail transmission.
If verification is required please request a hard-copy version.
This message is provided for informational purposes and should not
be construed as an invitation or offer to buy or sell any securities or
related financial instruments.
GAM operates in many jurisdictions and is
regulated or licensed in those jurisdictions as required.
****************************************************************************
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1106" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=035403807-02092005><FONT face=Arial color=#0000ff
size=2> You
need to look at the DBMS_LOGSTDBY package it has lots of functionality to help
you deal with "troublesome" statements. We spent about 5-6 weeks on our first
logical writing a custom package to be called by the logical apply processes to
attempt deal all sorts of re-occurring statements, like tablespaces going in
and
out backups, missing object alerts on the various skip statements. Prior to
this
we were spending about 2-3 hours a day fighting with the logical and stuck
statements! It's well worth trying to automate the logical apply process
as
much as possible if you can using the DBMS_LOGSTDBY, we now spend about 30 secs
a day, just making sure it's OK.</FONT></SPAN></DIV>
<DIV><SPAN class=035403807-02092005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN
class=035403807-02092005>
<FONT face=Arial color=#0000ff size=2>Rgds</FONT></SPAN></DIV>
<DIV><SPAN class=035403807-02092005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV></DIV>
<DIV><FONT face=Tahoma size=2>-- --Original Message-- --<BR><B>From:</B> rjamya
[mailto:rjamya@(protected)] <BR><B>Sent:</B> 01 Sep 2005 19:59<BR><B>To:</B>
Oracle Discussion List<BR><B>Subject:</B> Logical standby
problem<BR><BR></DIV></FONT>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">A colleague is trying to create a
logical standby database. During apply, it is getting stuck on
<BR><BR>LOGSTDBY stmt: grant select,insert on sys.ora_temp_1_ds_24148 to
"SYSTEM"<BR>LOGSTDBY status: ORA-00942 (See ORA-00942.ora-code.com): table or view does not
exist<BR>LOGSTDBY Apply process P004 pid=27 OS id=913594 stopped<BR><BR>Now
we
all know that this temp tablename is generated when collecting stats. System
owns the package that generated the stats in the actual database. Is there a
way to resolve this? I have no clue about it and Metalink has been less than
helpful. A TAR has been loggged, but I needed it to be run by you
all.<BR><BR>Any pointers are greatly appreciated.<BR>Raj
<BR>-- ---- ---- ---- ---- ---- --<BR>select standard_disclaimer from
company_requirements where category =
'MANDATORY';<BR></BLOCKQUOTE><FONT SIZE=3><BR>
<BR>
****************************************************************************<BR>
This message contains confidential information and is intended only <BR>
for the individual or entity named. If you are not the named addressee<BR>
you should not disseminate, distribute or copy this e-mail. <BR>
Please notify the sender immediately by e-mail if you have received <BR>
this e-mail by mistake and delete this e-mail from your system.<BR>
E-mail transmission cannot be guaranteed to be secure or error-free<BR>
as information could be intercepted, corrupted, lost, destroyed, arrive<BR>
late or incomplete, or contain viruses. The sender therefore does not<BR>
accept liability for any errors or omissions in the contents of this <BR>
message which arise as a result of e-mail transmission. <BR>
If verification is required please request a hard-copy version.<BR>
This message is provided for informational purposes and should not<BR>
be construed as an invitation or offer to buy or sell any securities or<BR>
related financial instruments.<BR>
GAM operates in many jurisdictions and is <BR>
regulated or licensed in those jurisdictions as required.<BR>
****************************************************************************<BR>
</FONT>
</BODY></HTML>
|
|
