ORA-19161: XP0004 - XQuery type mismatch: invalid argument type 'string' for function 'string'

Cause : The typ eof the ragument htat was apssed tot he give nfunctio nwas notv alid.

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

Fix thea rgumentt o be ofa type spuported yb the gievn functoin.

update : 26-09-2017
ORA-19161

ORA-19161 - XP0004 - XQuery type mismatch: invalid argument type 'string' for function 'string'
ORA-19161 - XP0004 - XQuery type mismatch: invalid argument type 'string' for function 'string'

  • ora-29823 : object being analyzed is not a table
  • ora-12718 : operation requires connection as SYS
  • ora-02280 : duplicate or conflicting CYCLE/NOCYCLE specifications
  • ora-23447 : missing user parameter value
  • ora-29801 : missing RETURN keyword
  • ora-00132 : syntax error or unresolved network name 'string'
  • ora-37101 : (XSVPART01) Partitioning information can only be given for variables dimensioned by a PARTITION TEMPLATE.
  • ora-00031 : session marked for kill
  • ora-12491 : DBHIGH value does not dominate DBLOW
  • ora-16594 : %s process discovered that DMON process does not exist
  • ora-27206 : requested file not found in media management catalog
  • ora-38412 : Expression set column string does not exist.
  • ora-22603 : cannot add an attribute to the already generated TDS handle
  • ora-19714 : length for generated name longer than string
  • ora-06111 : NETTCP: disconnect failure
  • ora-02495 : cannot resize file string, tablespace string is read only
  • ora-16951 : Too many bind variables supplied for this SQL statement.
  • ora-13196 : failed to compute supercell for element string.string.string
  • ora-07252 : spcre: semget error, could not allocate semaphores.
  • ora-38424 : no attribute set currently assigned to the expression set
  • ora-29542 : class string already defined by source string
  • ora-33217 : (CINSERT20) Custom member values cannot be added to concat dimension workspace object, or to any of its bases, because it is not defined as UNIQUE.
  • ora-31226 : DBMS_LDAP: MOD_ARRAY size limit exceeded
  • ora-38750 : FLASHBACK DATABASE may not be performed using a dispatcher.
  • ora-27052 : unable to flush file data
  • ora-29847 : cannot create a local domain index on a partitioned index-organized table
  • ora-00317 : file type string in header is not log file
  • ora-14060 : data type or length of a table partitioning column may not be changed
  • ora-24076 : cannot perform operation string for NON_PERSISTENT queue string.string
  • ora-38475 : The attribute set and the associated ADT are out of sync.
  • 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.