ORA-16129: unsupported dml encountered
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
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-13606: the specified task parameter element string is out of range for parameter string.
ORA-00040: active time limit exceeded - call aborted
QSM-02147: default date format is sensitive to session settings
TNS-12652: String truncated
NNL-00532: set|show forwarding_available [<on|off>] [<server_list>] : enable, disable or show server request forwarding
PLS-00245: Formals used in the 'parameters' clause must appear exactly once
ORA-25442: too many column values for table alias: string
SQL-02157: Source or destination lob is invalid
ORA-02264: name already used by an existing constraint
RMAN-06477: configuration value length exceeds 1024
ORA-06521: PL/SQL: Error mapping function
ORA-25183: index-organized table top index segment is in a different tablespace