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 : 29-04-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-25245 : agent name cannot be specified if address is a single-consumer queue or an exception queue
  • ora-27146 : post/wait initialization failed
  • ora-08117 : Index Organized Table operation released its block pin
  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • ora-24234 : unable to get source of string "string"."string", insufficient privileges or does not exist
  • ora-00203 : using the wrong control files
  • ora-39019 : invalid operation type string
  • ora-19028 : Invalid ADT parameter passed to toObject() function
  • ora-03280 : invalid DATAFILE filename specified
  • ora-12453 : label string already exists
  • ora-06521 : PL/SQL: Error mapping function
  • ora-14254 : cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table
  • ora-28560 : error in configuration of agent process
  • ora-19679 : RMAN configuration number string is outside valid range of 1 through string
  • ora-36280 : (XSCGMDLAGG08) Valueset workspace object does not contain values of any dimension of the current model.
  • ora-40287 : invalid data for model - cosine distance out of bounds
  • ora-30500 : database open triggers and server error triggers cannot have BEFORE type
  • ora-27004 : invalid blocksize specified
  • ora-23618 : Generation of script string is not complete.
  • ora-01526 : error in opening file 'string'
  • ora-25954 : missing primary key or unique constraint on dimension
  • ora-25534 : _MEAN_TIME_TO_CLUSTER_AVAILABILITY is specified
  • ora-12721 : operation cannot execute when other sessions are active
  • ora-13435 : GeoRaster metadata dimension inconsistent
  • ora-12733 : regular expression too long
  • ora-19767 : missing TRACKING keyword
  • ora-16542 : unrecognized operation
  • ora-06903 : CMX: cannot read transport address of remote application
  • ora-19570 : file number string is outside valid range of 1 through string
  • ora-29801 : missing RETURN keyword
  • 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.