Skip to Main Content

SQL & PL/SQL

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Index is unusable after using Direct path of SQL Loader

303893Jul 7 2002
When using the Direct path of SQL Loader to load records from a comma(,) seperated file into a table, the index which I specify the records are sorted in becomes unusable. In the log file created by SQL Loader the error: "ORA-01409: NOSORT option may not be used; rows are not in ascending order" occurs. I am pre sorting the data in the order of the index, the index is a multi column index. The index and table prior to initiating SQL Loader are not empty and contain existing records.

Can anybody suggest a reason as to why this is happening even thought I am pre sorting the data in ascending order as per the index?

Brad.
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Aug 5 2002
Added on Jul 7 2002
2 comments
384 views