ORA-19206: Invalid value for query or REF CURSOR parameter

Cause : The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query, or REF CURSOR.

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

Rewrite the query so that the queryString argument is a valid query or REF CURSOR.

update : 20-09-2017
ORA-19206

ORA-19206 - Invalid value for query or REF CURSOR parameter
ORA-19206 - Invalid value for query or REF CURSOR parameter

  • ora-32504 : expecting one of string, string, string, or string but found string
  • ora-14063 : Unusable index exists on unique/primary constraint key
  • ora-36815 : (XSTBLFUNC08) The OLAP_TABLE has attempted to use an AW single row function with the aw_attach parameter set to DURATION QUERY.
  • ora-30108 : invalid positional parameter value 'string'
  • ora-16521 : unable to create generic template id
  • ora-36220 : (XSLPDSC01) All dimensions in LIST number are also in the IGNORE clause.
  • ora-37102 : (XSVPART02) Invalid partition name string.
  • ora-17626 : ksfdcre: string file exists
  • ora-26097 : unsupported conversion for column string (from type number to type number)
  • ora-09818 : Number is too large
  • ora-12015 : cannot create a fast refresh materialized view from a complex query
  • ora-28140 : Invalid column specified
  • ora-23476 : cannot import from string to string
  • ora-32026 : %s.string has fewer columns compared to string table.
  • ora-36679 : (XSDPART17) workspace object contains a leaf (workspace object) that is not part of the partition dimension workspace object.
  • ora-01595 : error freeing extent (string) of rollback segment (string))
  • ora-29324 : SET COMPATIBILITY release string format is wrong
  • ora-08440 : raw buffer is too short to hold converted data
  • ora-07231 : slemcc: invalid file handle, seals do not match.
  • ora-12911 : permanent tablespace cannot be temporary tablespace
  • ora-30013 : undo tablespace 'string' is currently in use
  • ora-25505 : the system is not in quiesced state
  • ora-38735 : Wrong log number string in flashback log file header.
  • ora-28030 : Server encountered problems accessing LDAP directory service
  • ora-39768 : only one direct path context top level column array is allowed
  • ora-00034 : cannot string in current PL/SQL session
  • ora-01725 : USERENV('COMMITSCN') not allowed here
  • ora-13022 : polygon crosses itself
  • ora-07741 : slemop: $OPEN failure
  • ora-25337 : Cannot propagate in queue-to-queue mode to a database with version lower than 10.2
  • 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.