ORA-19105: invalid XQueryX: expected text node - got string

Cause : The XQueryX expression did not contain a text node as expected.

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

Specify a valid XQueryX.

update : 19-08-2017

ORA-19105 - invalid XQueryX: expected text node - got string
ORA-19105 - invalid XQueryX: expected text node - got string

  • ora-13870 : Database-wide SQL tracing is not enabled
  • ora-24422 : error occurred while trying to destroy the Session Pool
  • ora-06528 : Error executing PL/SQL profiler
  • ora-22617 : error while accessing the image handle collection
  • ora-09803 : Allocation of string buffer failed.
  • ora-07716 : sksachk: invalid device specification for ARCHIVE
  • ora-23457 : invalid flavor ID string
  • ora-28553 : pass-through SQL: invalid bind-variable position
  • ora-02731 : osnrnf: malloc of buffer failed
  • ora-32505 : too many watchpoints
  • ora-04097 : DDL conflict while trying to drop or alter a trigger
  • ora-31661 : there are no metadata transform values of type VARCHAR2
  • ora-14159 : duplicate subpartition name
  • ora-32631 : illegal use of objects in MODEL
  • ora-09712 : orasrv: log archiver already connected.
  • ora-32168 : Cannot perform operation on a null AnyData
  • ora-27069 : attempt to do I/O beyond the range of the file
  • ora-21709 : cannot refresh an object that has been modified
  • ora-31654 : unable to convert file or volume size as specified to a number
  • ora-22286 : insufficient privileges on file or directory to perform string operation
  • ora-38742 : Flashback log file has incorrect log reset status.
  • ora-27037 : unable to obtain file status
  • ora-25950 : missing where clause in join index specification
  • ora-19720 : Error occurred when converting an OCI number into an SCN
  • ora-39125 : Worker unexpected fatal error in string while calling string [string]
  • ora-16249 : Terminal apply failed to complete during failover
  • ora-25120 : MINIMUM EXTENT option already specified
  • ora-16115 : %s\% of LogMiner dictionary loading is done
  • ora-16512 : parameter exceeded maximum size limit
  • ora-19714 : length for generated name longer than 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.