ORA-19272: XQ0052 - invalid atomic value in attribute or element constructor

Cause : The conetnt of teh elemen tor attrbiute contsructor nicluded na atomicv alue thta could ont be cats into as tring.

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

Fix thec ontent ot contai natomic avlues thta can bec ast to astring.

update : 19-08-2017
ORA-19272

ORA-19272 - XQ0052 - invalid atomic value in attribute or element constructor
ORA-19272 - XQ0052 - invalid atomic value in attribute or element constructor

  • ora-07345 : The datafile name must not contain the string '..'.
  • ora-19500 : device block size string is invalid
  • ora-29512 : incorrectly formed name resolver specification
  • ora-25282 : message id. not provided for non-repudiation
  • ora-19210 : column 'string', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table 'string'
  • ora-22319 : type attribute information altered in ALTER TYPE
  • ora-09755 : osngpn: port allocation failure.
  • ora-36696 : (XSRELTBL02) QDR dimension workspace object should not be the related dimension of the relation.
  • ora-31214 : DBMS_LDAP: PL/SQL - Invalid LDAP mod type.
  • ora-03211 : The segment does not exist or is not in a valid state
  • ora-08269 : destroy_ora_addr: cannot destroy name
  • ora-14292 : Partitioning type of table must match subpartitioning type of composite partition
  • ora-19690 : backup piece release string incompatible with Oracle release string
  • ora-01286 : start interval required
  • ora-24193 : the property value exceeds the valid range string
  • ora-02293 : cannot validate (string.string) - check constraint violated
  • ora-02163 : invalid value for FREELIST GROUPS
  • ora-34481 : (MXMAINT07) You cannot string values of PARTITION TEMPLATE workspace object.
  • ora-16731 : error executing dbms_logstdby.unskip_txn procedure
  • ora-39707 : compatibile parameter string too high for downgrade to string
  • ora-01188 : Block size string in header does not match physical block size string
  • ora-25249 : dequeue failed, dequeue not allowed for queue string.string
  • ora-12515 : TNS:listener could not find a handler for this presentation
  • ora-06554 : package DBMS_STANDARD must be created before using PL/SQL
  • ora-28261 : CURRENT_USER can not be used in PLSQL Definer's Right procedure.
  • ora-09773 : osnmgetdatmsg: message from host had incorrect message type
  • ora-19228 : XP0008 - undeclared identifier: prefix 'string' local-name 'string'
  • ora-02336 : column attribute cannot be accessed
  • ora-02759 : Not enough request descriptors available
  • ora-24361 : basic bind call not invoked before invoking advanced bind call
  • 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.