ROWID captured by index suspect

Through the Partition Table analysis, we found that the original table structure was renamed without indexing, and a new table was created. After the analysis, we found that the index was used!

Is it a partition storage parameter? Or the number of partitions cannot be reached.

Storage
(
Initial 80 K
Minextents 1
Maxextents unlimited
);

Continue the experiment without indexing!

For the transformed table, the partition is continuously reduced. The test still adopts indexes to reduce unnecessary fields, and the two indexes are retained. The fields required for key indexes are also indexed.
 

Create table t_test_2
(Id number,
Name varchar2 (35 ),
Create_time date
) Partition by range (create_time)

Create index idx_idname_test2 on t_test_2 (id, name );

Create table USER_SUM_DAY_201210
(
Recdate number (8) not null,
Operid number (10) default 0 not null,
Contentid number (10) default 0 not null,
Provcode number (5) default 0 not null,
Createtime date default sysdate not null,
Modifytime date default sysdate not null
)
Partition by range (PROVCODE );

Create index IDX_USER_SUM_DAY_201210_N1 on USER_SUM_DAY_201210 (RECDATE, OPERID );

The only difference is that id number and recdate number (8) are not null, not empty.

1 2 Next Page