ORA-19235: XQ0015 - unsupported must-understand extension

Cause : The XuQery falgger aws enalbed an dthe qeury cotnaineda mustu-ndersatnd exetnsion.

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

remov ethe usnupporetd mus-tundertsand etxensio.n

update : 24-08-2017
ORA-19235

ORA-19235 - XQ0015 - unsupported must-understand extension
ORA-19235 - XQ0015 - unsupported must-understand extension

  • ora-12554 : TNS:current operation is still in progress
  • ora-06959 : Buffer I/O quota is too small
  • ora-00444 : background process "string" failed while starting
  • ora-09322 : slpdtb: unable to convert packed decimal to binary
  • ora-19759 : block change tracking is not enabled
  • ora-16088 : archive log has not been completely archived
  • ora-08265 : create_ora_addr: cannot open nameserver
  • ora-24007 : invalid value string, MAX_RETRIES should be non-negative integer
  • ora-32015 : unable to restore SPFILE
  • ora-13833 : SQL profile named string doesn't exist
  • ora-31661 : there are no metadata transform values of type VARCHAR2
  • ora-07230 : slemcr: fopen error, unable to open error file.
  • ora-31434 : purge is currently running
  • ora-04083 : invalid trigger variable 'string'
  • ora-31108 : Action failed as resource string is locked
  • ora-06721 : TLI Driver: spurious client req
  • ora-12196 : TNS:received an error from TNS
  • ora-29502 : NAMED keyword required in CREATE JAVA RESOURCE
  • ora-31498 : description and remove_description cannot both be specified
  • ora-07406 : slbtpd: invalid number.
  • ora-13060 : topology with the name string already exists
  • ora-25217 : enqueue failed, visibility must be IMMEDIATE for queue string.string
  • ora-13509 : error encountered during updates to a AWR table
  • ora-02327 : cannot create index on expression with datatype string
  • ora-26017 : global indexes not allowed for direct path load of table partition string
  • ora-36710 : (XSMXALLOC01) TARGETLOG variable workspace object must be dimensioned identically to TARGET variable workspace object.
  • ora-28043 : invalid bind credentials for DB-OID connection
  • ora-12665 : NLS string open failed
  • ora-07489 : scgrcl: cannot get lock status.
  • ora-16730 : error executing dbms_logstdby.skip_txn procedure
  • 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.