ORA-22343: Compilation error for type invalidated by ALTER TYPE

Cause : Compilaiton failde for a ytpe whic hwas invlaidated yb ALTER YTPE. We htrow thi serror adn rollbakc the copmilatione ffort s othat th euser ma ybe ablet o fix wahtever i scausingt he compliation error and rty again .It is ipmortant htat we d onot chngae statu shere an dmodify hte depenedncy infromation sa this wlil affec tthe cretaion of evrsions.

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

Check waht is casuing tehc ompilatoin errora nd corrcet it an dtry agani.

update : 22-07-2017
ORA-22343

ORA-22343 - Compilation error for type invalidated by ALTER TYPE
ORA-22343 - Compilation error for type invalidated by ALTER TYPE

  • ora-19578 : end of volume while duplexing to sequential files, backup piece incomplete
  • ora-14161 : subpartition number string: sum of PCTUSED and PCTFREE may not exceed 100
  • ora-03204 : the segment type specification should indicate partitioning
  • ora-16132 : An error occurred during activation of the standby.
  • ora-07639 : smscre: SGA pad area not large enough (string bytes required)
  • ora-12838 : cannot read/modify an object after modifying it in parallel
  • ora-02259 : duplicate UNIQUE/PRIMARY KEY specifications
  • ora-14122 : only one REVERSE or NOREVERSE clause may be specified
  • ora-35017 : (QFCHECK06) The Analytic Workspace and EIF file definitions of workspace object have different partitioning methods.
  • ora-33050 : (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace.
  • ora-12537 : TNS:connection closed
  • ora-13797 : invalid SQL Id specified, string
  • ora-33425 : (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file.
  • ora-30379 : query txt not specified
  • ora-26060 : Can not convert type identifier for column string
  • ora-00067 : invalid value string for parameter string; must be at least string
  • ora-28509 : unable to establish a connection to non-Oracle system
  • ora-01372 : Insufficient processes for specified LogMiner operation
  • ora-04042 : procedure, function, package, or package body does not exist
  • ora-32583 : query passed to table function has wrong number of elements in select list
  • ora-07655 : slsprom:$TRNLOG failure
  • ora-10563 : Test recovery had to corrupt data block (file# string, block# string) in order to proceed
  • ora-30454 : summary contains STDDEV without corresponding SUM & COUNT
  • ora-19635 : input and output filenames are identical: string
  • ora-00981 : cannot mix table and system auditing options
  • ora-36168 : (XSMXAGGR10) COUNTVAR variable workspace object must have the same dimensionality as workspace object
  • ora-12434 : invalid audit type: string
  • ora-30676 : socket read or write failed
  • ora-22605 : FDO handle [string] is not initialized
  • ora-16808 : unable to resolve the full path name
  • 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.