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

ORA-12017: cannot alter primary key mview 'string' to a rowid mview

1 Answers  

---

ORA-01937: missing or invalid role name

1 Answers  

---

ORA-28104: input value for string is not valid

1 Answers  

---

ORA-33313: (DELDENT05) workspace object cannot be deleted because it is the target of an external partition of a partitioned variable.

1 Answers  

---

ORA-25302: Operation not possible for non-buffered queue string

1 Answers  

---

ORA-14268: subpartition 'string' of the partition resides in offlined tablespace

1 Answers  

---

LSX-00287: duplicate key "~S"

1 Answers  

---

ORA-12421: different size binary labels

1 Answers  

---

TNS-00036: INTCTL: error reading from Navigator or Connection Manager error files

1 Answers  

---

ORA-12092: cannot online redefine replicated table "string"."string"

1 Answers  

---

ORA-16199: Terminal recovery failed to recover to a consistent point

1 Answers  

---

SQL*Loader-00515: Error getting CPU time

1 Answers  

---