Regarding Range Partition

Hi,
Is it possible to add a partition which will only contain NULL values for RANGE PARTITIONING.
Actually I cann't add a partition like "VALUES LESS THAN (MAXVALUE)"
as dynamically we will drop and add partition in this table and if I add a partition like "VALUES LESS THAN (MAXVALUE)" then we cann't add a partition, as it will gives an error "ORA-14074: partition bound must collate higher than that of the last partition". Is there any way of adding only NULL partition for range partition.
Thanks in advance,
Koushik

Hi,
Yes, you won't be able to add a new partition.. but did you think about SPLIT partition instead of ADD ?
Regards,
Yoann.

Similar Messages

NULL partition key in RANGE partition

All,
This is regarding partitioning a table using RANGE partition method. But the partition key contains null. How do I handle this situation? This is because there is no DEFAULT partition in RANGE partition though its present in LIST partition. Will rows with NULL partition key fall in MAXVALUE partition? Seeking your guidence.
Thanks,
...

NULLS would fit into the MAXVAL partition yes.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/partconc.htm#sthref2590
Thanks
Paul

Partition Pruning on Interval Range Partitioned Table not happening when SYSDATE used in Where Clause

We have tables that are interval range partitioned on a DATE column, with a partition for each day - all very standard and straight out of Oracle doc.
A 3rd party application queries the tables to find number of rows based on date range that is on the column used for the partition key.
This application uses date range specified relative to current date - i.e. for last two days would be "..startdate > SYSDATE -2 " - but partition pruning does not take place and the explain plan shows that every partition is included.
By presenting the query using the date in a variable partition pruning does table place, and query obviously performs much better.
DB is 11.2.0.3 on RHEL6, and default parameters set - i.e. nothing changed that would influence optimizer behavior to something unusual.
I can't work out why this would be so. It very easy to reproduce with simple test case below.
I'd be very interested to hear any thoughts on why it is this way and whether anything can be done to permit the partition pruning to work with a query including SYSDATE as it would be difficult to get the application code changed.
Furthermore to make a case to change the code I would need an explanation of why querying using SYSDATE is not good practice, and I don't know of any such information.
1) Create simple partitioned table
CREATETABLE part_test
   (id                      NUMBER NOT NULL,
    starttime               DATE NOT NULL,
    CONSTRAINT pk_part_test PRIMARY KEY (id))
PARTITION BY RANGE (starttime) INTERVAL (NUMTODSINTERVAL(1,'day')) (PARTITION p0 VALUES LESS THAN (TO_DATE('01-01-2013','DD-MM-YYYY')));
2) Populate table 1million rows spread between 10 partitions
BEGIN
    FOR i IN 1..1000000
    LOOP
        INSERT INTO part_test (id, starttime) VALUES (i, SYSDATE - DBMS_RANDOM.value(low => 1, high => 10));
    END LOOP;
END;
EXEC dbms_stats.gather_table_stats('SUPER_CONF','PART_TEST');
3) Query the Table for data from last 2 days using SYSDATE in clause
EXPLAIN PLAN FOR
SELECT count(*)
FROM    part_test
WHERE   starttime >= SYSDATE - 2;
| Id | Operation                 | Name      | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
|   0 | SELECT STATEMENT          |           |     1 |     8 | 7895 (1)| 00:00:01 |       |       |
|   1 | SORT AGGREGATE           |           |     1 |     8 |            |          |       |       |
|   2 |   PARTITION RANGE ITERATOR|           |   111K|   867K| 7895   (1)| 00:00:01 |   KEY |1048575|
|* 3 |    TABLE ACCESS FULL      | PART_TEST |   111K|   867K| 7895   (1)| 00:00:01 |   KEY |1048575|
Predicate Information (identified by operation id):
   3 - filter("STARTTIME">=SYSDATE@!-2)
4) Now do the same query but with SYSDATE - 2 presented as a literal value.
This query returns the same answer but very different cost.
EXPLAIN PLAN FOR
SELECT count(*)
FROM part_test
WHERE starttime >= (to_date('23122013:0950','DDMMYYYY:HH24MI'))-2;
| Id | Operation                 | Name      | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
|   0 | SELECT STATEMENT          |           |     1 |     8 |   131 (0)| 00:00:01 |       |       |
|   1 | SORT AGGREGATE           |           |     1 |     8 |            |          |       |       |
|   2 |   PARTITION RANGE ITERATOR|           |   111K|   867K|   131   (0)| 00:00:01 |   356 |1048575|
|* 3 |    TABLE ACCESS FULL      | PART_TEST |   111K|   867K|   131   (0)| 00:00:01 |   356 |1048575|
Predicate Information (identified by operation id):
   3 - filter("STARTTIME">=TO_DATE(' 2013-12-21 09:50:00', 'syyyy-mm-dd hh24:mi:ss'))
thanks in anticipation
Jim

As Jonathan has already pointed out there are situations where the CBO knows that partition pruning will occur but is unable to identify those partitions at parse time. The CBO will then use a dynamic pruning which means determine the partitions to eliminate dynamically at run time. This is why you see the KEY information instead of a known partition number. This is to occur mainly when you compare a function to your partition key i.e. where partition_key = function. And SYSDATE is a function. For the other bizarre PSTOP number (1048575) see this blog
http://hourim.wordpress.com/2013/11/08/interval-partitioning-and-pstop-in-execution-plan/
Best regards
Mohamed Houri

Oracle 11g List - Range Partition - Help Needed

Hi All,
I want to create a composite partition (LIST-RANGE) but RANGE partition should using interval partition
This is my query .
CREATE TABLE "DMSDB"."DEVICE_UTILS"
(     "ULID" VARCHAR2(100 CHAR),
     "IP_ADDRESS" VARCHAR2(24 CHAR),
     "PORT" VARCHAR2(8 CHAR),
     "SHUTDOWN" NUMBER(10,0),
     "LINE_TYPE" NUMBER(10,0) DEFAULT '0',
     "OCCUPIED" NUMBER(10,0),
     "UTILIZATION" NUMBER(10,0),
     "IDLE_TIME" VARCHAR2(32 CHAR),
     "ACTIVATION_TIME" VARCHAR2(32 CHAR),
     "PULLED_DATE" TIMESTAMP (6) DEFAULT SYSDATE,
     "ACCESS_TIME" TIMESTAMP (6) DEFAULT SYSDATE
PARTITION BY LIST(ULID)
          PARTITION PART_DEVUTILS_ULID VALUES (DEFAULT)
     SUBPARTITION BY RANGE( PULLED_DATE)
     PARTITION PART_DEVUTILS_WEEK INTERVAL (NUMTOYMINTERVAL(1,'WEEK'))
Somehow its not working. can you please suggest where i am making mistake?

Interval partitioning is not supported at the subpartition level.
http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_7002.htm#BABCDDIA
Regards
Girish Sharma

INTERVAL in Range Partition?

Hi All,
In Teradata, we have one option named INTERVAL which helps to define the interval at which we want the range partition to work.
In HANA, I see that we have to mention all the dates respectively for each partition.
Do you know if there any option like INTERVAL in HANA?
Regards,
Krishna Tangudu

Hi Krishna,
currently (SPS 8) there is no such half-automatic partition creation functionality available for SAP HANA.
- Lars

Range Partitioning Existing table

Hi,
I have a table with numeric field. I want to range partition the existing table. I used the following query
alter table dept add partition by range(deptno) (
partition p1 values less than (20),
partition p1 values less than (40))
It gives me ORA-00902: invalid datatype.
What am I doing wrong? Is it possible to partition an existing table?
Regards,
Subbu S.

Hi,
You cannot partition an existing table with an ALTER TABLE command. There are couple of techinques with which you can partition an existing table, like:
1) Rename existing table, create a new partitoned table and move data.
2) Using DBMS_REDEFINITION package.
Have a look at the following links for details:
http://www.oracle-base.com/articles/misc/PartitioningAnExistingTable.php
http://www.dba-oracle.com/oracle_news/2004_3_9_rittman.htm
Regards
Asif Momen
http://momendba.blogspot.com

Range Partition Concept

Hi,
I am having problem understanding a concept of Range Partition. While creating a range based partition this is the syntax generally used:
CREATE TABLE emp (
empno NUMBER(4),
ename VARCHAR2(30),
sal NUMBER
PARTITION BY RANGE(empno) (
partition e1 values less than (1000) tablespace ts1,
partition e2 values less than (2000) tablespace ts2,
partition e3 values less than (3000) tablespace ts3,
partition e4 values less than (4000) tablespace ts4,
partition em values less than (MAXVALUE) tablespace tsm
As per the above logic an empno with value 1500 would be inserted into tablespace e2. But the value 1500 is also less than 3000, then how to confirm (or why) that this is not getting inserted into tablespace e3.
DB Version: 10.2.0.1
Platform: Generic
Thanks for your valuable time.
Regards,
Joy

As per the above logic an empno with value 1500 would be inserted into tablespace e2.Yes you are right
But the value 1500 is also less than 3000, then how to confirm (or why) that this is not getting inserted into tablespace e3.Because e3 partition also implicitly denotes "greater than 2000" apart from less than 3000.
lesser than the value you mentioned & greater than that the previous partition value (if applicable)
When using range partitioning, consider the following rules:
* Each partition has a VALUES LESS THAN clause, which specifies a noninclusive upper bound for the partitions. Any binary values of the partition key equal to or higher than this literal are added to the next higher partition.
** All partitions, except the first, have an implicit lower bound specified by the VALUES LESS THAN clause on the previous partition.*
* A MAXVALUE literal can be defined for the highest partition. MAXVALUE represents a virtual infinite value that sorts higher than any other possible value for the partition key, including the null value.
HTH..

Creating Local partitioned index on Range-Partitioned table.

Hi All,
Database Version: Oracle 8i
OS Platform: Solaris
I need to create Local-Partitioned index on a column in Range-Partitioned table having 8 million records, is there any way to perform it in fastest way.
I think we can use Nologging, Parallel, Unrecoverable options.
But while considering Undo and Redo also mainly time required to perform this activity....Which is the best method ?
Please guide me to perform it in fastest way and also online !!!
-Yasser

YasserRACDBA wrote:
3. CREATE INDEX CSB_CLIENT_CODE ON CS_BILLING (CLIENT_CODE) LOCAL
NOLOGGING PARALLEL (DEGREE 14) online;
4. Analyze the table with cascade option.
Do you think this is the only method to perform operation in fastest way? As table contain 8 million records and its production database.Yasser,
if all partitions should go to the same tablespace then you don't need to specify it for each partition.
In addition you could use the "COMPUTE STATISTICS" clause then you don't need to analyze, if you want to do it only because of the added index.
If you want to do it separately, then analyze only the index. Of course, if you want to analyze the table, too, your approach is fine.
So this is how the statement could look like:
CREATE INDEX CSB_CLIENT_CODE ON CS_BILLING (CLIENT_CODE) TABLESPACE CS_BILLING LOCAL NOLOGGING PARALLEL (DEGREE 14) ONLINE COMPUTE STATISTICS;
If this operation exceeds particular time window....can i kill the process?...What worst will happen if i kill this process?Killing an ONLINE operation is a bit of a mess... You're already quite on the edge (parallel, online, possibly compute statistics) with this statement. The ONLINE operation creates an IOT table to record the changes to the underlying table during the build operation. All these things need to be cleaned up if the operation fails or the process dies/gets killed. This cleanup is supposed to be performed by the SMON process if I remember correctly. I remember that I once ran into trouble in 8i after such an operation failed, may be I got even an ORA-00600 when I tried to access the table afterwards.
It's not unlikely that your 8.1.7.2 makes your worries with this kind of statement, so be prepared.
How much time it may take? (Just to be on safer side)The time it takes to scan the whole table (if the information can't read from another index), the sorting operation, plus writing the segment, plus any wait time due to concurrent DML / locks, plus the time to process the table that holds the changes that were done to the table while building the index.
You can try to run an EXPLAIN PLAN on your create index statement which will give you a cost indication if you're using the cost based optimizer.
Please suggest me if any other way exists to perform in fastest way.Since you will need to sort 8 million rows, if you have sufficient memory you could bump up the SORT_AREA_SIZE for your session temporarily to sort as much as possible in RAM.
-- Use e.g. 100000000 to allow a 100M SORT_AREA_SIZE
ALTER SESSION SET SORT_AREA_SIZE = <something_large>;
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

Create range partition

hi ,
Oracle 10.2.0.1.0
I'm getting error while creating a range partition to already existing table (method employed : partition swap method ) .
PF screen shot of error
SQL> ed
Wrote file afiedt.buf
1 create table employee_details_temp partition by range (eid) (
2 partition eid_1r values less than (1000)
3 partition eid_2r values less than (20000)
4 partition eid_3r values less than (40000)
5 partition eid_3r values less than (maxvalue)
6* )
SQL> /
partition eid_2r values less than (20000)
ERROR at line 3:
ORA-14020: this physical attribute may not be specified for a table partitionalso ,
SQL> ed
Wrote file afiedt.buf
1 create table employee_details_temp partition by range (eid) (
2 partition eid_1r values less than (1000)
3 partition eid_2r values less than (20000)
4 partition eid_3r values less than (40000)
5 partition eid_3r values less than (maxvalue)
6 ) as select * from employee_details where 1=1;
7* /
SQL> /
partition eid_2r values less than (20000)
ERROR at line 3:
ORA-14020: this physical attribute may not be specified for a table partition please help .

answered .

How to find out the min & max partition_id in a range partition?

Hi we have a table set up by range partition
In the table creation script. It goes something like:
PARTITION PARTD_CUST_3_1_NEW VALUES LESS THAN ('39500')
so how we can find out this number '39500' from some of the data_dictionary view?
What we want to do is to set up parallel processing (do-it-yourself) based on partition.
So the number of parallel process will be based on this ID-range.
I can find out how many partitions are there by using something like this:
SELECT COUNT(*)
FROM all_tab_partitions WHERE table_owner='OWNER_NAME' AND table_name='TABLE_NAME'
We have 5 partitions now but the table structure can change in the near future even this table has moer than 130Million rows
I do not want to hardcode this "39500" just in case the table structure changes (partition structure changes)
Any idea ??

vxwo0owxv wrote:
Hi we have a table set up by range partition
In the table creation script. It goes something like:
PARTITION PARTD_CUST_3_1_NEW VALUES LESS THAN ('39500')
so how we can find out this number '39500' from some of the data_dictionary view?
What we want to do is to set up parallel processing (do-it-yourself) based on partition.
So the number of parallel process will be based on this ID-range.
I can find out how many partitions are there by using something like this:
SELECT COUNT(*)
FROM all_tab_partitions WHERE table_owner='OWNER_NAME' AND table_name='TABLE_NAME'
We have 5 partitions now but the table structure can change in the near future even this table has moer than 130Million rows
I do not want to hardcode this "39500" just in case the table structure changes (partition structure changes)
Any idea ??query DBA_TAB_PARTITIONS.HIGH_VALUE

Non-Partitioned Global Index on Range-Partitioned Table.

Hi All,
Is it possible to create Non-Partitioned Global Index on Range-Partitioned Table?
We have 4 indexes on CS_BILLING range-partitioned table, in which one is CBS_CLIENT_CODE(*local partitioned index*) and others are unknown types of index to me??
Means other 3 indexes are what type indexes ...either non-partitioned global index OR non-partitioned normal index??
Also if we create index as :(create index i_name on t_name(c_name)) By default it will create Global index. Please correct me......
Please help me in identifying other 3 indexes types by referring below ouputs!!!
select INDEX_NAME,TABLE_NAME,PARTITIONING_TYPE,LOCALITY from dba_part_indexes where TABLE_NAME='CS_BILLING';
INDEX_NAME TABLE_NAME PARTITI LOCALI
CSB_CLIENT_CODE CS_BILLING RANGE LOCAL
select index_name,index_type,table_name,table_type,PARTITIONED from dba_indexes where table_name='CS_BILLING';
INDEX_NAME INDEX_TYPE TABLE_NAME TABLE_TYPE PAR
CSB_CREATE_DATE NORMAL CS_BILLING TABLE NO
CSB_SUBMIT_ORDER NORMAL CS_BILLING TABLE NO
CSB_CLIENT_CODE NORMAL CS_BILLING TABLE YES
CSB_ORDER_NBR NORMAL CS_BILLING TABLE NO
select INDEX_OWNER,INDEX_NAME,TABLE_NAME,COLUMN_NAME from dba_ind_columns where TABLE_NAME='CS_BILLING';
INDEX_OWNER INDEX_NAME TABLE_NAME COLUMN_NAME
RPADMIN CSB_CREATE_DATE CS_BILLING CREATE_DATE
RPADMIN CSB_SUBMIT_ORDER CS_BILLING SUBMIT_TO_INVOICE
RPADMIN CSB_SUBMIT_ORDER CS_BILLING ORDER_NBR
RPADMIN CSB_CLIENT_CODE CS_BILLING CLIENT_CODE
RPADMIN CSB_ORDER_NBR CS_BILLING ORDER_NBR
select dip.index_name, dpi.locality, dip.partition_name, dip.status
from dba_part_indexes dpi, dba_ind_partitions dip
where dpi.table_name ='CS_BILLING'
and dpi.index_name = dip.index_name;
INDEX_NAME LOCALI PARTITION_NAME STATUS
CSB_CLIENT_CODE LOCAL CSB_2006_4Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2006_3Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2007_1Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2007_2Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2007_3Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2007_4Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2008_1Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2008_2Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2008_3Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2008_4Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2009_1Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2009_2Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2009_3Q USABLE
CSB_CLIENT_CODE LOCAL CSB_2009_4Q USABLE
select * from dba_part_indexes
where table_name ='CS_BILLING'
and locality = 'GLOBAL';
no rows selected
-Yasser
Edited by: YasserRACDBA on Mar 5, 2009 11:45 PM

Yaseer,
Is it possible to create Non-Partitioned and Global Index on Range-Partitioned Table?
Yes
We have 4 indexes on CS_BILLING range-partitioned table, in which one is CBS_CLIENT_CODE(*local partitioned index*) and others are unknown types of index to me??
Means other 3 indexes are what type indexes ...either non-partitioned global index OR non-partitioned normal index??
You got local index and 3 non-partitioned "NORMAL" b-tree tyep indexes
Also if we create index as :(create index i_name on t_name(c_name)) By default it will create Global index. Please correct me......
Above staement will create non-partitioned index
Here is an example of creating global partitioned indexes
CREATE INDEX month_ix ON sales(sales_month)
   GLOBAL PARTITION BY RANGE(sales_month)
      (PARTITION pm1_ix VALUES LESS THAN (2)
       PARTITION pm2_ix VALUES LESS THAN (3)
       PARTITION pm3_ix VALUES LESS THAN (4)
        PARTITION pm12_ix VALUES LESS THAN (MAXVALUE));Regards

How to Implement 30 days Range Partitioning with Date column. Not Interval

Hi,
I am using the db:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit
Current table structure is:
CREATE TABLE A
a NUMBER,
CreationDate DATE
PARTITION BY RANGE (CreationDate)
INTERVAL ( NUMTODSINTERVAL (30, 'DAY') )
(PARTITION P_FIRST
VALUES LESS THAN (TIMESTAMP ' 2001-01-01 00:00:00'))
How can I define virtual column based partitioning with RANGE partitioning without using INTERVAL partitioning.
And that is with Intervals of 30 days.
For monthly I am trying as
CREATE TABLE A
a NUMBER,
CreationDate DATE,
monthly_interval date as (to_char(CreationDate,'MM-YYYY')) VIRTUAL
PARTITION BY RANGE (monthly_interval)
partition p_AUG12 values less than (to_date('08-2012','mm-yyyy')),
partition p_SEP12 values less than (to_date('09-2012','mm-yyyy')),
partition p_OCT12 values less than (to_date('10-2012','mm-yyyy'))
Enable ROw Movement
BUT CAN'T INSERT the data even for that:
Insert into a (a, CreationDate)
Values (1, '12-10-2012')
Insert into a (a, CreationDate)
Values (1, '12-10-2012')
Please suggest..

Hi rp,
Interval Partitioned to Range. Created Daily Partitions from Monthly Part. got complicated so I am posting here.
Basically,
I know Interval Partitioning is a kind of Range partitioning. But explicitly for Interval Partitioned tables XML Indexes are not allowed as discussed here:
XMLIndexes on an Interval Partitioned Table??
I can do monthly partitions as :
CREATE TABLE A
a NUMBER,
CreationDate DATE,
monthly_interval varchar2(8) as (to_char(CreationDate,'MM-YYYY')) VIRTUAL
PARTITION BY RANGE (monthly_interval)
partition p_AUG12 values less than ('09-2012'),
partition p_SEP12 values less than ('10-2012'),
partition p_OCT12 values less than ('11-2012')
) Enable ROw Movement
Insert into a (a, CreationDate)
Values (1, '12-SEP-2012')
Insert into a (a, CreationDate)
Values (1, '14-SEP-2012')
Select * from A partition (p_SEP12)
Select * from A partition (p_AUG12)
Select * from A partition (p_OCT12)
Can we do it for 30 days partitions, instead of the monthly partitions. ANY suggestions..
Thanks..

Is there any plan of allowing non-range partitioning of spatial indexes

our application is really lacking the ability of spatial index being partitioned by list. We are binning information in our data warehouse by spatial locations, and when we query it (actually, MapViewer is generating a tile), entire geometry set is searched because table is list-partitioned and we cannot have local spatial index.

Hi,
I'm not in a position to answer the question about list partitioning, but would a pseudo-list partition implemented as a range partition work? For example, something like this:
CREATE TABLE customers (
first_name    VARCHAR2(20),
last_name     VARCHAR2(20),
address_1     VARCHAR2(20),
address_2     VARCHAR2(20),
city          VARCHAR2(20),
state_abrv    VARCHAR2(3),
postal_code   VARCHAR2(10),
customer_id   NUMBER NOT NULL UNIQUE)
PARTITION BY RANGE (state_abrv)
   PARTITION ALASKA         VALUES LESS THAN ('AKz'),
   PARTITION ALABAMA        VALUES LESS THAN ('ALz'),
   PARTITION ARKANSAS       VALUES LESS THAN ('ARz'),
   PARTITION AMERICANSAMOA VALUES LESS THAN ('ASz'),
   PARTITION ARIZONA        VALUES LESS THAN ('AZz'),
   PARTITION CALIFORNIA     VALUES LESS THAN ('CAz'),
   PARTITION WYOMING        VALUES LESS THAN ('WYz')
   );I've used this method in the past, although I agree a list partitioning solution is much preferred.
Dan

Subpartition existing range partition in Oracle

I have table xyz with following structure
xyz ( vld_dte date,
prd_typ varchar2(100),
sales number
table XYZ is partitioned by range on field vld_dte and partitions are monthly partitions like JAN-2009 , FEB-2009....DEC-2009 and so on.table is currently loaded with data.
How can I modify existing range partition into composite range-list partition so that every partiton is subpartitioned on prd_typ , basically three sub-partitions for every partition 1- Grocery , 2-Home decoration,3-OTHERS

ORA-14759: SET INTERVAL is not legal on this table.
Cause: ALTER TABLE SET INTERVAL is only legal on a range partitioned table with a single partitioning column. Additionally this table cannot have a maxvalue partition.
Action: Use SET INTERVAL only on a valid table
mark answered post as helpful / correct*

Problem with a 2 columns Range Partitioning for a indexed organized table

have an indexed organized table with a 2 column PK. the first field (datum) is a date field the second field (installatieid) is a number(2) field.
Every minute a 7 records are inserted (installatieid 0-6).
I like to partition this table with one partition per year per installatieid.
I tried to do it with:
partition by range(datum,installatieid)
(partition P_2004_0 values less than (to_date('2004-01,'yyyy-mm'),1)
,partition P_2004_6 values less than (to_date('2004-01','yyyy-mm'),7)
partition P_2005_0 values less than (to_date('2005-01','yyyy-mm'),1)
,partition P_2005_6 values less than (to_date('2005-01','yyyy-mm'),7)
but now only the P_2004_0 and P_2005_0 are filled.
I thought about to combine a range partition on datum with a list subpartition on installatieid, but I read this is not allowed with an index organized table.
How can I solve this problem.

partition by range(datum,installatieid)
(partition P_2004_0 values less than
(to_date('2004-01,'yyyy-mm'))
,partition P_2004_6 values less than
(to_date('2004-07','yyyy-mm'))
partition P_2005_0 values less than
(to_date('2005-01','yyyy-mm'))
,partition P_2005_6 values less than
(to_date('2005-07','yyyy-mm'))
? Sorry haven't got time to test it this morning ;0)

Regarding Range Partition

Similar Messages

Maybe you are looking for