ORA-13827: null or zero length attribute specified in SQL profile collection

Cause : One of the attributes within the SQL profile was not properly specified.

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

Retry with a fully specified SQL profile.

update : 25-04-2017

ORA-13827 - null or zero length attribute specified in SQL profile collection
ORA-13827 - null or zero length attribute specified in SQL profile collection

  • ora-16589 : Data Guard Connection process detected a network transfer error
  • ora-38502 : invalid XML tag: string
  • ora-36961 : Oracle OLAP is not available.
  • ora-32690 : Hash Table Infrastructure ran out of memory
  • ora-23368 : name string cannot be null or the empty string
  • ora-22332 : a dependent object in schema "string" has errors. string
  • ora-13389 : unable to compute buffers or intersections in analysis function
  • ora-29521 : referenced name string could not be found
  • ora-29501 : invalid or missing Java source, class, or resource name
  • ora-33052 : (XSAGDNGL25) AGGMAP workspace object is a dimensioned AGGMAP; it can only be used to aggregate like-dimensioned variables.
  • ora-24030 : Only one of rule or rule-set must be specified
  • ora-34489 : (MXMAINT06) You cannot maintain workspace object because it is a SURROGATE.
  • ora-30512 : cannot modify string.string more than once in a transaction
  • ora-16225 : Missing LogMiner session name for Streams
  • ora-01547 : warning: RECOVER succeeded but OPEN RESETLOGS would get error below
  • ora-07645 : sszfsl: $CHANGE_CLASS failure
  • ora-27071 : unable to seek to desired position in file
  • ora-09942 : Write of ORACLE password file header failed.
  • ora-36642 : (XSDUNION06) Concat dimension list contains duplicate leaf dimension workspace object.
  • ora-22603 : cannot add an attribute to the already generated TDS handle
  • ora-29316 : datafile string been imported twice
  • ora-07339 : spcre: maximum number of semaphore sets exceeded.
  • ora-24750 : incorrect size of attribute
  • ora-27509 : IPC error receiving a message
  • ora-14644 : table is not subpartitioned by Hash method
  • ora-24760 : invalid isolation level flags
  • ora-31102 : Already locked in exclusive mode. Cannot add lock.
  • ora-36708 : (XSMXALLOC00) Variable workspace object must be dimensioned to be used by the ALLOCATE command.
  • ora-16636 : Fast-Start Failover target standby in error state, cannot stop observer
  • ora-16122 : applying large dml transaction at 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.