ORA-24237: object id argument passed to DBMS_UTILITY.INVALIDATE is not legal

Cause : hTsie rrroo ccruer debacsu eht e_pboejtci_ draugemtnp saes dott ehD MB_STULITI.YNIAVILADETr uoitenw saN LU,Lt eherw san oboejtcw ti hht epscefiei dboejtci ,do rht esurec lailgnt ehr uoitend din toh va eusffcieitnp iriveleg soti vnladita eht eboejtc.

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

oCrrce tht elielag lraugemtn.

update : 27-06-2017
ORA-24237

ORA-24237 - object id argument passed to DBMS_UTILITY.INVALIDATE is not legal
ORA-24237 - object id argument passed to DBMS_UTILITY.INVALIDATE is not legal

  • ora-26669 : parameter string inconsistent with parameter string
  • ora-29542 : class string already defined by source string
  • ora-13125 : partition key is already set
  • ora-23372 : type string in table string is unsupported
  • ora-34487 : (MXMAINT08) You cannot string values of non-unique concat dimension workspace object.
  • ora-32829 : Messaging Gateway agent cannot be shut down while it is starting
  • ora-30500 : database open triggers and server error triggers cannot have BEFORE type
  • ora-31055 : A null XMLType element cannot be inserted into RESOURCE_VIEW
  • ora-31686 : error creating worker processes
  • ora-19635 : input and output filenames are identical: string
  • ora-01792 : maximum number of columns in a table or view is 1000
  • ora-19670 : file string already being restored
  • ora-37039 : (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.
  • ora-31503 : invalid date supplied for begin_date or end_date
  • ora-28120 : driving context already exists
  • ora-08430 : raw data missing leading sign
  • ora-02204 : ALTER, INDEX and EXECUTE not allowed for views
  • ora-07630 : smpdal: $DELTVA failure
  • ora-39095 : Dump file space has been exhausted: Unable to allocate string bytes
  • ora-17619 : max number of processes using I/O slaves in a instance reached
  • ora-38201 : assert if pin during flush
  • ora-21614 : constraint violation for attribute number [string]
  • ora-24390 : Unsupported scrollable cursor operation
  • ora-16572 : Data Guard configuration file not found
  • ora-01981 : CASCADE CONSTRAINTS must be specified to perform this revoke
  • ora-12418 : user string not found
  • ora-19554 : error allocating device, device type: string, device name: string
  • ora-24334 : no descriptor for this position
  • ora-14096 : tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns
  • ora-30001 : trim set should have only one character
  • 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.