Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16129: unsupported dml encountered
- 1 Answers
- 3101 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-38418: ADT associated with the attribute set string does not exist
ORA-01772: Must specify a value for LEVEL
ORA-01262: Stat failed on a file destination directory
ORA-16643: unable to determine location of broker configuration files
TNS-12510: TNS:database temporarily lacks resources to handle the request
TNS-00115: Could not allocate pump global buffers
RMAN-08046: channel string: starting compressed full datafile backupset
RMAN-06412: no proxy copy channel found
ORA-02262: ORA-string occurs while type-checking column default value expression
ORA-16753: Resource guard could not open standby database
PCB-00311: Datatype equivalencing is an Oracle extension
RMAN-06559: MAXSIZE must be larger than 1 kb
Oracle Errors 
