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

Similar Messages

Range partition by a virtual column derived from XMLTYPE

I want to create table and partition it by interval partion (range partition) on a virtual column which is derived from XMLTYPE i get ora-14513 error.
create table dicom_archive_virtual
id integer not null primary key,
parent_id integer, -- where this image is created from
dcm_filename varchar2(60), -- DICOM image file name from import
description varchar2(100), -- description of the image
dicom orddicom, -- DICOM data
image ordimage, -- DICOM data in JPEG format
thumb ordimage, -- DICOM data in JPEG thumbnail
metadata xmltype, -- user customized metadata
isAnonymous integer, -- accessible flag for the research role.
study_date date as
(to_date(substr(extractValue(metadata,'//DATE/text()'),1,10),'yyyy-mm-dd')) virtual)
PARTITION BY RANGE (study_date)
INTERVAL(NUMTOYMINTERVAL(1, 'MONTH'))
( PARTITION p_2005 VALUES LESS THAN (TO_DATE('1-1-2006', 'DD-MM-YYYY')),
PARTITION p_2006 VALUES LESS THAN (TO_DATE('1-1-2007', 'DD-MM-YYYY')),
PARTITION p_2007 VALUES LESS THAN (TO_DATE('1-1-2008', 'DD-MM-YYYY'))
Study_date is a virtual colum which is derived from the column metadata which is of type XMLTYPE,so when i partition on this virtual column i get the follwoing error
SQL Error: ORA-14513: partitioning column may not be of object datatype
So i want to know whether this is not possible or there is any other alternative to achieve this.

I want to create table and partition it by interval partion (range partition) on a virtual column which is derived from XMLTYPE Congratulations on trying to fit as many cutting edge techniques into a single line as possible.
So i want to know whether this is not possible ...The error message is pretty unequivocal.
...or there is any other alternative to achieve this.What you could try is materializing the virtual column, i.e. adding an actual date column which you populate with that code in the insert and update triggers. Inelegant but then complexity often is.
Cheers, APC
blog : http://radiofreetooting.blogspot.com

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..

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

Creating interval parition to existing range partition

I have a table which has range partition on a number column.
CREATE TABLE TEST(
id INT NOT NULL,
start INT NOT NULL
PARTITION BY RANGE (start)
     PARTITION old_Data VALUES LESS THAN (1000000) TABLESPACE old,
     PARTITION new_Data VALUES LESS THAN (MAXVALUE) TABLESPACE new
I would like to create monthly interval partition in old_data partition. Is this possible? Don't see any syntax for supporting this scenario.

Welcome to the forum!
Whenever you post provide your 4 digit Oracle version.
>
I have a table which has range partition on a number column.
CREATE TABLE TEST(
id INT NOT NULL,
start INT NOT NULL
PARTITION BY RANGE (start)
PARTITION old_Data VALUES LESS THAN (1000000) TABLESPACE old,
PARTITION new_Data VALUES LESS THAN (MAXVALUE) TABLESPACE new
I would like to create monthly interval partition in old_data partition. Is this possible? Don't see any syntax for supporting this scenario.
>
No - it is not possible. There isn't any syntax for supporting that because integers do have have 'months' so how would Oracle partition an integer 'monthly'?
If those integers are supposed to represent Unix 'epoch' date values then in 11g you can create a virtual column of DATE datatype and partition on that.
But you will need to either recreate the table or, if you needed to do it online, use the DBMS_REDEFINITION package. Either approach results in a new table with the correct partitioning that includes the existing data.
Here is a similar table to yours with a VIRTUAL column that is partitioned by day:
drop table some_table_int
create table some_table_int (
    column_1 nvarchar2(50),
    start_t number(38,0),
    column_n number,
    start_date DATE GENERATED ALWAYS AS (
    to_timestamp(to_char( to_date('01011970','ddmmyyyy') + 1/24/60/60 * start_t, 'DD-MON-YYYY HH24:MI:SS'),'DD-MON-YYYY HH24:MI:SS')
) VIRTUAL
partition by range (start_date) interval (NUMTODSINTERVAL(7,'day'))
(partition p_19700105 values less than (to_date('19700105', 'yyyymmdd'))
/That VIRTUAL column is an ordinary DATE column and your ranges will be dates rather than numbers that have no meaning for anyone.
The VIRTUAL column is only a data dictionary entry so it won't affect any actual data.

Existing Range partition to Interval Partition

I have an Range and list partition tables on Oracle 11g with some records and have to move the
range and List partition tables to interval partitions. I tried for the range partition
table with following query,
SQL> alter table F_PTP_PAYMENTS set interval (numtoyminterval(3,'MONTH'));
alter table F_PTP_PAYMENTS set interval (numtoyminterval(3,'MONTH'))
ERROR at line 1:
ORA-14759: SET INTERVAL is not legal on this table.
it doesnt worked out.
Can you please help me to create the interval partitions.

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*

Alter range partition table to Interval partitioning table.

Hi DBA's,
I have a very big range partitioned table.
Recently we have upgraded our database to 11gR2 which has a feautre called interval partitioning.
Now i want to modify that existing range partitioned table to Interval Partitioning.
can we alter the range partitioned table to interval partitioning table?
I googled for the syntax but i didn't find it, can any one help[ me out on this?
Thanks.

If you ignore the "alter session set NLS_CALENDAR=PERSIAN;" during create/alter, everything else seems to work.
When you set the "alter session..." during inserts, the rows gets inserted into the correct partitions.
Only thing is when you look at HIGH_VALUE, you need to convert from the default GREGORIAN to PERSIAN.

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*

Range Partitioning a table. Max value to be defined

Hi,
I am using a range partitioned table, range partitioned on date, and have defined max value as 6 months after the Creation Date.
I have a proc which creates the partitions I want in advance by splitting up the max partition.
- Now what do I do when max partition is reached after 6 months?
- If I define max partition one year or two year after the current date instead of the currently defined 6 months after creation date. What are the negatives attached with it?
I can't use Interval Partition and have to use Range only.
Kindly suggest.
Thanks..

>
I am using a range partitioned table, range partitioned on date, and have defined max value as 6 months after the Creation Date.
I have a proc which creates the partitions I want in advance by splitting up the max partition.
- Now what do I do when max partition is reached after 6 months?
- If I define max partition one year or two year after the current date instead of the currently defined 6 months after creation date. What are the negatives attached with it?
>
Any data with a partition key that does NOT match any partition will cause your INSERT query to fail.
Any partition that has no data to match it will simply remain empty.
A common partitioning scheme is to define one partition for all old data, one partition with a high max value and then split the max value partition to get the partitions you want in the middle.
Let's say you want monthly partitions but don't have that much data from before the current year, 2012.
1. Create one partition for dates < 1/1/2012
2. One partition each for the 12 months of 2012
3. One max value partition to be 1/1/4000
You would just split the max value partition to create each month of 2013. The split could be done ahead of time or a month at a time as you choose.
The only negative is that any data inserted by mistake that has a super-high date will go into the max value partition. But that is going to happen anyway. If you accidentally enter a date of 3/23/3882 it won't be rejected.
But it is easy to query periodically to see if you have any 'bad' data like that. And the alternative is that an INSERT would fail because of the one bad record and all of your good data would be rejected anyway so it's not really much of a negative.
Remember - for best management performance each partition should have its own tablespace and the indexes should all be local if possible.

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

Unique key on range-partitioned table

Hi,
We are using a composite range-hash interval partitioned table
Uses index - trying to make this have same tablespace as the partitions i.e. local but not liking it
alter table RETAILER_TRANSACTION_COMP_POR
add constraint RETAILER_TRANSACTION_COMP_PK primary key (DWH_NUM)
using index
LOCAL
ora-14039: partitioning columns must form a subset of key columns of a unique index
Without local then fine but doesn't have same tablespace as the partitions and don't want to make this part of partition key.
Tbale range partitioned - this is just a UK to prevent duplicates

[oracle@localhost ~]$ oerr ora 14039
14039, 00000, "partitioning columns must form a subset of key columns of a UNIQUE index"
// *Cause: User attempted to create a UNIQUE partitioned index whose
//          partitioning columns do not form a subset of its key columns
//          which is illegal
// *Action: If the user, indeed, desired to create an index whose
//          partitioning columns do not form a subset of its key columns,
//          it must be created as non-UNIQUE; otherwise, correct the
//          list of key and/or partitioning columns to ensure that the index'
//          partitioning columns form a subset of its key columns

Range Partitioning of Table

Hi all,
I need to do range partitioning on a table using current system timestamp. sth like
CREATE TABLE SAMPLE(ID NUMBER, SAMPLE_DATE TIMESTAMP)PARTITION BY RANGE(SAMPLE_DATE)(PARTITION P1 VALUES LESS THAN (LOCALTIMESTAMP));
Is there any way I can assign a dynamic date using variable other than string literal after VALUES LESS THAN clause? I tried achieving this with stored procedure but always throws error for this filed.
CREATE OR REPLACE PROCEDURE partition_test
IS
x TIMESTAMP;
comm long;
BEGIN
SELECT LOCALTIMESTAMP into x from dual;
comm := 'CREATE TABLE SAMPLE(ID NUMBER, SAMPLE_DATE TIMESTAMP)PARTITION BY RANGE(SAMPLE_DATE)(PARTITION P1 VALUES LESS THAN (x))';
execute immediate comm;
END partition_test;
error I'm getting is
ORA-14019: partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE
Any clue? Would really appreciate your help.
Noman

Can you please try with proper quotes like this...
comm := 'CREATE TABLE SAMPLE(ID NUMBER, SAMPLE_DATE TIMESTAMP)PARTITION BY RANGE(SAMPLE_DATE)(PARTITION P1 VALUES LESS THAN (' || x || '))';
If that didn't work out, try printing the value of comm before execute immediate and if required you can add proper number of quotes.

TIMESTAMP(6) Partitioned Key - Range partitioned table ddl needed

What is DDL syntax for TIMESTAMP(6) Partitioned Key, Range partitioned table
Edited by: oracletune on Jan 11, 2013 10:26 AM

>
What is DDL syntax for TIMESTAMP(6) Partitioned Key, Range partitioned table
>
Not sure what you are asking. Are you asking how to create a partitioned table using a TIMESTAMP(6) column for the key?
CREATE TABLE TEST1
    USERID                 NUMBER,
    ENTRYCREATEDDATE     TIMESTAMP(6)
PARTITION BY RANGE (ENTRYCREATEDDATE) INTERVAL(NUMTOYMINTERVAL(1, 'MONTH'))
    PARTITION P0 VALUES LESS THAN (TO_DATE('1-1-2013', 'DD-MM-YYYY'))
)See my reply Posted: Jan 10, 2013 9:56 PM if you need to do it on a TIMESTAMP with TIME ZONE column. You need to add a virtual column.
Creating range paritions automatically

Will JDeveloper support INTERVAL and REFERENCES partitioning methods soon?

JDeveloper is a fantastic tool, and I'm very impressed with its data modeling capabilities as they are quite robust. However, currently its support for Table Partitioning is limited to the feature level of Oracle 10g, as it does not support 11g INTERVAL or REFERENCES partitioning methods, nor the Composite List partitioning methods List-Range, List-Hash, and List-List.
Any idea when JDeveloper will support these Partitioning enhancements available in Oracle Database 11g? If it's in the works, I'd be happy to help beta test it!
Best regards,
Terry

Hi Terry
I love it that you are working with the data modeling and would love to hear how you are using it. Please email me direct with more info
We are working to get composite partitions (11g) into a future release but I don't have any timeframe for you at the moment.
rgds
Susan Duncan
Product Manager
susan.duncan@oracle

Composite range - range partitioning gives ORA-14202

i am trying to do e composite range - range partitioning, but the table is not created. i get an error, which i cannot look up at ora-codes, it says : value is to high for subpartition, which confuses me...
CREATE TABLE "NJ_VE_AERIAL_RDT"
(     "RASTERID" NUMBER NOT NULL ENABLE,
"BANDBLOCKNUMBER" NUMBER NOT NULL ENABLE,
     "PYRAMIDLEVEL" NUMBER NOT NULL ENABLE,
     "ROWBLOCKNUMBER" NUMBER NOT NULL ENABLE,
     "COLUMNBLOCKNUMBER" NUMBER NOT NULL ENABLE,
     "FILENAME" VARCHAR2(100 CHAR) NOT NULL ENABLE,
     "FILESIZE" NUMBER(12,0) NOT NULL ENABLE,
     "NORTH" NUMBER(19,15) NOT NULL ENABLE,
     "SOUTH" NUMBER(19,15) NOT NULL ENABLE,
     "EAST" NUMBER(19,15) NOT NULL ENABLE,
     "WEST" NUMBER(19,15) NOT NULL ENABLE,
     "BLOCKMBR" "MDSYS"."SDO_GEOMETRY" ,
     "RASTERBLOCK" BLOB,
     "INFO_CREATOR" VARCHAR2(100 BYTE) DEFAULT 'novalue' NOT NULL ENABLE,
     "INFO_CREATED" TIMESTAMP (6) WITH LOCAL TIME ZONE DEFAULT CURRENT_TIMESTAMP NOT NULL ENABLE,
     "INFO_LASTMODIFIER" VARCHAR2(100 CHAR) DEFAULT 'novalue' NOT NULL ENABLE,
     "INFO_LASTMODIEFIER" TIMESTAMP (6) WITH LOCAL TIME ZONE DEFAULT CURRENT_TIMESTAMP NOT NULL ENABLE,
     CONSTRAINT "NJ_VE_RDT_PK" PRIMARY KEY
("RASTERID"
,"BANDBLOCKNUMBER"
,"PYRAMIDLEVEL"
,"ROWBLOCKNUMBER"
,"COLUMNBLOCKNUMBER"))
PARTITION BY RANGE (WEST) INTERVAL (1)
SUBPARTION BY RANGE (NORTH)
SUBPARTITION TMEPLATE (
SUBPARTITION s0 VALUES LESS THAN (15)
,SUBPARTITION s0 VALUES LESS THAN (5)
(PARTITION p0 VALUES LESS THAN (0));
What is my problem ? My current solution is fully dropping subpartitioning. but thats a cheesy workaround...
ingo
Message was edited by:
Ingo Jannick

achso ?!
this works, but even switching the subpartition definitions results in the mentioned error. adding another sub does the same.
my guess is that it is a range by interval issue. i have to figure that out...
Working:
CREATE TABLE "NJ_VEL_RDT"
(     "RASTERID" NUMBER NOT NULL ENABLE,
"BANDBLOCKNUMBER" NUMBER NOT NULL ENABLE,
     "PYRAMIDLEVEL" NUMBER NOT NULL ENABLE,
     "ROWBLOCKNUMBER" NUMBER NOT NULL ENABLE,
     "COLUMNBLOCKNUMBER" NUMBER NOT NULL ENABLE,
     "FILENAME" VARCHAR2(100 CHAR) NOT NULL ENABLE,
     "FILESIZE" NUMBER(12,0) NOT NULL ENABLE,
     "NORTH" NUMBER(19,15) NOT NULL ENABLE,
     "SOUTH" NUMBER(19,15) NOT NULL ENABLE,
     "EAST" NUMBER(19,15) NOT NULL ENABLE,
     "WEST" NUMBER(19,15) NOT NULL ENABLE,
     "BLOCKMBR" "MDSYS"."SDO_GEOMETRY" ,
     "RASTERBLOCK" BLOB,
     "INFO_CREATOR" VARCHAR2(100 BYTE) DEFAULT 'novalue' NOT NULL ENABLE,
     "INFO_CREATED" TIMESTAMP (6) WITH LOCAL TIME ZONE DEFAULT CURRENT_TIMESTAMP NOT NULL ENABLE,
     "INFO_LASTMODIFIER" VARCHAR2(100 CHAR) DEFAULT 'novalue' NOT NULL ENABLE,
     "INFO_LASTMODIEFIER" TIMESTAMP (6) WITH LOCAL TIME ZONE DEFAULT CURRENT_TIMESTAMP NOT NULL ENABLE,
     CONSTRAINT "NJ_VE_PK" PRIMARY KEY
( "RASTERID",
"BANDBLOCKNUMBER",
"PYRAMIDLEVEL",
"ROWBLOCKNUMBER",
"COLUMNBLOCKNUMBER"))
PARTITION BY RANGE(WEST) INTERVAL (5)
SUBPARTITION BY RANGE(NORTH)
SUBPARTITION TEMPLATE
SUBPARTITION s1 VALUES LESS THAN (65)
,SUBPARTITION s0 VALUES LESS THAN (MAXVALUE)
(PARTITION p0 VALUES LESS THAN (15))
;

INTERVAL in Range Partition?

Similar Messages

Maybe you are looking for