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 : 26-04-2017

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

  • ora-24168 : rule string.string cannot have default evaluation context
  • ora-26692 : invalid value string, string should be in string format
  • ora-23323 : parameter length exceeds deferred RPC limits
  • ora-29890 : specified primary operator does not have an index context
  • ora-30565 : Only one INVALIDATE or UPDATE GLOBAL INDEXES clause may be specified
  • ora-07715 : sksadtd: could not dismount archival device (SYS$DISMNT failure)
  • ora-07456 : cannot set RESOURCE_MANAGER_PLAN when database is closed
  • ora-32821 : subscriber queue and exception queue must have same payload type
  • ora-14407 : partitioned table contains subpartitions in a different tablespace
  • ora-00206 : error in writing (block string, # blocks string) of control file
  • ora-24787 : remote cursors must be closed before a call completes
  • ora-02249 : missing or invalid value for MAXLOGMEMBERS
  • ora-09946 : File name too long for buffer
  • ora-24092 : invalid value string specified
  • ora-19244 : XQ0024 - invalid attribute node in element constructor
  • ora-32007 : internal
  • ora-01784 : RECOVERABLE cannot be specified with database media recovery disabled
  • ora-16009 : remote archive log destination must be a STANDBY database
  • ora-07210 : slcpu: getrusage error, unable to get cpu time.
  • ora-06108 : NETTCP: connect to host failed
  • ora-30341 : dropped level has references
  • ora-01673 : data file string has not been identified
  • ora-12548 : TNS:incomplete read or write
  • ora-01531 : a database already open by the instance
  • ora-29827 : keyword USING is missing
  • ora-16193 : Primary and standby network encryption mismatch
  • ora-01513 : invalid current time returned by operating system
  • ora-16245 : paging in transaction string, string, string
  • ora-06521 : PL/SQL: Error mapping function
  • ora-00910 : specified length too long for its datatype
  • 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.