Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-01409: NOSORT option may not be used; rows are not in
ascending order
- 1 Answers
- 3038 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-31181: PL/SQL DOM handle accesses node that is no longer available
TNS-12637: Packet receive failed
ORA-16595: NetSlave process string failed to terminate
ORA-15109: conflicting protection attributes specified
ORA-28293: No matched Kerberos Principal found in any user entry
ORA-23343: no match for specified conflict resolution information
ORA-02839: Sync of blocks to disk failed.
PCC-02404: This indicator variable must be declared as a pointer type
QSM-02019: mv references another mv in FROM clause
NNL-00234: Auto-refresh failure-retry expiration period is currently string
ORA-14105: RECOVERABLE/UNRECOVERABLE may not be specified in this context
NZE-29238: the cryptographic engine could not apply the algorithm
Oracle Errors 
