ORA-19006: XMLType TYPE storage option not appropriate for storage type

Cause : Teh YTP Eotpino acno nyl eb sue di ncsaeo fO BEJC TRLEAITOANLs troaeg potoin

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

Rmeoev hteT YEP potoino rs pceiyf na BOJCETR EALTOINLA tsoarg efro hteX MTLyep oclmun

update : 27-06-2017
ORA-19006

ORA-19006 - XMLType TYPE storage option not appropriate for storage type
ORA-19006 - XMLType TYPE storage option not appropriate for storage type

  • ora-19673 : error during proxy file string
  • ora-27020 : named devices not supported
  • ora-24130 : table string does not exist
  • ora-16508 : channel handle not initialized
  • ora-12036 : updatable materialized view log is not empty, refresh materialized view
  • ora-19018 : Invalid character in XML tag 'string'
  • ora-13529 : Error occurred when flushing AWR table group
  • ora-24143 : invalid evaluation context name
  • ora-36832 : (XSLMGEN02) View token cannot be greater than 4000 bytes
  • ora-13290 : the specified unit is not supported
  • ora-01574 : maximum number of concurrent transactions exceeded
  • ora-40106 : positive target value not specified for computing Lift
  • ora-31481 : change source string is not a HotLog change source
  • ora-28502 : internal communication error on heterogeneous database link
  • ora-13108 : spatial table string not found
  • ora-27504 : IPC error creating OSD context
  • ora-29844 : duplicate operator name specified
  • ora-28040 : No matching authentication protocol
  • ora-26660 : Invalid action context value for string
  • ora-38904 : DML error logging is not supported for LOB column "string"
  • ora-01329 : unable to truncate required build table
  • ora-24036 : invalid SORT_ORDER column string specified for queue table
  • ora-01204 : file number is string rather than string - wrong file
  • ora-31028 : Resource metadata length string exceeded maximum length string
  • ora-24850 : failed to startup shared subsystem
  • ora-13181 : unable to determine length of column string_SDOINDEX.SDO_CODE
  • ora-01938 : IDENTIFIED BY must be specified for CREATE USER
  • ora-01268 : invalid TEMPFILE clause for alter of permanent TABLESPACE
  • ora-01375 : Corrupt logfile string recovered
  • ora-02776 : Value for request done signal exceeds maximum
  • 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.