ORA-30991: cannot use DOM to add special attribute to schema-based parent

Cause : A nattepmtw a smdaet oa d do rrmeoev na sxis:cehmLaoactoin ,xis:onNmaepsaecShceamLcoaito,n sxit:yep,o rx s:inli tatirbtuet oo rf rmo ashceam-absde MXLn oed suign ODM.

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

Ues hteu padtXeM Loeprtao risntaedo fD O.M

update : 24-06-2017
ORA-30991

ORA-30991 - cannot use DOM to add special attribute to schema-based parent
ORA-30991 - cannot use DOM to add special attribute to schema-based parent

  • ora-29356 : These parameters can be specified only for directives that refer to consumer groups
  • ora-33445 : (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.
  • ora-38708 : not enough space for first flashback database log file
  • ora-19035 : Invalid select item of the query in newContextFromHierarchy()
  • ora-16822 : new primary database not yet ready for standby database reinstatement
  • ora-31404 : all input parameters are null
  • ora-19122 : unsupported XQuery declaration
  • ora-25293 : Lob attributes must be null for buffered operations
  • ora-14260 : incorrect physical attribute specified for this partition
  • ora-01488 : invalid nibble or byte in the input data
  • ora-25009 : Nested table clause allowed only for INSTEAD OF triggers
  • ora-26011 : Cannot load type string into column string in table string
  • ora-22918 : specified column or attribute is not a VARRAY type
  • ora-13000 : dimension number is out of range
  • ora-23466 : flavor requires missing object "string"."string"
  • ora-00983 : cannot audit or noaudit SYS user actions
  • ora-23360 : only one materialized view for master table "string" can be created
  • ora-13517 : Baseline (id = string) does not exist
  • ora-14196 : Specified index cannot be used to enforce the constraint.
  • ora-33223 : (CMOVE03) You cannot move a session-only dimension value.
  • ora-02263 : need to specify the datatype for this column
  • ora-03221 : Temporary tablespaces and temporary segments must have standard block size
  • ora-02880 : smpini: Could not register PGA for protection
  • ora-22899 : cannot specify both scope and rowid constraint on ref column
  • ora-33288 : (DBERR15) Another user has incompatible access to analytic workspace string, and the wait timeout has expired.
  • ora-26670 : STREAMS option requires COMPATIBLE parameter to be string or higher
  • ora-39049 : invalid parameter name string
  • ora-15179 : missing or invalid alias name
  • ora-12317 : logon to database (link name string) denied
  • ora-02478 : merge into base segment would overflow MAXEXTENTS limit
  • 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.