ORA-19116: too many xmlspace declarations

Cause : The query prolog contained multiple xmlspace declarations.

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

Remove the duplicate xmlspace declarations.

update : 27-06-2017
ORA-19116

ORA-19116 - too many xmlspace declarations
ORA-19116 - too many xmlspace declarations

  • ora-30655 : cannot select FOR UPDATE from external organized table
  • ora-01320 : Invalid Logminer dictionar attribute
  • ora-38454 : attribute set not defined for the column being indexed
  • ora-38730 : Invalid SCN/TIMESTAMP expression.
  • ora-28232 : invalid input length for obfuscation toolkit
  • ora-26680 : object type not supported
  • ora-02172 : The PUBLIC keyword is not appropriate for a disable thread
  • ora-16240 : Waiting for logfile (thread# string, sequence# string)
  • ora-16078 : media recovery disabled
  • ora-07759 : slemtr: invalid destination
  • ora-16070 : parameter string contains an invalid REGISTER attribute value
  • ora-14071 : invalid option for an index used to enforce a constraint
  • ora-19333 : Invalid flags for the CREATE_DBURI operator
  • ora-33920 : (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, or INTEGER.
  • ora-01510 : error in deleting log files
  • ora-14508 : specified VALIDATE INTO table not found
  • ora-24373 : invalid length specified for statement
  • ora-02707 : osnacx: cannot allocate context area
  • ora-01166 : file number string is larger than string (string)
  • ora-14281 : CHECK constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-08448 : syntax error in DECIMAL-POINT environment clause
  • ora-13283 : failure to get new geometry object for conversion in place
  • ora-31512 : name cannot contain double quotation marks
  • ora-30932 : Reference node 'string' not contained in specified parent node 'string'
  • ora-25195 : invalid option for index on an index-organized table
  • ora-14617 : cannot add/drop values to DEFAULT subpartition
  • ora-32503 : Mapping SGA from file failed
  • ora-01865 : not a valid era
  • ora-39050 : parameter string is incompatible with parameter string
  • ora-12660 : Encryption or crypto-checksumming parameters incompatible
  • 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.