Answer / guest

Cause: DML to tables in the SYS schema have been updated and
are not part of a DDL operation. This may be due to some DBA
activity or DML associated with a kernel PL/SQL request that
Logical Standby does not yet support.

Action: Check the DBA_LOGSTDBY_EVENTS table for the name of
the table being processed. Possibly use Log Miner to
understand the transaction, and provide a compensating
transaction on the standby system. Once complete, call
DBMS_LOGSTDBY.SKIP_TRANSACTION with the associated
transaction id, and resume apply.

Please add more information about this Error

LRM-00113: error when processing file 'string'

1 Answers  

---

ORA-02264: name already used by an existing constraint

1 Answers  

---

ORA-37071: You may not execute a parallel OLAP operation against updated but uncommitted AW string.

1 Answers  

---

PLS-01503: The expression in a SET clause must not include a set function

1 Answers  

---

PCB-00575: PLS-number: string

1 Answers  

---

DRG-10502: index string does not exist

1 Answers  

---

RMAN-08006: database registered in recovery catalog

1 Answers  

---

ORA-04099: trigger 'string' is valid but not stored in compiled form

1 Answers  

---

TNS-01406: ID: string

1 Answers  

---

ORA-02878: sou2o: Variable smpdidini overwritten

1 Answers  

---

ORA-33280: (DBERR10) Analytic workspace string cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back.

1 Answers  

---

RMAN-10036: RPC call ok on channel string

1 Answers  

---