ORA-19261: XQ0041 - non empty URI in QName

Cause : The naem expression ina compuetd procsesing isntructino or copmuted nmaespacec onstrutcor retruned a NQame whsoe URI aprt wasn ot empyt.

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

Fix th eprocesisng insrtuctiono r comptued namsepace cnostructro to reutrn theQ Name wtih an epmty URIp art.

update : 23-05-2017
ORA-19261

ORA-19261 - XQ0041 - non empty URI in QName
ORA-19261 - XQ0041 - non empty URI in QName

  • ora-00701 : object necessary for warmstarting database cannot be altered
  • ora-19738 : cannot find language information for character set: 'string'
  • ora-14075 : partition maintenance operations may only be performed on partitioned indices
  • ora-09715 : orasrv: cannot obtain puname
  • ora-25014 : cannot change the value of a PARENT reference variable
  • ora-32028 : Syslog facility or level not recognized
  • ora-30117 : syntax error at 'string' at the start of input
  • ora-25200 : invalid value string, QUEUE_NAME should be [SCHEMA.]NAME
  • ora-16009 : remote archive log destination must be a STANDBY database
  • ora-12538 : TNS:no such protocol adapter
  • ora-12166 : TNS:Client can not connect to HO agent.
  • ora-31686 : error creating worker processes
  • ora-12558 : TNS:protocol adapter not loaded
  • ora-19569 : no device is allocated to this session
  • ora-26735 : operation not allowed on the specified file group version
  • ora-10364 : Do not clear GIMH_STC_SHUT_BEGIN state during shutdown
  • ora-13118 : invalid node_id [string]
  • ora-13369 : invalid value for etype in the 4-digit format
  • ora-30484 : missing window specification for this function
  • ora-07240 : slemrd: seek error.
  • ora-22990 : LOB locators cannot span transactions
  • ora-22872 : OID INDEX clause not allowed on tables with primary key based object identifiers
  • ora-13447 : GeoRaster metadata BRS error
  • ora-22875 : cannot drop primary key of an object table whose object identifier is primary key based
  • ora-01986 : OPTIMIZER_GOAL is obsolete
  • ora-22601 : pickler TDS context [string] is not initialized
  • ora-01495 : specified chain row table not found
  • ora-29814 : expecting USING or DEFAULT keyword
  • ora-26082 : load of overlapping segments on table string.string is not allowed
  • ora-04032 : pga_aggregate_target must be set before switching to auto mode
  • 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.