Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16129: unsupported dml encountered
- 1 Answers
- 3050 Views
- I also Faced
- E-Mail Answers
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-02436: date or system variable wrongly specified in CHECK constraint
ORA-01605: missing numbers in clause "string" of string
ORA-01215: enabled thread string is missing after CREATE CONTROLFILE
ORA-30002: SYS_CONNECT_BY_PATH function is not allowed here
ORA-24004: invalid column name string in SORT_LIST, should be ENQ_TIME or PRIORITY
ORA-19648: datafile string: incremental-start SCN equals checkpoint SCN
AMD-00131: dimension #string: RDBMS parent column data type not specified
LFI-01515: truncate() failed.
TNS-00293: Trace File Name : string
DRG-10829: feedback id string is longer than the maximum length of string bytes
RMAN-20003: target database incarnation not found in recovery catalog
ORA-04091: table string.string is mutating, trigger/function may not see it
Oracle Errors 
