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 : 19-08-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-08412 : error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message
  • ora-12464 : invalid characters in label component string
  • ora-24043 : destination string uses a reserved name, names with AQ$_ prefix are not valid
  • ora-16824 : Fast-Start Failover and other warnings detected for the database
  • ora-01203 : wrong incarnation of this file - wrong creation SCN
  • ora-30733 : cannot specify rowid constraint on scoped ref column
  • ora-24153 : rule set string.string already exists
  • ora-39178 : cannot perform estimate on metadata only jobs
  • ora-01682 : read-only DB cannot allocate temporary space in tablespace string
  • ora-12417 : database object "string" not found
  • ora-12451 : label not designated as USER or DATA
  • ora-31230 : DBMS_LDAP: unable to dynamically allocate additional memory
  • ora-13182 : failed to read element string.string.string
  • ora-24182 : attribute number specified does not exist
  • ora-24067 : exceeded maximum number of subscribers for queue string
  • ora-12022 : materialized view log on "string"."string" already has rowid
  • ora-21602 : operation does not support the specified typecode
  • ora-00053 : maximum number of enqueues exceeded
  • ora-26523 : rpc termination error
  • ora-01249 : archiving not allowed in a clone database
  • ora-12704 : character set mismatch
  • ora-38861 : flashback recovery stopped before reaching recovery target
  • ora-22289 : cannot perform string operation on an unopened file or LOB
  • ora-02329 : column of datatype string cannot be unique or a primary key
  • ora-30682 : improper value for argument OPTION_FLAGS
  • ora-31219 : DBMS_LDAP: PL/SQL - Invalid LDAP notypes.
  • ora-01533 : cannot rename file 'string'; file does not belong to tablespace
  • ora-02254 : DEFAULT not allowed here
  • ora-12632 : Role fetch failed
  • ora-31447 : cannot create change tables in the SYS schema
  • 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.