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

ORA-16543: invalid request made to broker

1 Answers  

---

TNS-02513: Requested data type does not match retrieved type

1 Answers  

---

ORA-06043: NETDNT: message send failure

1 Answers  

---

ORA-29302: database is not open clone

1 Answers  

---

DRG-11610: URL store: unable to read local file specified by string

1 Answers  

---

ORA-01197: thread string only contains one log

1 Answers  

---

TNS-12515: TNS:listener could not find a handler for this presentation

1 Answers  

---

SQL*Loader-00526: OCI return status: success with info

1 Answers  

---

ORA-24186: wrong object type, could not transform message

1 Answers  

---

ORA-23473: replication RPC processing for "string"."string" is disabled

1 Answers  

---

NNL-01041: Data stream open failures: number

1 Answers  

---

NNL-00202: No shutdown currently scheduled

1 Answers  

---