Interested to Buy Any Domain ? << Click Here >> for more details...
SQL*Loader-00258: Maximum number of SORTED INDEXES (number)
exceeded on table string
- 1 Answers
- 2917 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
Cause: There are too many indexes in the SORTED INDEX
clause. The message displays the maximum number that are
permitted.
Action: Reduce the number of indexes specified in the SORTED
INDEX clause or use the conventional path load instead of
the direct path load.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
ORA-26029: index string.string partition string initially in unusable state
RMAN-05017: no copy of datafile number found to recover
IMG-02003: 2FF03 - incorrect color histogram feature specification
When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............
NZE-28890: Entrust Login Failed
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?
IMP-00064: Definition of LOB was truncated by export
ORA-26032: index string.string loading aborted after string keys
NZE-28868: Peer certificate chain check failed.
ORA-26030: index string.string had string partitions made unusable due to:
ORA-16627: No standby databases support the overall protection mode.
ORA-26076: cannot set or reset value after direct path structure is allocated
ORA-16516: The current state is invalid for the attempted operation.
