ORA-26024: SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable

Cause : User reuqested SIKP_UNUSALBE_INDEXSE option ,and thei ndex semgent *w as in uunsable satte prio rto the ebginningo f the laod.

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

Informaitonal onyl. User iwll needt o eithe rrebuildt he inde x * or nidex parittion, o rre-creaet the inedx.

update : 26-04-2017
ORA-26024

ORA-26024 - SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable
ORA-26024 - SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable

  • ora-28181 : proxy 'string' failed to enable one or more of the specified initial roles for client 'string'
  • ora-01226 : file header of log member is inconsistent with other members
  • ora-31463 : logfile location string is an empty directory
  • ora-10617 : Cannot create rollback segment in dictionary managed tablespace
  • ora-30493 : The percentile value should be a number between 0 and 1.
  • ora-19335 : Invalid format type object
  • ora-37107 : (XSVPART07) Attempt to write to non-existent partition of workspace object.
  • ora-01530 : a database already mounted by the instance
  • ora-36992 : (XSRELGID09) A level relation is needed to produce a surrogate dimension gid.
  • ora-16501 : the Data Guard broker operation failed
  • ora-12447 : policy role already exists for policy string
  • ora-01346 : LogMiner processed redo beyond specified reset log scn
  • ora-10707 : Simulate process death for instance registration
  • ora-36393 : (XSMXCLEA03) When using the AGGREGATES, CHANGES or CACHE options, you must specify the ALL keyword.
  • ora-36274 : (XSCGMDLAGG05) The operator used in this equation needs a weight variable.
  • ora-27076 : unable to set limit for open files
  • ora-01784 : RECOVERABLE cannot be specified with database media recovery disabled
  • ora-36278 : (XSCGMDLAGG07) workspace object does not exist or is not valueset.
  • ora-14150 : missing SUBPARTITION keyword
  • ora-12060 : shape of prebuilt table does not match definition query
  • ora-12212 : TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
  • ora-32509 : watchpoint was already deleted
  • ora-06124 : NETTCP: timeout waiting for ORASRV
  • ora-07755 : slemcf: fseek before read failure
  • ora-30075 : TIME/TIMESTAMP WITH TIME ZONE literal must be specified in CHECK constraint
  • ora-39155 : error expanding dump file name "string"
  • ora-19910 : can not change recovery target incarnation in control file
  • ora-31047 : Could not retrieve resource data at path string
  • ora-13153 : invalid high water mark specified
  • ora-24099 : operation not allowed for 8.0 compatible queues
  • 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.