ORA-24121: both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure

Cause : Boht csacaed adn ab lokc rnagew er espceifeid ni ac al ltoD BM_SREAPIRC.HEKC_OJBEC.T

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

Us eeihterc asacdeo r ablcok arng,e o rdon otu see itehr noe.

update : 27-06-2017
ORA-24121

ORA-24121 - both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure
ORA-24121 - both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure

  • ora-09792 : sllfop: cannot allocate read buffer.
  • ora-32812 : subscriber string does not exist
  • ora-01880 : the fractional seconds must be between 0 and 999999999
  • ora-31504 : cannot alter or drop predefined change source
  • ora-03238 : unable to extend LOB segment string.string subpartition string by string in tablespace string
  • ora-22626 : Type Mismatch while constructing or accessing OCIAnyData
  • ora-33008 : (XSAGDNGL03) The relation workspace object is not a relation over a base dimension of AGGMAP workspace object.
  • ora-16215 : history metadata inconsistency
  • ora-00128 : this command requires a dispatcher name
  • ora-25226 : dequeue failed, queue string.string is not enabled for dequeue
  • ora-16074 : ARCH processes must be active
  • ora-35578 : (SQLOUT11) SQL cursor 'number' cannot be used with CURRENT OF syntax
  • ora-13456 : GeoRaster cell data error
  • ora-16068 : redo log file activation identifier mismatch
  • ora-06445 : ssvpstevrg: Incorrect parameters passed to function call
  • ora-16808 : unable to resolve the full path name
  • ora-09945 : Unable to initialize the audit trail file
  • ora-19661 : datafile string could not be verified
  • ora-36862 : (XSTFRC02) Column number for this SQL Cache must be between 1 and number. Specified column number number is invalid.
  • ora-16220 : no failed transaction found
  • ora-22152 : destination variable-length array is not initialized
  • ora-19904 : test recovery not allowed for datafile string
  • ora-24382 : statement handled already executed or described
  • ora-01547 : warning: RECOVER succeeded but OPEN RESETLOGS would get error below
  • ora-13521 : Unregister operation on local Database id (string) not allowed
  • ora-38727 : FLASHBACK DATABASE requires a current control file.
  • ora-25246 : listen failed, the address string is an 8.0 style exception queue
  • ora-04081 : trigger 'string' already exists
  • ora-22318 : input type is not an array type
  • ora-23323 : parameter length exceeds deferred RPC limits
  • 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.