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 : 27-04-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-13485 : error occurred during compression or decompression: string
  • ora-32058 : operation restricted to SYSDBA users
  • ora-19320 : Host name not specified in HTTP URL
  • ora-19224 : XP0004 - XQuery static type mismatch: expected - string got - string
  • ora-24431 : Statement does not exist in the cache
  • ora-06031 : NETDNT: connect failed, unrecognized object name
  • ora-00444 : background process "string" failed while starting
  • ora-24347 : Warning of a NULL column in an aggregate function
  • ora-16409 : Archive log switchover reference number mismatch
  • ora-29299 : Invalid handle for piecewise compress or uncompress
  • ora-12814 : only one CACHE or NOCACHE clause may be specified
  • ora-22278 : must update the LOB only through the LOB buffers
  • ora-25533 : FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified
  • ora-02297 : cannot disable constraint (string.string) - dependencies exist
  • ora-24231 : database access descriptor (DAD) string not found
  • ora-38796 : Not enough flashback database log data to undo FLASHBACK.
  • ora-19270 : XP0050 - treat failed - expected string got string
  • ora-04014 : descending sequences that CYCLE must specify MINVALUE
  • ora-34802 : (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.
  • ora-13333 : invalid LRS measure
  • ora-30006 : resource busy; acquire with WAIT timeout expired
  • ora-31628 : error getting worker process exception
  • ora-24356 : internal error while converting from to COBOL display type.
  • ora-12680 : Native services disabled but required
  • ora-24011 : cannot drop QUEUE, string should be stopped first
  • ora-01409 : NOSORT option may not be used; rows are not in ascending order
  • ora-28671 : UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
  • ora-33267 : (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it
  • ora-19210 : column 'string', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table 'string'
  • ora-19715 : invalid format string for generated name
  • 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.