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 : 24-05-2017

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

  • ora-24755 : OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported
  • ora-01115 : IO error reading block from file string (block # string)
  • ora-01189 : file is from a different RESETLOGS than previous files
  • ora-00289 : suggestion : string
  • ora-06559 : wrong datatype requested, string, actual datatype is string
  • ora-00720 : ALTER DATABASE RESET COMPATIBILITY command has been de-supported
  • ora-24123 : feature string is not yet implemented
  • ora-29306 : datafile string is not online
  • ora-15197 : suppressing string additional ASM messages
  • ora-12719 : operation requires database is in RESTRICTED mode
  • ora-32114 : Cannot perform operation on a null LOB
  • ora-15114 : missing or invalid ASM file name
  • ora-40211 : algorithm name string is invalid
  • ora-14187 : partitioning method for LOCAL index is inconsistent with that of the underlying table
  • ora-07741 : slemop: $OPEN failure
  • ora-26082 : load of overlapping segments on table string.string is not allowed
  • ora-26503 : internal RepAPI operation failure on object string.string
  • ora-19903 : test recovery not allowed when recovering to new incarnation
  • ora-10630 : Illegal syntax specified with SHRINK clause
  • ora-02020 : too many database links in use
  • ora-24331 : user buffer too small
  • ora-24900 : invalid or unsupported mode paramater passed in call
  • ora-14268 : subpartition 'string' of the partition resides in offlined tablespace
  • ora-23501 : refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0
  • ora-01576 : The instance string is not enabled
  • ora-32766 : instr with negative offset: use varchar semantics on LOBs
  • ora-16769 : the physical standby database is open read-only
  • ora-39132 : object type "string"."string" already exists with different hashcode
  • ora-08008 : another instance is mounted with USE_ROW_ENQUEUES = string
  • ora-00130 : invalid listener address 'string'
  • 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.