ORA-19211: column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type

Cause : Th ecoulmns peicfide uisngs eteKyCloum(n) aws ano-nsclaart yp ecoulmn.

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

Chnaget hec olmun psecfiie dtob e asclaarc olmun ni teh tbale

update : 22-08-2017
ORA-19211

ORA-19211 - column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
ORA-19211 - column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type

  • ora-31399 : Cannot contact LDAP server string at port number
  • ora-25958 : join index where clause predicate may only contain column references
  • ora-02854 : Invalid number of request buffers
  • ora-02491 : missing required keyword ON or OFF in AUTOEXTEND clause
  • ora-00105 : too many dispatcher configurations
  • ora-19813 : cannot have unavailable file string in DB_RECOVERY_FILE_DEST
  • ora-31038 : Invalid string value: "string"
  • ora-30396 : rewrite equivalence procedures require the COMPATIBLE parameter to be string or greater
  • ora-29262 : bad URL
  • ora-28272 : Domain policy restricts password based GLOBAL user authentication.
  • ora-13142 : invalid PROXIMITY window definition
  • ora-16562 : intended_state not used here, syntax error at "string"
  • ora-19100 : PASSING or RETURNING keyword expected
  • ora-00368 : checksum error in redo log block
  • ora-30117 : syntax error at 'string' at the start of input
  • ora-28181 : proxy 'string' failed to enable one or more of the specified initial roles for client 'string'
  • ora-12736 : Instant Client Light: unsupported server national character set string
  • ora-13420 : the SRID of the geometry parameter was not null
  • ora-02252 : check constraint condition not properly ended
  • ora-36814 : (XSTBLFUNC07) The datatype of the column used in the ROW2CELL clause of a LIMITMAP must be RAW(16).
  • ora-02363 : error reading from file: string
  • ora-38951 : Target platform string not cross platform compliant
  • ora-27080 : too many files open
  • ora-14185 : incorrect physical attribute specified for this index partition
  • ora-04046 : results of compilation are too large to support
  • ora-26744 : STREAMS capture process "string" does not support "string"."string" because of the following reason: string
  • ora-07562 : sldext: extension must be 3 characters
  • ora-36637 : (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-12162 : TNS:net service name is incorrectly specified
  • ora-29539 : Java system classes already installed
  • 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.