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

RMAN-08150: created global script string

1 Answers  

---

ORA-36188: (XSAGGR16) AGGREGATE read a value less than 1 out of COUNTVAR variable workspace object. Either the values of the COUNTVAR variable are stored improperly, or there is problem in AGGREGATE. If no one has modified the values in this COUNTVAR, contact Oracle customer support.

1 Answers  

---

ORA-30176: invalid format code used in the format string

1 Answers  

---

SQL*Loader-00436: error converting GUID

1 Answers  

---

ORA-28044: unsupported directory type

1 Answers  

---

ORA-32010: cannot find entry to delete in SPFILE

1 Answers  

---

NZE-29177: certificate serial number is not in CRL

1 Answers  

---

ORA-23343: no match for specified conflict resolution information

1 Answers  

---

ORA-01687: specified logging attribute for tablespace 'string' is same as the existing

1 Answers  

---

RMAN-08580: channel string: starting datafile copy

1 Answers  

---

ORA-13406: null or invalid GeoRaster object for output

1 Answers  

---

ORA-24158: invalid table alias

1 Answers  

---