ORA-19248: XQ0028 - invalid node in document constructor

Cause : The cotnent seuqence i na docuemnt contsructorc ontainde eithe ra docuemnt or na attriubte nod.e

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

Fix th econten tso it odes notc ontaina ny of hte abov enode tpyes.

update : 30-04-2017

ORA-19248 - XQ0028 - invalid node in document constructor
ORA-19248 - XQ0028 - invalid node in document constructor

  • ora-38434 : could not evaluate expression "string"
  • ora-15133 : instance recovery required for diskgroup string
  • ora-13864 : Statistics aggregation for service (module/action) string is already enabled
  • ora-19753 : error writing to change tracking file
  • ora-01605 : missing numbers in clause "string" of string
  • ora-23615 : Block number string does not exist for script string
  • ora-15050 : disk "string" contains string error(s)
  • ora-31668 : Timeout before worker process string finished initialization.
  • ora-01625 : rollback segment 'string' does not belong to this instance
  • ora-09718 : osnsui: cannot set up user interrupt handler.
  • ora-01103 : database name 'string' in control file is not 'string'
  • ora-30195 : reserved for future use
  • ora-12417 : database object "string" not found
  • ora-29507 : query derived from USING clause found zero or many rows
  • ora-00350 : log string of instance string (thread string) needs to be archived
  • ora-01236 : Error string occurred during initialization of file header access
  • ora-28300 : No permission to read user entry in LDAP directory service.
  • ora-19252 : XQ0032 - too many declarations for base URI
  • ora-31207 : DBMS_LDAP: PL/SQL - Invalid LDAP search time value.
  • ora-37023 : (XSMLTUPD01) Object workspace object cannot be updated without dimension workspace object.
  • ora-30189 : reserved for future use
  • ora-24194 : attempt to read data in a message as the wrong type
  • ora-33066 : (XSAGDNGL32) In AGGMAP workspace object, the hierarchy dimension QDR workspace object must be a hierarchy dimension of the relation.
  • ora-14030 : non-existent partitioning column in CREATE TABLE statement
  • ora-06960 : Failed to access log file
  • ora-38861 : flashback recovery stopped before reaching recovery target
  • ora-24811 : less data provided for writing than indicated
  • ora-38797 : Full database recovery required after a database has been flashed back
  • ora-01632 : max # extents (string) reached in index string.string
  • ora-19931 : file string has invalid creation SCN string
  • 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.