ORA-19030: Method invalid for non-schema based XML Documents.

Cause : The method can be invoked on only schema based xmltype objects.

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

Don't invoke the method for non schema based xmltype objects.

update : 28-04-2017
ORA-19030

ORA-19030 - Method invalid for non-schema based XML Documents.
ORA-19030 - Method invalid for non-schema based XML Documents.

  • ora-37102 : (XSVPART02) Invalid partition name string.
  • ora-30194 : reserved for future use
  • ora-12708 : error while loading create database NLS parameter string
  • ora-35282 : (SNSYN166) The format of the AGGREGATE function is: AGGREGATE(varname USING aggmap-name [COUNTVAR intvar-name] [FORCECALC])
  • ora-00327 : log string of thread string, physical size string less than needed string
  • ora-06923 : CMX: illegal break condition
  • ora-28577 : argument string of external procedure string has unsupported datatype string
  • ora-12084 : must use ALTER MATERIALIZED VIEW to alter "string"."string"
  • ora-12353 : secondary stored object cannot reference remote object
  • ora-14192 : cannot modify physical index attributes of a Hash index partition
  • ora-29382 : validation of pending area failed
  • ora-26094 : stream format error: input column overflow
  • ora-30154 : The memory address given as buffer for OCIFileRead/Write is invalid
  • ora-13265 : geometry identifier column string in table string is not of type NUMBER
  • ora-19511 : Error received from media manager layer, error text: string
  • ora-02242 : no options specified for ALTER INDEX
  • ora-08190 : restore point string is from a different incarnation of the database
  • ora-10668 : Inject Evil Identifiers
  • ora-01104 : number of control files (string) does not equal string
  • ora-19555 : invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
  • ora-32026 : %s.string has fewer columns compared to string table.
  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • ora-13951 : MMON sub-action time limit exceeded
  • ora-12026 : invalid filter column detected
  • ora-13467 : unsupported GeoRaster metadata specification: string
  • ora-33022 : (XSAGDNGL10) The measure dimension workspace object must be a TEXT or ID base dimension that does not dimension AGGMAP workspace object, but is in the same analytic workspace.
  • ora-25312 : Cannot specify nonzero sender protocol
  • ora-31053 : The value of the depth argument in the operator cannot be negative
  • ora-15105 : missing or invalid FAILGROUP name
  • ora-01352 : tablespace given for Logminer spill does not exist
  • 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.