- ORA-01409: NOSORT option may not be used; rows are not in ascending order
-
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.
ORA-01463: cannot modify column datatype with current constraint(s)
-
Cause:
An attempt was made to
modify the datatype of column which has referential constraints; or has
check constraints which only allows changing the datatype from CHAR to
VARCHAR or vise versa. -
Action:
Remove the constraint(s) or do not perform the offending operation.
ORA-01485: compile bind length different from execute bind length
-
Cause:
You bound a buffer of
type DTYVCS (VARCHAR with the two byte length in front) and at execute
time the length in the first two bytes is more than the maximum buffer
length (given in the bind call). The number of elements in the array and
the current number of elements in the array cannot be more than the
maximum size of the array. -
Action:
none
- ORA-01500: failure in getting date/time
-
Cause:
During create database or alter tablespace, there was a failure in getting the date and time. -
Action:
Contact your customer support representative.link:http://www.docfans.net/?p=459