ORA-01409: NOSORT option may not be used; rows are not in
ascending order
- 1 Answers
- 2472 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: Creation of index with NOSORT option when rows were
not ascending. For non-unique indexes the rowid is
considered part of the index key. Therefore, if you create
an index nosort and two of the rows in the table have the
same key and are stored in ascending order, but get split
accross two extents where the dba of the first block in the
second extent is less than the dba of the last block in the
first extent, then the create index nosort may fail.
Action: Create the index without the NOSORT option, or
ensure table is stored in one extent.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-02451: duplicate HASHKEYS specification
TNS-00064: INTCTL: Failed to find CMANAGER_NAME in INTCHG.ORA
ORA-19005: Duplicate XMLType LOB storage option
ORA-23420: interval must evaluate to a time in the future
ORA-10644: SYSTEM tablespace cannot be default temporary tablespace
ORA-28602: statement not permitted on tables containing bitmap indexes
ORA-06578: output parameter cannot be a duplicate bind
NNO-00613: disabling FORWARDING-DESIRED on system queries
ORA-02055: distributed update operation failed; rollback required
ORA-16138: end of log stream not received from primary
ORA-38471: ROWIDs for table aliases cannot be null
ORA-02424: potential circular view references or unknown referenced tables
Oracle Errors 
