Thank you all for the reply.

Here is the query :

SELECT custnum, media_cd, ext_price, lst_ord_ss, ltd_dol_ss,
______ daycare_ty, dec_sc_is, cont_lvl, pr_daychur, fac_type,
______ aft_sch_pr, ss_line, grade_rng, ss_subgrp, ss_group, list_pri,
______ site_upd_dt, sic_prim8, dec_sc_ss, group_no
___ FROM ssw.multi_mv
___ WHERE country_cd = :sys_b_0
_____ AND mail_cont IN (:sys_b_1, :sys_b_2)
_____ AND mail_site = :sys_b_3
_____ AND dsf_index IN (:sys_b_4, :sys_b_5)
_____ AND list_pri BETWEEN :sys_b_6 AND :sys_b_7
___ ORDER BY custnum


CUSTNUM is not null, has non unique B*tree index on it. Other columns in the where clause
have bitmap indexes.

So, should the optimizer be using the index for the order by clause, provided nls_sort='BINARY' has been set ?.

Is nls_sort should be set separately for client ?.

Chrisrlong's point of presorted data has raised another question ?.

Should the data be sorted in the table which is
created by this :

CREATE table A
as select * from B order by custnum ;

This table is not having any inserts or updates.

I will appreciate any response.

Thanks,