ORA-22869: depth of type dependency hierarchy exceeds maximum limit

Cause : The type dependency hierarchy was structured to have depth greater than 1024.

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

Re-structure the type dependency hierarchy to a shorter depth.

update : 28-05-2017

ORA-22869 - depth of type dependency hierarchy exceeds maximum limit
ORA-22869 - depth of type dependency hierarchy exceeds maximum limit

  • ora-23367 : table string is missing the primary key
  • ora-32152 : Cannot perform operation on a null number
  • ora-28168 : attempted to grant password-protected role
  • ora-32145 : Environment not specified
  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • ora-16251 : LSP1 Background Build not permitted
  • ora-10588 : Can only allow 1 corruption for normal media/standby recovery
  • ora-01502 : index 'string.string' or partition of such index is in unusable state
  • ora-02066 : missing or invalid DISPATCHERS text
  • ora-31431 : all source tables must belong to the synchronous change set
  • ora-09825 : Unable to disable allowmacaccess privilege.
  • ora-23422 : Oracle Server could not generate an unused job number
  • ora-14308 : partition bound element must be one of: string, datetime or interval literal, number, or NULL
  • ora-22618 : attribute is a BAD NULL in the image handle
  • ora-24006 : cannot create QUEUE, string already exists
  • ora-16559 : out of memory at string
  • ora-12234 : TNS:Redirect to destination
  • ora-25001 : cannot create this trigger type on views
  • ora-07549 : sftopn: $OPEN failure
  • ora-08443 : syntax error in BLANK WHEN ZERO clause in mask options
  • ora-25401 : can not continue fetches
  • ora-19009 : Missing XMLSchema keyword
  • ora-04060 : insufficient privileges to execute string
  • ora-23319 : parameter value string is not appropriate
  • ora-01718 : BY ACCESS | SESSION clause not allowed for NOAUDIT
  • ora-24308 : illegal define position
  • ora-33292 : (DBERR18) insufficient permissions to access analytic workspace string using the specified access mode.
  • ora-01575 : timeout waiting for space management resource
  • ora-01210 : data file header is media corrupt
  • ora-31901 : the current operation was cancelled by the user
  • 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.