Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: dataguard logical standby issue
Edward, if you don't actually need DML and/or DDL for the SYSMAN schema
propogated to the logical standby, then just set the schema to be skipped
and it should be able to move past the statement(s) that are failing.
However, having said that, a few weeks ago, a few transactions for an
already-set-to-skip schema caused SQL Apply to stop. Both DDL and DML for
this schema were set to be skipped and have been all along. I ended up
calling the skip procedure again for that schema and SQL Apply was then able
to move on with its life. The name of the object that your standby is
choking on looks like something that is system-generated and, therefore,
will probably be different in every database where the DDL is run to create
it. Also, you can call the skip_error or skip_transaction procedures or you
can "alter database start logical standby apply skip failed transaction" as
many times as it takes to get past the problem transactions.
BTW, I'm on 10.1.0.5, so whatever I recommend is based on my experiences with logical standby in that version.
Regards,
Mark Strickland
Seattle, WA
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Mar 19 2007 - 11:46:48 CDT
![]() |
![]() |