ORA-14134: indexes cannot use both DESC and REVERSE

Cause : An attempt was made to make a reverse index with some index columns marked DESC.

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

Do not use DESC in reverse indexes. The rule-based optimizer can scan indexes backwards, which allows a normal reverse index to simulate a reverse index with columns marked DESC.

update : 21-08-2017
ORA-14134

ORA-14134 - indexes cannot use both DESC and REVERSE
ORA-14134 - indexes cannot use both DESC and REVERSE

  • ora-07205 : slgtd: time error, unable to obtain time.
  • ora-00055 : maximum number of DML locks exceeded
  • ora-06446 : ssvpstevrg: Failed with unexpected error number.
  • ora-22998 : CLOB or NCLOB in multibyte character set not supported
  • ora-12465 : Not authorized for read or write on specified groups or compartments
  • ora-15042 : ASM disk "string" is missing
  • ora-31527 : could not find source column string for CDC change table string.string
  • ora-01664 : Transaction which has expanded the Sort Segment has aborted
  • ora-13626 : The specified object string is not valid for task string.
  • ora-10932 : trace name context forever
  • ora-25449 : invalid variable name: string
  • ora-14125 : REVERSE/NOREVERSE may not be specified in this context
  • ora-16166 : LGWR network server failed to send remote message
  • ora-02231 : missing or invalid option to ALTER DATABASE
  • ora-34896 : (PPMONTHS00) At least 12 month names must be given. Only number were provided.
  • ora-23400 : invalid materialized view name "string"
  • ora-36221 : (XSLPDSC02) LIST number and LIST number have different base dimensions.
  • ora-14601 : Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template
  • ora-06801 : TLI Driver: listen for SPX server reconnect failed
  • ora-24092 : invalid value string specified
  • ora-25456 : rule set was modified or evaluation terminated for iterator: string
  • ora-26004 : Tables loaded through the direct path may not be clustered
  • ora-29377 : consumer group string is not part of top-plan string
  • ora-29807 : specified operator does not exist
  • ora-24415 : Missing or null username.
  • ora-12005 : may not schedule automatic refresh for times in the past
  • ora-02081 : database link is not open
  • ora-09344 : spsig: error signalling thread
  • ora-39058 : current object skipped: string of type string
  • ora-38731 : Expected version string does not match string in log header.
  • 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.