ORA-19273: XQ0053 - empty string in namespace declaration

Cause : An empty string was used in a namespace declaration.

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

Fix the namespace declaration to have a non-empty string.

update : 30-04-2017
ORA-19273

ORA-19273 - XQ0053 - empty string in namespace declaration
ORA-19273 - XQ0053 - empty string in namespace declaration

  • ora-39035 : Data filter string has already been specified.
  • ora-22625 : OCIAnyData is not well-formed
  • ora-12029 : LOB columns may not be used as filter columns
  • ora-40289 : duplicate attributes provided for data mining function
  • ora-22347 : No changes to type specified for ALTER TYPE
  • ora-19619 : cannot call restoreValidate after files have been named
  • ora-38402 : invalid name: empty string or spaces in the name
  • ora-26099 : direct path context is already prepared
  • ora-01279 : db_files too large
  • ora-24438 : Invalid Authentication Handle specified.
  • ora-06319 : IPA: Remote maximum number of users exceeded
  • ora-16821 : logical standby database dictionary not yet loaded
  • ora-26516 : no push transaction acknowledgement
  • ora-28103 : adding a policy to an object owned by SYS is not allowed
  • ora-33413 : (EIFMAKEF01) You cannot export compressed composite workspace object because one of its bases has limited status or a PERMIT READ restriction.
  • ora-22875 : cannot drop primary key of an object table whose object identifier is primary key based
  • ora-19596 : SPFILE already included
  • ora-23541 : tables do not match tables used while defining the redefinition
  • ora-10269 : Don't do coalesces of free space in SMON
  • ora-30345 : circular dimension hierarchy
  • ora-24421 : OCISessionRelease cannot be used to release this session.
  • ora-01688 : unable to extend table string.string partition string by string in tablespace string
  • ora-31606 : XML context number does not match any previously allocated context
  • ora-16207 : Logical standby dictionary build not permitted.
  • ora-24010 : QUEUE string does not exist
  • ora-07610 : $GETJPIW failed in retrieving the user's MAC priviledges
  • ora-33016 : (XSAGDNGL07) In AGGMAP workspace object, workspace object is not a valid operator or variable name.
  • ora-16782 : instance not open for read and write access
  • ora-31526 : could not find source table string.string for CDC change table string.string
  • ora-39768 : only one direct path context top level column array is allowed
  • 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.