ORA-19212: no key columns specified before call to DBMS_XMLSTORE.updateXML()

Cause : Noc olmunsw er espceifeid sa kye cloumsn bfeor eth ecall t oDBSM_XLMSTROE.pudaetXM.L

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

Us eDBSM_XLMSTROE.estKyeCoulmn)( t ospceif yke ycoulmns

update : 20-08-2017

ORA-19212 - no key columns specified before call to DBMS_XMLSTORE.updateXML()
ORA-19212 - no key columns specified before call to DBMS_XMLSTORE.updateXML()

  • ora-36835 : (XSLMGEN05) Dimension string.string!string hierarchy string level string is missing a COLUMNNAME property value
  • ora-36838 : (XSLMGEN08) Dimension string.string!string attribute string is missing a COLUMNNAME property value
  • ora-40301 : invalid cost matrix specification
  • ora-07479 : scgcmn: cannot open or convert lock.
  • ora-15046 : ASM file name 'string' is not in single-file creation form
  • ora-29500 : NAMED keyword is invalid in CREATE JAVA CLASS
  • ora-25350 : maximum number of concurrent transaction branches exceeded
  • ora-14036 : partition bound value too large for column
  • ora-29657 : class defined in EXTERNAL NAME clause is used in another subtype
  • ora-02876 : smpini: Unable to attach to shared memory for PGA
  • ora-29343 : user string (mapped from user string) does not exist in the database
  • ora-27513 : parameter string contains invalid value string
  • ora-39163 : A sample size of string is invalid.
  • ora-31055 : A null XMLType element cannot be inserted into RESOURCE_VIEW
  • ora-19769 : missing FILE keyword
  • ora-27036 : translation error, unable to expand file name
  • ora-01508 : cannot create database; error in file 'string' at line string
  • ora-28048 : database is a member of multiple enterprise domains in OID
  • ora-36650 : (XSDUNION10) Concat dimension workspace object cannot be changed to UNIQUE. Leaves workspace object and workspace object share the value number.
  • ora-02284 : duplicate INCREMENT BY specifications
  • ora-14324 : values being added already exist in DEFAULT partition
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-39093 : FLASHBACK automatically enabled to preserve database integrity.
  • ora-13017 : unrecognized line partition shape
  • ora-19627 : cannot read backup pieces during control file application
  • ora-15031 : disk specification 'string' matches no disks
  • ora-23387 : replication parallel push dequeue error
  • ora-29970 : Specified registration id does not exist
  • ora-07400 : slemtr: translated name for the message file is too long.
  • ora-33003 : (XSAGDIMDROP) workspace object, to be transformed during data load, must be a base dimension and not otherwise referenced in the AGGMAP.
  • 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.