ORA-26030: index string.string had string partitions made unusable due to:

Cause : A logical index error occurred on a partitioned index which * affected one or more index partitions, which are listed below * this message.

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

The affected index partitions will have to be re-built, or, the * entire index dropped and re-created.

update : 25-09-2017
ORA-26030

ORA-26030 - index string.string had string partitions made unusable due to:
ORA-26030 - index string.string had string partitions made unusable due to:

  • ora-02077 : selects of long columns must be from co-located tables
  • ora-14270 : table is not partitioned by Range or Hash or List method
  • ora-06705 : TLI Driver: remote node is unknown
  • ora-27192 : skgfcls: sbtclose2 returned error - failed to close file
  • ora-26517 : materialized view control entry for 'string.string' was not found
  • ora-26520 : internal memory failure
  • ora-19719 : length for operation name longer than string
  • ora-09368 : Windows 3.1 Two-Task driver unable to spawn ORACLE
  • ora-12714 : invalid national character set specified
  • ora-26692 : invalid value string, string should be in string format
  • ora-25120 : MINIMUM EXTENT option already specified
  • ora-02191 : correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT
  • ora-07504 : scgcmn: $hiber unexpected return
  • ora-31066 : Insertion of string into string creates a cycle
  • ora-19763 : compatibility version string is higher than maximum allowed: string
  • ora-30355 : materialized view container does not exist
  • ora-09932 : Close of ORACLE password file failed.
  • ora-08007 : Further changes to this block by this transaction not allowed
  • ora-12035 : could not use materialized view log on "string"."string"
  • ora-21780 : Maximum number of object durations exceeded.
  • ora-38720 : Missing log file number.
  • ora-06566 : invalid number of rows specified
  • ora-26029 : index string.string partition string initially in unusable state
  • ora-14102 : only one LOGGING or NOLOGGING clause may be specified
  • ora-12633 : No shared authentication services
  • ora-28671 : UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
  • ora-22906 : cannot perform DML on expression or on nested table view column
  • ora-07501 : scgtoa: $deq unexpected return
  • ora-29877 : failed in the execution of the ODCIINDEXUPDATE routine
  • ora-06568 : obsolete ICD procedure called
  • 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.