ORA-24124: invalid ACTION parameter passed to DBMS_REPAIR.string procedure

Cause : An invalid ACTION parameter was specified.

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

Specify CREATE_ACTION, PURGE_ACTION or DROP_ACTION for the ACTION parameter.

update : 24-05-2017
ORA-24124

ORA-24124 - invalid ACTION parameter passed to DBMS_REPAIR.string procedure
ORA-24124 - invalid ACTION parameter passed to DBMS_REPAIR.string procedure

  • ora-28111 : insufficient privilege to evaluate policy predicate
  • ora-13434 : GeoRaster metadata cellRepresentation error
  • ora-10630 : Illegal syntax specified with SHRINK clause
  • ora-14164 : subpartition "string": INITRANS value must be less than MAXTRANS value
  • ora-24159 : invalid variable definiton
  • ora-10631 : SHRINK clause should not be specified for this object
  • ora-15075 : disk(s) are not visible cluster-wide
  • ora-29872 : parameters clause cannot be combined with the specified options
  • ora-24902 : invalid subscription name or name-length in subscription handle
  • ora-00231 : snapshot control file has not been named
  • ora-29846 : cannot create a local domain index on a string partitioned table
  • ora-01160 : file is not a string
  • ora-00096 : invalid value string for parameter string, must be from among string
  • ora-01611 : thread number string is invalid - must be between 1 and string
  • ora-12071 : definition query of "string"."string" is invalid for offline instantiation
  • ora-00056 : DDL lock on object 'string.string' is already held in an incompatible mode
  • ora-16156 : LGWR archive log dependency not allowed if database is standby protected
  • ora-19637 : backupPieceCreate requires file name when using DISK device
  • ora-10632 : Invalid rowid
  • ora-37130 : (XSCCOMP05) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because you must specify AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over base workspace object.
  • ora-03213 : Invalid Lob Segment Name for DBMS_SPACE package
  • ora-29863 : warning in the execution of ODCIINDEXCREATE routine
  • ora-30018 : Create Rollback Segment failed, USN string is out of range
  • ora-16631 : operation requires shutdown of database/instance "string"
  • ora-03279 : invalid INSTANCE specified
  • ora-02464 : Cluster definition can not be both HASH and INDEX
  • ora-00317 : file type string in header is not log file
  • ora-01113 : file string needs media recovery
  • ora-12652 : String truncated
  • ora-08234 : smsget: cannot get instance listener address
  • 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.