ORA-29383: all leaves of top-plan string must be consumer groups

Cause : nAa ttmetpw sam da eotc erta erom dofi yht epscefiei dot-plpnab tui tah sosemp alsna selvase.

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

oTi edtnfi yhwci hlpna sna/drop al nidertcvisen ee dotb eomidifde ,olkoa tla llpna shttah va eonp al nidertcvise .hTne ,laet rht eot-plpnas ohttaa lli stl aeev sra eocsnmureg orpu.s

update : 21-08-2017

ORA-29383 - all leaves of top-plan string must be consumer groups
ORA-29383 - all leaves of top-plan string must be consumer groups

  • ora-14151 : invalid table partitioning method
  • ora-31447 : cannot create change tables in the SYS schema
  • ora-13350 : two or more rings of a complex polygon touch
  • ora-09703 : sem_release: cannot release latch semaphore
  • ora-32848 : foreign queue DOMAIN required for JMS unified connections
  • ora-09943 : Allocation of memory for password list component failed.
  • ora-12446 : Insufficient authorization for administration of policy string
  • ora-38472 : VARCHAR representation of the data item is too long.
  • ora-13049 : unable to determine tolerance value from table _SDODIM
  • ora-01878 : specified field not found in datetime or interval
  • ora-31080 : type not specified for attribute or element "string"
  • ora-08435 : PICTURE MASK missing the leading sign when SIGN IS LEADING specified
  • ora-16061 : Log file status has changed
  • ora-30154 : The memory address given as buffer for OCIFileRead/Write is invalid
  • ora-29809 : cannot drop an operator with dependent objects
  • ora-06043 : NETDNT: message send failure
  • ora-19008 : Invalid version of the XMLType
  • ora-16536 : unknown object type
  • ora-30979 : Partitioned XML Index not yet supported.
  • ora-27207 : syntax error in device PARMS - parentheses mismatch or missing
  • ora-06309 : IPA: No message queue available
  • ora-08119 : The new initrans will make the index too big
  • ora-01317 : Not attached to a Logminer session
  • ora-36222 : (XSLPDSC03) duplicate IGNORE or DENSE information for dimension workspace object
  • ora-36847 : (XSLMGEN17) AW name is blank
  • ora-24197 : JAVA stored procedure throws JAVA exceptions
  • ora-31055 : A null XMLType element cannot be inserted into RESOURCE_VIEW
  • ora-01646 : tablespace 'string' is not read only - cannot make read write
  • ora-02201 : sequence not allowed here
  • ora-36885 : (XSSRF04) Error rewriting OLAP DML expression. Column name too big
  • 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.