ORA-01409: NOSORT option may not be used; rows are not in
ascending order
- 1 Answers
- 2738 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-24378: user callbacks not allowed for this call
AMD-00102: invalid metadata entity: string "string"
ORA-12702: invalid NLS parameter string used in SQL function
ORA-31612: Allocation of process descriptor failed.
ORA-31433: subscriber view does not exist
RMAN-06516: time specified in KEEP UNTIL clause must be be after today
ORA-31211: DBMS_LDAP: PL/SQL - Invalid LDAP entry dn.
ORA-38612: FI item length cannot exceed half of one database block.
ORA-34181: (MXCHGDCL21) workspace object is not a partitioned VARIABLE.
ORA-02202: no more tables permitted in this cluster
ORA-07507: scgcm: unexpected lock status condition
PCC-02399: Illegal CHAR_MAP option value for DBMS=V6. Option ignored.
Oracle Errors 
