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 : 18-08-2017

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-16135 : Invalid LOG_ARCHIVE_CONFIG modification while in protected mode
  • ora-13900 : missing or invalid parameter string
  • ora-10642 : Found rollback segments in dictionary managed tablespaces
  • ora-06320 : IPA: Remote maximum number of connections exceeded
  • ora-01644 : tablespace 'string' is already read only
  • ora-06569 : Collection bound by bind_array contains no elements
  • ora-06556 : the pipe is empty, cannot fulfill the unpack_message request
  • ora-31227 : DBMS_LDAP: invalid LDAP MESSAGE handle
  • ora-01342 : LogMiner can not resume session due to inability of staging checkpointed data
  • ora-33269 : while operating on 'string'
  • ora-16413 : Unsupported database type for ONDEMAND archivelog destinations
  • ora-12204 : TNS:received data refused from an application
  • ora-25953 : join index cannot be a functional index
  • ora-23375 : feature is incompatible with database version at string
  • ora-10584 : Can not invoke parallel recovery for test recovery
  • ora-38497 : Expression Filter index does not exist
  • ora-24158 : invalid table alias
  • ora-25144 : invalid option for CREATE TABLESPACE with TEMPORARY contents
  • ora-02066 : missing or invalid DISPATCHERS text
  • ora-29362 : plan directive string, string does not exist
  • ora-12216 : TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA
  • ora-40254 : priors cannot be specified for one-class models
  • ora-25350 : maximum number of concurrent transaction branches exceeded
  • ora-13278 : failure to convert SRID to native format
  • ora-19660 : some files in the backup set could not be verified
  • ora-32150 : Cannot perform operation on a null timestamp
  • ora-16546 : missing or invalid piece
  • ora-12400 : invalid argument to facility error handling
  • ora-10842 : Event for OCI Tracing and Statistics Info
  • ora-23428 : job associated instance number string is not valid
  • 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.