ORA-01409 NOSORT option may not be used

Question

Hi all,
We've got a range partitioned table, each partition resides in a different tablespace (locally managed) thus :
create tablespace abcblast_hit_test_data1
datafile '/export/data/oracle/HLDDEV05/abcblast_hit_test_data1.dbf'
size 2600m extent management local uniform size 2500m;
create tablespace abcblast_hit_test_data2
datafile '/export/data/oracle/HLDDEV05/abcblast_hit_test_data2.dbf'
size 2600m extent management local uniform size 2500m;
Two large SORTED files of data are sql*loaded into each partition, taking up ONE extent in each partition
I then try to create a non-unique index on the table using NOSORT and get the error ORA-01409 NOSORT option may not be used; rows are not in ascending order
... with the following reasoning :
For non-unique indexes the ROWID is considered part of the index key. This means that two rows that appear to be stored in ascending order may not be. If you create an index NOSORT, and two of the rows in the table have the same index values, but get split across two extents, the data block address of the first block in the second extent can be less than the data block address of the last block in the first extent. If these addresses are not in ascending order, the ROWIDs are not either. Since these ROWIDs are considered part of the index key, the index key is not in ascending order, and the create index NOSORT fails.
BUT the data for each partition DOES reside in one extent :
select partition_name, tablespace_name, extent_id, bytes
from dba_extents
where segment_name = 'ABCBLAST_HIT'
and segment_type = 'TABLE PARTITION';
PARTITION_NAME     TABLESPACE_NAME          EXTENT_ID     BYTES
PART_01          ABCBLAST_HIT_TEST_DATA1     0          2621440000
PART_02          ABCBLAST_HIT_TEST_DATA2     0          2621440000
(Oracle 9.0.1 on Linux)
HELP !!!! Does this mean we can't use NOSORT when building indexes on partitioned tables ?!
(Note : if NOSORT is not used then a sort is performed which we are trying to avoid - final table will contain 1.6 billion rows and will consist of 50 partitions)

Answer 1

Hi ,
Still i am facing same error like. Can any body help me..
The following index(es) on table KA31CVLA.CITY were processed:
index KA31CVLA.CITY_PK was made unusable due to:
ORA-01409: NOSORT option may not be used; rows are not in ascending order
index KA31CVLA.CITY_UQ01 loaded successfully with 29761 keys
i have create one table CITY in user KA31CVLA.
CREATE TABLE CITY
CNTRY_CD VARCHAR2(2 BYTE) NOT NULL,
CITY_NM VARCHAR2(40 BYTE) NOT NULL,
SEQ_NBR NUMBER(10) NOT NULL,
POSTL_STT_EQNT_CD VARCHAR2(9 BYTE),
LATITUDE NUMBER(9,5) NOT NULL,
LONGITUDE NUMBER(9,5) NOT NULL
and then added primary constraints
ALTER TABLE CITY ADD CONSTRAINT KA31CVLA.CITY_PK PRIMARY KEY (CNTRY_CD, CITY_NM, SEQ_NBR)
after this default unique index created as below
CREATE UNIQUE INDEX KA31CVLA.CITY_PK ON KA31CVLA.CITY (CNTRY_CD, CITY_NM, SEQ_NBR)
after that i have added one more constraints is
CREATE UNIQUE INDEX KA31CVLA.CITY_UQ01 ON KA31CVLA.CITY (CITY_NM, POSTL_STT_EQNT_CD, CNTRY_CD, SEQ_NBR)
Now trying to load data to KA31CVLA.CITY table through SQLLDR
here is the command which i am executing to insert..
SQLLDR CONTROL=D:\GMVS\city.ctl, DATA=D:\GMVS\sorted_city.dat log=D:\GMVS\sorted_log.log USERID="KA31CVLA/KA31CVLA123" DIRECT=Y
Here is the control file details
options (direct=true)
unrecoverable
load data
truncate
into table KA31CVLA.city
sorted indexes (city_PK)
reenable disabled_constraints
fields terminated by "^"
trailing nullcols
(cntry_cd char,
city_nm char,
seq_nbr integer external,
postl_stt_eqnt_cd Char,
latitude integer external,
longitude integer external)
The total records insertd to table but i am getting above error in log files.
The following index(es) on table KA31CVLA.CITY were processed:
index KA31CVLA.CITY_PK was made unusable due to:
ORA-01409: NOSORT option may not be used; rows are not in ascending order
index KA31CVLA.CITY_UQ01 loaded successfully with 29761 keys