ORA-19000: missing RELATIONAL keyword

Cause : The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in the XMLTYPE storage clause specification.

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

Supply the RELATIONAL keyword in the storage clause

update : 21-07-2017

ORA-19000 - missing RELATIONAL keyword
ORA-19000 - missing RELATIONAL keyword

  • ora-15095 : reached maximum ASM file size (string GB)
  • ora-02798 : Invalid number of requests
  • ora-14082 : new partition name must differ from that of any other partition of the object
  • ora-38446 : Error with embedded ADT "string" in the attribute set.
  • ora-09937 : Chmod of ORACLE password file failed.
  • ora-24395 : cannot reinitialize non-existent pool
  • ora-29702 : error occurred in Cluster Group Service operation
  • ora-03200 : the segment type specification is invalid
  • ora-34840 : (OPCREATE01) The string option must be declared with datatype string.
  • ora-19614 : archivelog thread string sequence string not found in backup set
  • ora-19161 : XP0004 - XQuery type mismatch: invalid argument type 'string' for function 'string'
  • ora-01052 : required destination LOG_ARCHIVE_DUPLEX_DEST is not specified
  • ora-15177 : cannot operate on system aliases
  • ora-01228 : SET DATABASE option required to install seed database
  • ora-10842 : Event for OCI Tracing and Statistics Info
  • ora-13759 : User "string" cannot remove reference "string".
  • ora-31674 : worker process interrupt for unhandled exception in master process
  • ora-29358 : resource plan string does not exist
  • ora-23444 : duplicate template parameter
  • ora-07568 : slspool: $OPEN failure
  • ora-01314 : Name of the column to be mined should be a string literal
  • ora-00380 : cannot specify db_stringk_cache_size since stringK is the standard block size
  • ora-36808 : (XSTBLFUNC04) The OLAP_TABLE function LEVELREL clause cannot declare number ADT fields from number AW fields.
  • ora-26020 : index string.string loaded successfully with string keys
  • ora-31508 : invalid parameter value for synchronous change set
  • ora-36400 : (XSSPROP02) workspace object is not a valid variable name.
  • ora-30502 : system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
  • ora-30082 : datetime/interval column to be modified must be empty to decrease fractional second or leading field precision
  • ora-09827 : SCLGT: atomic latch return unknown error.
  • ora-16121 : applying transaction with commit SCN 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.