ORA-22816: unsupported feature with RETURNING clause

Cause : ERUTNRNI Glcuaesi sucrrnelt yon tuspproet dof rboejtct py eoculnm,sL NO Goculnm,sr meto eatlbse ,NIESTRw ti husqbeuyr ,na dNITSAE DFOT irggre.s

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

sU eesaparets lece ttstamene totg tet ehv laeu.s

update : 25-04-2017
ORA-22816

ORA-22816 - unsupported feature with RETURNING clause
ORA-22816 - unsupported feature with RETURNING clause

  • ora-32300 : cannot drop a secondary materialized view "string"."string"
  • ora-06529 : Version mismatch - PL/SQL profiler
  • ora-01715 : UNIQUE may not be used with a cluster index
  • ora-06263 : NETNTT: out of memory in pi_connect
  • ora-31085 : schema "string" already registered
  • ora-25466 : data not specified for variable name: string
  • ora-12044 : invalid CREATE MATERIALIZED VIEW LOG option
  • ora-32121 : Source FILE is null
  • ora-03243 : destination dba overlaps with existing control information
  • ora-06407 : NETCMN: unable to set up break handling environment
  • ora-12216 : TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA
  • ora-16707 : the value of the property string is invalid, valid values are string
  • ora-39105 : Master process string failed during startup. Master error:
  • ora-33454 : (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
  • ora-06712 : TLI Driver: error on accept
  • ora-09702 : sem_acquire: cannot acquire latch semaphore
  • ora-39307 : operation is illegal without an initial clone
  • ora-18002 : the specified outline does not exist
  • ora-14266 : data type or length of an index subpartitioning column may not be changed
  • ora-13628 : Insufficient privileges to access the task belonging to the specified user
  • ora-12457 : security label exceeded maximum allowable length
  • ora-16214 : apply stalled for apply delay
  • ora-10574 : Test recovery did not corrupt any data block
  • ora-29387 : no top-plans found in the pending area
  • ora-07493 : scgrcl: lock manager error.
  • ora-13500 : SYSAUX DATAFILE clause specified more than once
  • ora-00062 : DML full-table lock cannot be acquired; DML_LOCKS is 0
  • ora-02279 : duplicate or conflicting MINVALUE/NOMINVALUE specifications
  • ora-19202 : Error occurred in XML processingstring
  • 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.