ORA-16129: unsupported dml encountered

Cause : DM Ltot abels ni teh SSY shcem ahaev been pudaetd nad rae ont aprto f aDD Lopreatoin.T hi sma ybed uet o osmeD BAa ctviit yorD MLa sscoiaetd iwtha krene lPLS/QLr eqeustt ha tLoigca lStnadb ydose nto yte spupotr.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Chcek hte BDA_OLGSDTBYE_VETNS atbl efo rth enaem o fth etalbe ebin gprcoesesd.P osisbl yus eLo gMienr ot udnertsan dth etrnasatcio,n adn porvied ac omepnstain gtrnasatcio nont hes tadnbys ysetm.O nc ecopmleet, acllD BM_SLOSGTDYB.SIKP_RTANASCTOIN iwtht hea sscoiaetd rtanasctoin di, nad ersuem apply.

update : 27-04-2017
ORA-16129

ORA-16129 - unsupported dml encountered
ORA-16129 - unsupported dml encountered

  • ora-02054 : transaction string in-doubt
  • ora-29834 : REF datatype not supported with operators
  • ora-01952 : system privileges not granted to 'string'
  • ora-26683 : invalid value for value_type
  • ora-16714 : the value of property string is inconsistent with the database setting
  • ora-12989 : invalid value for checkpoint interval
  • ora-22801 : invalid object row variable
  • ora-14081 : new partition name must differ from the old partition name
  • ora-29529 : invalid function or method call string in trigger string
  • ora-39601 : Hash key is required.
  • ora-30725 : JDWP-based debugging is not yet available
  • ora-13390 : error in spatial analysis and mining function: [string]
  • ora-19248 : XQ0028 - invalid node in document constructor
  • ora-23447 : missing user parameter value
  • ora-06024 : NETASY: VTM error
  • ora-00201 : control file version string incompatible with ORACLE version string
  • ora-22891 : cannot have multiple columns in REF constraint
  • ora-15048 : ASM internal files cannot be deleted
  • ora-29310 : database is not open, or opened as a clone
  • ora-27143 : OS system call failure
  • ora-02038 : define is not allowed for array type
  • ora-01224 : group number in header string does not match GROUP string
  • ora-07279 : spcre: semget error, unable to get first semaphore set.
  • ora-31062 : Cannot delete an unsaved resource
  • ora-16080 : invalid LogMiner session string for APPLY
  • ora-24809 : amount specified will not fit in the lob buffers
  • ora-13632 : The user cancelled the current operation.
  • ora-00164 : distributed autonomous transaction disallowed within migratable distributed transaction
  • ora-34000 : (MODCOMP13) You cannot use both workspace object and workspace object as model dimensions, because they are both surrogates of dimension workspace object.
  • ora-29917 : cannot lock a table which gets its rows from a collection operand
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.