Logical Standby Apply Fail with ORA-02443 (Doc ID 1528254.1)

Last updated on AUGUST 06, 2014

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.4 [Release 10.2 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 7th-Aug-2014***

Symptoms

 Logical Standby Apply will terminate with  "ORA-02443"   for any opeartion(like DROP CONSTRAINT) done on SYSTEM generated Constraint because the constraint name is different in primary and logical Standby. Its a system generated constraint name.

Mon Feb 11:56:02 2013
LOGSTDBY status: ORA-02443: Cannot drop constraint - nonexistent constraint
LOGSTDBY Apply process P004 pid=28 OS id=2500 stopped
Mon Feb 11 11:56:05 2013
Errors in file d:\databases\cherry\bdump\cherry_lsp0_1236.trc:
ORA-12801: error signaled in parallel query server P004
ORA-02443: Cannot drop constraint - nonexistent constraint

LOGSTDBY Analyzer process P003 pid=24 OS id=428 stopped
LOGSTDBY Apply process P007 pid=31 OS id=3452 stopped
LOGSTDBY Apply process P008 pid=32 OS id=1116 stopped
LOGSTDBY Apply process P006 pid=30 OS id=140 stopped


--------------"Primary"------------

SQL> select CONSTRAINT_NAME,CONSTRAINT_TYPE from user_constraints where TABLE_NAME='T1';

CONSTRAINT_NAME C
-----------------
SYS_C002836 P

 

--------------"Logical Standby"-----------------


SQL> select CONSTRAINT_NAME,CONSTRAINT_TYPE from user_constraints where TABLE_NAME='T1';

CONSTRAINT_NAME C
------------------
SYS_C002859 P

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms