Re: Logical Standby - dba_logstdby_skip.error
- From: Jason Heinrich <jheinrichdba@xxxxxxxxx>
- To: wellmetus@xxxxxxxxx
- Date: Fri, 15 Jan 2010 10:35:28 -0600
Roger,
I'm not sure about what the documentation is saying there. Maybe I'm not
thinking straight today, but that sounds backwards. From my experience, the
error column simply means that Oracle will skip (or handle through a stored
procedure) only errors on the given object/statement, as opposed to all
matching activity. For example, in the following rows from my
dba_logstdby_skip view, I skip all activity on the KWEYGANDT schema. Any
errors raised from DDL statements are passed to the SKIP_LOGSTDBY_ERROR
procedure, which has special handling for certain errors.
OWNER NAME ERR STATEMENT_OPT PROC
----------- ------ --- --------------- ------------------------------
KWEYGANDT % N DML
KWEYGANDT % N SCHEMA_DDL
% % Y SCHEMA_DDL SYSTEM.SKIP_LOGSTDBY_ERROR
--
Jason Heinrich
On Thu, Jan 14, 2010 at 4:59 PM, Roger Xu <wellmetus@xxxxxxxxx> wrote:
> Hi List,
>
> Oracle doc says that dba_logstdby_skip.error indicates "whether the
> statement should be skipped (Y) or just return errors for the statement
> (N)". What does this really mean?
>
> Below shows that no DML is applied for tables owned by userA and userC. All
> DML are applied for userB except table1 and table2, correct?
>
> SQL> select OWNER, NAME, ERROR, STATEMENT_OPT from dba_logstdby_skip order
> by OWNER;
>
> OWNER NAME ERR STAT
> ------------------------------ ------------------------------ --- ----
> USERA % N DML
> USERB TABLE1 N DML
> USERB TABLE2 N DML
> USERC % N DML
>
> 4 rows selected.
>
> SQL>
>
> Thanks,
>
> Roger Xu
>
Other related posts:
