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-12815: value for INSTANCES must be greater than 0

1 Answers  

---

ORA-02356: The database is out of space. The load cannot continue

1 Answers  

---

ORA-19028: Invalid ADT parameter passed to toObject() function

1 Answers  

---

ORA-06713: TLI Driver: error on connect

1 Answers  

---

ORA-21706: duration does not exist or is invalid

1 Answers  

---

ORA-14632: cannot specify PARALLEL clause when adding a List subpartition

1 Answers  

---

ORA-03233: unable to extend table string.string subpartition string by string in tablespace string

1 Answers  

---

DRG-11622: URL store: unknown HTTP error getting string

1 Answers  

---

RMAN-08025: channel string: copied controlfile copy

1 Answers  

---

TNS-00111: Failed to get configuration data from file

1 Answers  

---

ORA-16211: unsupported record found in the archived redo log

1 Answers  

---

RMAN-08059: media recovery failed

1 Answers  

---