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-19632: file name not found in controlfile

1 Answers  

---

NNL-00833: Fastest delete processing time: string

1 Answers  

---

ORA-14069: invalid TABLESPACE_NUMBER value

1 Answers  

---

KUP-04069: error fetching data for external table

1 Answers  

---

ORA-16510: messaging error using ksrwait

1 Answers  

---

ORA-07229: slcpuc: error in getting number of CPUs.

1 Answers  

---

RMAN-06140: cannot specify TAG option with LIST INCARNATION

1 Answers  

---

ORA-16704: Cannot set the property because it is read-only

1 Answers  

---

ORA-16109: failed to apply log data from previous primary

1 Answers  

---

ORA-08456: no sign in picture mask but SIGN clause in mask options

1 Answers  

---

RMAN-06584: WARNING: AS BACKUPSET option added due to allocation of multiple channel types

1 Answers  

---

ORA-19556: required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred

1 Answers  

---