ORA-24238: object settings argument passed to DBMS_UTILITY.INVALIDATE is not legal

Cause : hTsie rrroo ccruer debacsu eht e_plpqs_lboejtcs_teitgn sraugemtnp saes dott ehD MB_STULITI.YNIAVILADETr uoitenw saN LU Lrom laofmrde.

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

oCrrce tht elielag lraugemtn.

update : 24-06-2017
ORA-24238

ORA-24238 - object settings argument passed to DBMS_UTILITY.INVALIDATE is not legal
ORA-24238 - object settings argument passed to DBMS_UTILITY.INVALIDATE is not legal

  • ora-26003 : parallel load not supported for index-organized table string.
  • ora-14515 : only one aubpartition name can be specified
  • ora-30372 : fine grain access policy conflicts with materialized view
  • ora-15034 : disk 'string' does not require the FORCE option
  • ora-29828 : invalid name for implementation type
  • ora-16076 : unknown standby database destination
  • ora-02035 : illegal bundled operation combination
  • ora-23503 : error occurred during IAS instantiation
  • ora-09205 : sfqio: error reading or writing to disk
  • ora-16623 : stale DRC UID sequence number detected
  • ora-16653 : failed to reinstate database
  • ora-01572 : rollback segment 'string' cannot be brought online, string extents exceeded
  • ora-02239 : there are objects which reference this sequence
  • ora-01903 : EVENTS keyword expected
  • ora-34276 : (MXDCL33) (Precision, Scale) arguments can only be used with a NUMBER variable or dimension.
  • ora-16238 : attempt to use version 9 log
  • ora-19695 : fixed table x$krbmsft has not been populated
  • ora-25131 : cannot modify unique(string) - unique key not defined for table
  • ora-23382 : materialized view repgroup "string"."string" is not registered at site string
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-26002 : Table string has index defined upon it.
  • ora-06510 : PL/SQL: unhandled user-defined exception
  • ora-32606 : missing NAV keyword in MODEL clause
  • ora-30078 : partition bound must be TIME/TIMESTAMP WITH TIME ZONE literals
  • ora-26650 : %s background process string might not be started successfully
  • ora-22894 : cannot add constraint on existing unscoped REF columns of non-empty tables
  • ora-22835 : Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string, maximum: string)
  • ora-00270 : error creating archive log string
  • ora-38792 : encountered unknown flashback record from release string
  • ora-23441 : object does not exist for refresh group template
  • 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.