SQL*Loader-00256: SORTED INDEXES option allowed only for
direct path

Answer Posted / guest

Cause: The SQL*Loader control file contains a SORTED INDEXES
statement, but it was not used in a direct path load.

Action: Specify a direct path load with DIRECT=TRUE on the
command line, remove the statement from the SQL*Loader
control file, or

Please add more information about this Error

Is This Answer Correct ?    0 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

NZE-28868: Peer certificate chain check failed.

2265


ORA-26084: direct path context already finished

1483


ORA-16516: The current state is invalid for the attempted operation.

8070


IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created

1239


ORA-26076: cannot set or reset value after direct path structure is allocated

1476






if the lengths of two wires are same and the area of cross sections is 4:7 then what will be the ratio of current passing through these wires

2234


ORA-26030: index string.string had string partitions made unusable due to:

1562


ORA-26027: unique index string.string partition string initially in unusable state

6161


ORA-26028: index string.string initially in unusable state

3403


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?

2313


ORA-26094: stream format error: input column overflow

2254


ORA-26095: unprocessed stream data exists

2803


invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity

2862


ORA-26032: index string.string loading aborted after string keys

1655


RMAN-05017: no copy of datafile number found to recover

1887