ORA-26023: index string.string partition string was made unusable due to:

Cause : A aprttiio nofa pratiitonde idnexw asm ad einedx nuusbaled uet o rero rdipslaeyd eblo wthsi error.

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

Deepndnig no teh error ,eihterr ebiuldt hei ndxe pratiiton ,ord ro pan drec-retae hte netier idnex.

update : 24-05-2017
ORA-26023

ORA-26023 - index string.string partition string was made unusable due to:
ORA-26023 - index string.string partition string was made unusable due to:

  • ora-00601 : cleanup lock conflict
  • ora-06954 : Illegal file name
  • ora-14101 : partition extended table name cannot refer to a synonym
  • ora-00399 : corrupt change description in redo log
  • ora-19121 : duplicate attribute definition - string
  • ora-29871 : invalid alter option for a domain index
  • ora-31600 : invalid input value string for parameter string in function string
  • ora-12322 : unable to mount database (link name string)
  • ora-00232 : snapshot control file is nonexistent, corrupt, or unreadable
  • ora-32612 : invalid use of FOR loop
  • ora-26694 : error while enqueueing into queue string.string
  • ora-16721 : unable to set LOG_ARCHIVE_DEST_n initialization parameters
  • ora-13356 : adjacent points in a geometry are redundant
  • ora-36636 : (XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension.
  • ora-06500 : PL/SQL: storage error
  • ora-28293 : No matched Kerberos Principal found in any user entry
  • ora-27080 : too many files open
  • ora-01799 : a column may not be outer-joined to a subquery
  • ora-23381 : generated object for base object string.string@string does not exist
  • ora-03286 : ALLOCATE EXTENT not valid for HASH CLUSTERS
  • ora-02202 : no more tables permitted in this cluster
  • ora-38954 : Cross platform transport is not supported between source platform identifier string and target platform identifier string
  • ora-29930 : COMPUTE ANCILLARY DATA specified without the INDEX CONTEXT clause
  • ora-31230 : DBMS_LDAP: unable to dynamically allocate additional memory
  • ora-39148 : unable to import data into pre-existing queue table string. Table_exists_action of string being ignored for this table
  • ora-31492 : could not set session parameters for LogMiner session
  • ora-07470 : snclget: cannot get cluster number.
  • ora-06733 : TLI Driver: failed to receive disconnect
  • ora-29878 : warning in the execution of ODCIINDEXTRUNCATE routine
  • ora-31015 : Attempted to insert entry without name
  • 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.