The second column is only checked when after the first one. All your
entries have a partition value for col1 that is less than 1001, so they all
belong in the first partition. This is expected behavior.
--
HTH. Additions and corrections welcome.
Pete
Author of "Oracle8i: Architecture and Administration Exam Cram"
Now got a life back again that the book is released!
"Controlling developers is like herding cats."
Kevin Loney, Oracle DBA Handbook
"Oh no, it's not. It's much harder than that!"
Bruce Pihlamae, long-term Oracle DBA
"Joe Black" <joe.black_at_home.com> wrote in message
news:tq22nngsdbv404_at_corp.supernews.com...
> I used the following statement to create a partition table:
>
> CREATE TABLE temp
>
> (
>
> col1 number(38),
>
> col2 number(38)
>
> )
>
> PARTITION BY RANGE (col1, col2)
>
> (
>
> PARTITION part1 VALUES LESS THAN (1001, 11),
>
> PARTITION part2 VALUES LESS THAN (1001, 21),
>
> PARTITION part3 VALUES LESS THAN (1101, 11),
>
> PARTITION part4 VALUES LESS THAN (1101, 21))
>
> Records Entered:
>
> 1000, 10
>
> 1000, 20
>
> 1000, 30
>
> 1000, 40
>
> I expected each record to load in to each partition. Instead, they loaded
as
>
> follows:
>
> Part1:
>
> 1000, 10
>
> 1000, 20
>
> Part3:
>
> 1100, 10
>
> 1100, 20
>
> It seems like it ignores the second column condition. Please let me know
if
>
> anyone is aware on how I can implement the partition strategy to work as I
>
> expected.
>
>
>
>
>
Received on Thu Sep 13 2001 - 17:53:43 CDT
