Interval partitioning indexes

Hi,
I am unable to get the indexes interval partitioned, it always throws "ORA-00906: missing left parenthesis"
Example:
-- interval partitioning the table works fine as below
create table t1 (partitionID number, name varchar2(200))
partition by range (partitionID) interval (1)
(partition p1 values less than (2))
-- Now, lets try building a global interval partitioned index on this
-- Though it is possible to simply tag it as local, I would like to create it as global for other reasons
create unique index t1_u1 on t1(partitionID) global
partition by range (partitionID) interval (1)
(partition p1 values less than (2))
Index creation as above fails for me with "ORA-00906: missing left parenthesis" and I can't figure out why it is doing so.
I tried to see if I can range partition the index and add interval later, but that fails too
SQL> create unique index t1_u1 on t1(partitionID) global
2 partition by range (partitionID)
3 (partition p1 values less than (MAXVALUE));
Index created.
SQL> alter index t1_u1 set interval (1);
alter index t1_u1 set interval (1)
ERROR at line 1:
ORA-02243: invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
Isn't interval partitioning not supported for indexes ?

Isn't interval partitioning not supported for indexes ?When all else fails, Read The Fine Manual
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_1008.htm#i2050158

Similar Messages

How to index a column in an interval partitioned table

Hi -
I see that domain indexes are not allowed on a table which has interval partitioning on it.
Given this limitation, is there any way to improve performance on wildcard searches (like '%condition%';) on a VARCHAR(2) column in a table which has interval partitioning?
Or are we SOL if we want to do this?
Thanks for any advice or experience in this area.
LJ

There's no real good way to make non-domain-indexed text queries fast. If there was, the Text forum wouldn't be the lively place it is today!
But SOL? No, I wouldn't call you SOL... There are always ways to do stuff, just depends on how important it is to you, how much space/time/maintenance you're willing to do to make things work.
For example, create a non-interval-partitioned materialized view of your target table/column and use a domain index on that.
What constraints or options do you have (or think you have) in order to make this work?

Creating DOMAIN INDEX on INTERVAL PARTITIONING

Hi !
I hava a problem, and I hope someone can help me!
Two questions are asked below:
1. Main question: HOW CAN I SOLVE THIS PROBLEM, ARE THERE OTHER WAYS DOING THE SAME JOB (MAYBE FASTER) ?
2. Additionally: Is there a way to accelerate the deletion process
Step 1: Creating the table* For Information how I create the table:
CREATE TABLE LOC_EXAMPLE
COLUMN1 NUMBER
COLUMN2 NUMBER
COLUMN3 NUMBER
COLUMN4 NUMBER
START_TIME TIMESTAMP
GEOLOC MDSYS.SDO_GEOMETRY,
TABLESPACE DB_DATA
PCTUSED 0
PCTFREE 10
INITRANS 1
MAXTRANS 255
STORAGE (
INITIAL 64K
MINEXTENTS 1
MAXEXTENTS 2147483645
PCTINCREASE 0
BUFFER_POOL DEFAULT
NOLOGGING
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING
PARTITION BY RANGE (START_TIME)
INTERVAL (NUMTODSINTERVAL(1,'DAY'))
PARTITION PART_LOC_EXAMPLE VALUES LESS THAN (TO_DATE('01-01-2008','dd-MM-yyyy'))
ALTER TABLE LOC_EXAMPLE
ADD CONSTRAINT PK_LOC_EXAMPLE PRIMARY KEY (COLUMN2,COLUMN4)
DELETE FROM USER_SDO_GEOM_METADATA VALUE WHERE TABLE_NAME = 'LOC_EXAMPLE'
INSERT INTO USER_SDO_GEOM_METADATA VALUES ('LOC_EXAMPLE','GEOLOC', MDSYS.SDO_DIM_ARRAY( MDSYS.SDO_DIM_ELEMENT('X',-180,180,0.001111949), MDSYS.SDO_DIM_ELEMENT('Y',-90,90,0.001111949) ), 8307)
STEP 2: I TRY TO CREATE SPATIAL INDEX (ITS A DOMAIN INDEX IF I'M NOT WRONG) ON PARTITIONED TABLE*
(PARTITIONED TABLE is an extension of range partitioning)
CREATE INDEX LOC_EXAMPLE_idx ON LOC_EXAMPLE'(GEOLOC)
INDEXTYPE IS MDSYS.SPATIAL_INDEX LOCAL;
THE SECOND STEP IS NOT POSSIBLE AS THE ORACLE DOCUMENTATION SAYS:
When using interval partitioning, consider the following restrictions:
-You can only specify one partitioning key column, and it must be of NUMBER or DATE type.
-Interval partitioning is not supported for index-organized tables.
-You cannot create a domain index on an interval-partitioned table.
1) I THINK IT IS IMPOSSIBLE FOR ME TO PASS ON INTERVAL PARTITIONING (AMOUNT OF DATA IS REALY BIG).
This partitioning is also used to delete datas from database once a mounth (scheduled on the basis of the partitions).
Is there a way to accelerate the deletion process?
2) I NEED A SPATIAL INDEX! NO WAY TO PASS ON IT!
HOW CAN I SOLVE THIS PROBLEM, ARE THERE OTHER WAYS DOING THE SAME JOB (MAYBE FASTER) ?
Why is it not possible to create a domain index on interval partitioning, any reason?
Will this be possible anytime?
I would be grateful to read any advise ...!
Thanking you in anticipation,
Ali

There is a forum here at OTN for spatial. Please delete the contents of this post and ask your question there. Thanks.

Creating DOMAIN INDEX (SPATIAL) on INTERVAL PARTITIONING

Hi !
I hava a problem, and I hope someone can help me!
Two questions are asked below:
1. Main question: HOW CAN I SOLVE THIS PROBLEM, ARE THERE OTHER WAYS DOING THE SAME JOB (MAYBE FASTER) ?
2. Additionally: Is there a way to accelerate the deletion process
Step 1: Creating the table For Information how I create the table:
CREATE TABLE LOC_EXAMPLE
COLUMN1 NUMBER
COLUMN2 NUMBER
COLUMN3 NUMBER
COLUMN4 NUMBER
START_TIME TIMESTAMP
GEOLOC MDSYS.SDO_GEOMETRY,
TABLESPACE DB_DATA
PCTUSED 0
PCTFREE 10
INITRANS 1
MAXTRANS 255
STORAGE (
INITIAL 64K
MINEXTENTS 1
MAXEXTENTS 2147483645
PCTINCREASE 0
BUFFER_POOL DEFAULT
NOLOGGING
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING
PARTITION BY RANGE (START_TIME)
INTERVAL (NUMTODSINTERVAL(1,'DAY'))
PARTITION PART_LOC_EXAMPLE VALUES LESS THAN (TO_DATE('01-01-2008','dd-MM-yyyy'))
ALTER TABLE LOC_EXAMPLE
ADD CONSTRAINT PK_LOC_EXAMPLE PRIMARY KEY (COLUMN2,COLUMN4)
DELETE FROM USER_SDO_GEOM_METADATA VALUE WHERE TABLE_NAME = 'LOC_EXAMPLE'
INSERT INTO USER_SDO_GEOM_METADATA VALUES ('LOC_EXAMPLE','GEOLOC', MDSYS.SDO_DIM_ARRAY( MDSYS.SDO_DIM_ELEMENT('X',-180,180,0.001111949), MDSYS.SDO_DIM_ELEMENT('Y',-90,90,0.001111949) ), 8307)
STEP 2: I TRY TO CREATE SPATIAL INDEX (ITS A DOMAIN INDEX IF I'M NOT WRONG) ON PARTITIONED TABLE
(PARTITIONED TABLE is an extension of range partitioning)
CREATE INDEX LOC_EXAMPLE_idx ON LOC_EXAMPLE'(GEOLOC)
INDEXTYPE IS MDSYS.SPATIAL_INDEX LOCAL;
THE SECOND STEP IS NOT POSSIBLE AS THE ORACLE DOCUMENTATION SAYS:
When using interval partitioning, consider the following restrictions:
-You can only specify one partitioning key column, and it must be of NUMBER or DATE type.
-Interval partitioning is not supported for index-organized tables.
-You cannot create a domain index on an interval-partitioned table.
1) I THINK IT IS IMPOSSIBLE FOR ME TO PASS ON INTERVAL PARTITIONING (AMOUNT OF DATA IS REALY BIG).
This partitioning is also used to delete datas from database once a mounth (scheduled on the basis of the partitions).
Is there a way to accelerate the deletion process?
2) I NEED A SPATIAL INDEX! NO WAY TO PASS ON IT!
HOW CAN I SOLVE THIS PROBLEM, ARE THERE OTHER WAYS DOING THE SAME JOB (MAYBE FASTER) ?
Why is it not possible to create a domain index on interval partitioning, any reason?
Will this be possible anytime?
I would be grateful to read any advise ...!
Thanking you in anticipation,
Ali

Is it possible to just use a normal range-partitioned table?
CREATE TABLE LOC_EXAMPLE
START_TIME TIMESTAMP
GEOLOC MDSYS.SDO_GEOMETRY,
PARTITION BY RANGE (START_TIME)
PARTITION P1 VALUES LESS THAN (TO_DATE('01-01-2008','dd-MM-yyyy'))
alter table loc_example add partition p2 VALUES LESS THAN (TO_DATE('02-01-2008','dd-MM-yyyy'));
alter table loc_example drop partition p1;
I understand it is not as perfect as interval partitioning, since
you have to drop an old partition/add a new one either manually
or by some script. But you should be able to create a spatial domain index
on it.

11g interval partitioning and global index maintenance

hi gurus,
in 11g interval partitioning system can automatically manage the creation of new partitions based on data.
in this case do we need to manage global indexes?
in earlier versions, we have to update global indexes whenever there is a partition maintenance operation.
please suggest.
thanks,
charles

user570138 wrote:
in earlier versions, we have to update global indexes whenever there is a partition maintenance operation.In 10gR2 you don't need to update/rebuild a global index after adding a partition to the base table.
So it should be the same when using interval partitioning.
Regards
Maurice

Primary Key Causing Problem in Interval Partition Exchange

DB : 11.2.0.2
OS : AIX 6.1
I am getting the problem while exchanging data with interval partitioned table. I have a interval partitioned table and a normal staging table having data to be uploaded.
Following are the steps i am doing.
SQL> CREATE TABLE DEMO_INTERVAL_DATA_LOAD (
                ROLL_NUM        NUMBER(10),
                CLASS_ID        NUMBER(2),
                ADMISSION_DATE DATE,
                TOTAL_FEE       NUMBER(4),
                COURSE_ID       NUMBER(4))
                PARTITION BY RANGE (ADMISSION_DATE)
                INTERVAL (NUMTOYMINTERVAL(3,'MONTH'))
                ( PARTITION QUAT_1_2012 VALUES LESS THAN (TO_DATE('01-APR-2012','DD-MON-YYYY')),
                 PARTITION QUAT_2_2012 VALUES LESS THAN (TO_DATE('01-JUL-2012','DD-MON-YYYY')),
                 PARTITION QUAT_3_2012 VALUES LESS THAN (TO_DATE('01-OCT-2012','DD-MON-YYYY')),
                 PARTITION QUAT_4_2012 VALUES LESS THAN (TO_DATE('01-JAN-2013','DD-MON-YYYY')));
Table created.
SQL> ALTER TABLE DEMO_INTERVAL_DATA_LOAD ADD CONSTRAINT IDX_DEMO_ROLL PRIMARY KEY (ROLL_NUM);
Table altered.
SQL> SELECT TABLE_OWNER,
           TABLE_NAME,
           COMPOSITE,
           PARTITION_NAME,
       PARTITION_POSITION,
          TABLESPACE_NAME,
       LAST_ANALYZED
FROM DBA_TAB_PARTITIONS
    WHERE TABLE_OWNER='SCOTT'
   AND TABLE_NAME='DEMO_INTERVAL_DATA_LOAD'
   ORDER BY PARTITION_POSITION;
TABLE_OWNER                    TABLE_NAME                     COM PARTITION_NAME                 PARTITION_POSITION TABLESPACE_NAME                LAST_ANAL
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO QUAT_1_2012                                     1 USERS
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO QUAT_2_2012                                     2 USERS
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO QUAT_3_2012                                     3 USERS
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO QUAT_4_2012                                     4 USERS
SQL> INSERT INTO DEMO_INTERVAL_DATA_LOAD VALUES (10,1,'12-MAR-2012',1000,90);
1 row created.
SQL> INSERT INTO DEMO_INTERVAL_DATA_LOAD VALUES (11,5,'01-JUN-2012',5000,80);
1 row created.
SQL> INSERT INTO DEMO_INTERVAL_DATA_LOAD VALUES (12,9,'12-SEP-2012',4000,20);
1 row created.
SQL> INSERT INTO DEMO_INTERVAL_DATA_LOAD VALUES (13,7,'29-DEC-2012',7000,10);
1 row created.
SQL> INSERT INTO DEMO_INTERVAL_DATA_LOAD VALUES (14,8,'21-JAN-2013',2000,50); ---- This row will create a new interval partition in table.
1 row created.
SQL> commit;
SQL> SELECT TABLE_OWNER,
        TABLE_NAME,
        COMPOSITE,
        PARTITION_NAME,
        PARTITION_POSITION,
        TABLESPACE_NAME,
        LAST_ANALYZED
FROM DBA_TAB_PARTITIONS
     WHERE TABLE_OWNER='SCOTT'
   AND TABLE_NAME='DEMO_INTERVAL_DATA_LOAD'
   ORDER BY PARTITION_POSITION;
TABLE_OWNER                    TABLE_NAME                     COM PARTITION_NAME                 PARTITION_POSITION TABLESPACE_NAME                LAST_ANAL
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO QUAT_1_2012                                     1 USERS
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO QUAT_2_2012                                     2 USERS
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO QUAT_3_2012                                     3 USERS
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO QUAT_4_2012                                     4 USERS
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO SYS_P98                                         5 USERS
SYS_P98 partition is added to table automatically.
SQL> CREATE TABLE DEMO_INTERVAL_DATA_LOAD_Y (
                ROLL_NUM        NUMBER(10),
                CLASS_ID        NUMBER(2),
                ADMISSION_DATE DATE,
                TOTAL_FEE       NUMBER(4),
                COURSE_ID       NUMBER(4));
Table created.
SQL> INSERT INTO DEMO_INTERVAL_DATA_LOAD_Y VALUES (30,3,'21-MAY-2013',2000,12);
1 row created.
SQL> commit;
Commit complete.
Since, i need a partition in DEMO_INTERVAL_DATA_LOAD table, which can be used in partition exchange, so i create a new partition as below:
SQL> LOCK TABLE DEMO_INTERVAL_DATA_LOAD PARTITION FOR (TO_DATE('01-APR-2013','DD-MON-YYYY')) IN SHARE MODE;
Table(s) Locked.
SQL> SELECT TABLE_OWNER,
           TABLE_NAME,
           COMPOSITE,
           PARTITION_NAME,
           PARTITION_POSITION,
           TABLESPACE_NAME,
           LAST_ANALYZED
FROM DBA_TAB_PARTITIONS
    WHERE TABLE_OWNER='SCOTT'
   AND TABLE_NAME='DEMO_INTERVAL_DATA_LOAD'
   ORDER BY PARTITION_POSITION;
TABLE_OWNER                    TABLE_NAME                     COM PARTITION_NAME                 PARTITION_POSITION TABLESPACE_NAME                LAST_ANAL
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO QUAT_1_2012                                     1 USERS
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO QUAT_2_2012                                     2 USERS
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO QUAT_3_2012                                     3 USERS
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO QUAT_4_2012                                     4 USERS
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO SYS_P98                                         5 USERS
SCOTT                          DEMO_INTERVAL_DATA_LOAD        NO SYS_P102                                        6 USERS
SQL> ALTER TABLE DEMO_INTERVAL_DATA_LOAD
EXCHANGE PARTITION SYS_P102
WITH TABLE DEMO_INTERVAL_DATA_LOAD_Y
INCLUDING INDEXES
WITH VALIDATION;
ALTER TABLE DEMO_INTERVAL_DATA_LOAD
ERROR at line 1:
ORA-14097: column type or size mismatch in ALTER TABLE EXCHANGE PARTITIONNow, if i disable/drop the primary key constraint, it works without any problem.
SQL> alter table DEMO_INTERVAL_DATA_LOAD disable constraint IDX_DEMO_ROLL;
Table altered.
SQL> alter table DEMO_INTERVAL_DATA_LOAD drop constraint IDX_DEMO_ROLL;
Table altered.
SQL> ALTER TABLE DEMO_INTERVAL_DATA_LOAD
EXCHANGE PARTITION SYS_P102
WITH TABLE DEMO_INTERVAL_DATA_LOAD_Y
INCLUDING INDEXES
WITH VALIDATION;
Table altered.
SQL> select * from DEMO_INTERVAL_DATA_LOAD partition (SYS_P102);
ROLL_NUM   CLASS_ID ADMISSION TOTAL_FEE COURSE_ID
        30          3 21-MAY-13       2000         12
SQL> select * from DEMO_INTERVAL_DATA_LOAD_Y;
no rows selectedPlease suggest.

First, thanks for posting the code that lets us reproduce your test. That is essential for issues like this.
Because the primary key is global you will not be able to use
INCLUDING INDEXES
WITH VALIDATION;And you will need to add the primary key to the temp table
ALTER TABLE DEMO_INTERVAL_DATA_LOAD_Y ADD CONSTRAINT IDX_DEMO_ROLL_Y PRIMARY KEY (ROLL_NUM);The the exchange will work. You will need to rebuild the primary key after the exchange.

Create table interval partition on a column timestamp with local time zone

Hi
Does anyone have an example for 11g on how to create a table with interval partitioning on a column defined as timestamp with local time zone. I know it's possible. the following does not work.
CREATE TABLE KOMODO_EXPIRED_RESULTS
TEST_EVENT_KEY NUMBER NOT NULL,
HPS_DEVICE_KEY NUMBER NOT NULL,
RCS_DEVICE_KEY NUMBER,
EVENT_START_TIMESTAMP TIMESTAMP(6) with local time zone NOT NULL,
BOOTROMVERSION NUMBER,
CHANNELNUMBER NUMBER,
CLIENTVERSION VARCHAR2(4000 BYTE),
ETHERNET_CRC_ERROR_COUNT NUMBER,
ETHERNET_DROPPED_PACKETS NUMBER,
ETHERNET_THROUGHPUT NUMBER,
ETHERNET_TRAFFIC_IN NUMBER,
ETHERNET_TRAFFIC_OUT NUMBER,
IPADDRESS VARCHAR2(4000 BYTE),
KOMODO_ID VARCHAR2(4000 BYTE),
LASTREBOOTTIME VARCHAR2(4000 BYTE),
OSVERSION VARCHAR2(4000 BYTE),
RECEIVER_AUDIOACCESSCONTROLER NUMBER,
RECEIVER_AUDIOBUFFEROVERFLOWS NUMBER,
RECEIVER_AUDIOBUFFERUNDERRUNS NUMBER,
RECEIVER_AUDIOCODEC VARCHAR2(4000 BYTE),
RECEIVER_AUDIODATADROPPED NUMBER,
RECEIVER_AUDIODATATHROUGHPUT NUMBER,
RECEIVER_AUDIODECODERERRORS NUMBER,
RECEIVER_AUDIODESCBUFFERUNDER NUMBER,
RECEIVER_AUDIODESCCRYPTOERROR NUMBER,
RECEIVER_AUDIODESCDATADROPPED NUMBER,
RECEIVER_AUDIODESCDATATHROUGH NUMBER,
RECEIVER_AUDIODESCDECODERERRO NUMBER,
RECEIVER_AUDIODESCDRMERRORS NUMBER,
RECEIVER_AUDIODESCPTSDELTA NUMBER,
RECEIVER_AUDIODESCPTSDELTAHAL NUMBER,
RECEIVER_AUDIODESCSAMPLESDROP NUMBER,
RECEIVER_AUDIODSPCRASHES VARCHAR2(4000 BYTE),
RECEIVER_AUDIOPTSDELTAHAL NUMBER,
RECEIVER_AUDIOSAMPLESDECODED NUMBER,
RECEIVER_AUDIOSAMPLESDROPPED NUMBER,
RECEIVER_AUDIOUNDERRUN NUMBER,
RECEIVER_BITRATE NUMBER,
RECEIVER_BUFFEROVERRUN NUMBER,
RECEIVER_BYTESCCRECEIVED NUMBER,
RECEIVER_BYTESRECEIVED NUMBER,
RECEIVER_CHANNEL NUMBER,
RECEIVER_DECODERSTALL NUMBER,
RECEIVER_DISCONTINUITIES NUMBER,
RECEIVER_DISCONTINUITIESPACKE NUMBER,
RECEIVER_DRIFT NUMBER,
RECEIVER_DROPPEDPACKETSUNTILR NUMBER,
RECEIVER_ECMLOOKUPERROR NUMBER,
RECEIVER_ECMPARSEERRORS NUMBER,
RECEIVER_PMTCHANGED NUMBER,
RECEIVER_REBUFFER NUMBER,
RECEIVER_SELECTCOMPONENTAUDIO NUMBER,
RECEIVER_TIMELINEDISCONTINUIT NUMBER,
RECEIVER_VIDEOACCESSCONTROLER NUMBER,
RECEIVER_VIDEOACCESSCONTROLUN NUMBER,
RECEIVER_VIDEOBUFFEROVERFLOWS NUMBER,
RECEIVER_VIDEOBUFFERUNDERRUNS NUMBER,
RECEIVER_VIDEOCODEC VARCHAR2(4000 BYTE),
RECEIVER_VIDEOCRYPTOERROR NUMBER,
RECEIVER_VIDEODATADROPPED NUMBER,
RECEIVER_VIDEODATATHROUGHPUT NUMBER,
RECEIVER_VIDEODECODERERRORS NUMBER,
RECEIVER_VIDEODRMERRORS NUMBER,
RECEIVER_VIDEODSPCRASHES VARCHAR2(4000 BYTE),
RECEIVER_VIDEOFIFORD NUMBER,
RECEIVER_VIDEOFIFOSIZE NUMBER,
RECEIVER_VIDEOFRAMESDECODED NUMBER,
RECEIVER_VIDEOFRAMESDROPPED NUMBER,
RECEIVER_VIDEOPTSDELTA NUMBER,
RECEIVER_VIDEOPTSDELTAHAL NUMBER,
RECEIVER_VIDEOUNDERRUN NUMBER,
SUBNETMASK VARCHAR2(4000 BYTE),
TUNER_BITRATE NUMBER,
TUNER_BUFFERFAILURE NUMBER,
TUNER_CCPACKETSRECEIVED NUMBER,
TUNER_CHANNEL NUMBER,
TUNER_DATATIMEOUTS NUMBER,
TUNER_DELIVERYMODE VARCHAR2(4000 BYTE),
TUNER_DROPPAST NUMBER,
TUNER_FILL NUMBER,
TUNER_HOLE NUMBER,
TUNER_HOLEDURINGBURST NUMBER,
TUNER_HOLEDURINGBURSTPACKETS NUMBER,
TUNER_HOLETOOLARGEPACKETS NUMBER,
TUNER_MAXIMUMHOLESIZE NUMBER,
TUNER_MULTICASTADDRESS VARCHAR2(4000 BYTE),
TUNER_MULTICASTJOINDELAY NUMBER,
TUNER_OUTOFORDER NUMBER,
TUNER_OVERFLOWRESET NUMBER,
TUNER_OVERFLOWRESETTIMES NUMBER,
TUNER_PACKETSEXPIRED NUMBER,
TUNER_PACKETSPROCESSED NUMBER,
TUNER_PACKETSRECEIVED NUMBER,
TUNER_PACKETSWITHOUTSESSION NUMBER,
TUNER_PARSEERRORS NUMBER,
TUNER_SRCUNAVAILABLERECEIVED NUMBER,
TUNER_TOTALHOLEPACKETS NUMBER,
TUNER_TOTALPACKETSEXPIRED NUMBER,
TUNER_TOTALPACKETSRECEIVED NUMBER,
TUNER_UNICASTADDRESS VARCHAR2(4000 BYTE),
RECEIVER_TUNEDFOR NUMBER,
MACADDRESS VARCHAR2(4000 BYTE),
RECEIVER_TOTALAVUNDERRUNS NUMBER,
RECEIVER_TOTALDISCONTINUITIES NUMBER,
SERVICEID VARCHAR2(4000 BYTE),
DRIVEPRESENT VARCHAR2(4000 BYTE),
STB_STATE VARCHAR2(32 BYTE),
PREV_EXPIRED NUMBER,
PREV_HOLES NUMBER,
PREV_RECEIVED NUMBER,
PREV_TIMESTAMP TIMESTAMP(6),
PREV_REBOOT VARCHAR2(4000 BYTE),
TOTALPACKETSEXPIRED_RATE NUMBER,
TOTALHOLEPACKETS_RATE NUMBER,
TOTALPACKETSRECEIVED_RATE NUMBER,
CONSTRAINT KOMODO_EXPIRED_RESULTS_PK
PRIMARY KEY
(HPS_DEVICE_KEY, EVENT_START_TIMESTAMP)
USING INDEX
TABLESPACE HPS_SUMMARY_INDEX
TABLESPACE HPS_SUMMARY_DATA
PARTITION BY RANGE (EVENT_START_TIMESTAMP)
INTERVAL( NUMTODSINTERVAL(1,'DAY'))
PARTITION DEFAULT_TIME_PART_01 VALUES LESS THAN (TIMESTAMP' 2010-08-01 00:00:00.000000000 +00:00')
LOGGING
COMPRESS FOR ALL OPERATIONS
TABLESPACE HPS_SUMMARY_DATA
NOCACHE
PARALLEL ( DEGREE DEFAULT INSTANCES DEFAULT )
MONITORING
/

I am not sure it can be done.
SQL> create table sales
2 (
3 sales_id number,
4 sales_dt TIMESTAMP(6) with local time zone NOT NULL
5 )
6 partition by range (sales_dt)
7 interval (numtoyminterval(1,'MONTH'))
8 ( partition p0901 values less than (to_date('2009-02-01','yyyy-mm-dd')) );
create table sales
ERROR at line 1:
ORA-14751: Invalid data type for partitioning column of an interval partitioned
table
SQL> ed
Wrote file afiedt.buf
1 create table sales
2 (
3 sales_id number,
4 sales_dt TIMESTAMP(6)
5 )
6 partition by range (sales_dt)
7 interval (numtoyminterval(1,'MONTH'))
8* ( partition p0901 values less than (to_date('2009-02-01','yyyy-mm-dd')) )
SQL> /
Table created.

Droping Partition Dynamically in Interval Partitioning

Hi All,
I have created an Interval Partition Table as show below, Is their any way, i can drop the partition dynamically when i truncate the table as oracle creates them with system generated name? Instead Alter table drop partition !
Create Table Script :
CREATE TABLE TBL_EMP_SALES
EMP_ID NUMBER(38),
EMPNAME VARCHAR2(9),
EMP_SALES_AMOUNT NUMBER(5),
EMP_SALES_DATE DATE,
CONSTRAINT PK_EMP_03 PRIMARY KEY (EMP_ID) USING INDEX TABLESPACE EMP_TABLESPACE
) NOLOGGING PARALLEL 4 TABLESPACE EMP_TABLESPACE
PARTITION BY RANGE(EMP_SALES_DATE)
INTERVAL (numtodsinterval(1,'day'))
STORE IN (EMP_TABLESPACE)
PARTITION P0 VALUES LESS THAN (to_date('23-AUG-2012','DD-MON-YYYY')) NOLOGGING
Insert Script :
INSERT INTO TBL_EMP_SALES VALUES (1001,'A',50,SYSDATE);
INSERT INTO TBL_EMP_SALES VALUES (1002,'B',100,SYSDATE+1);
INSERT INTO TBL_EMP_SALES VALUES (1003,'C',80,SYSDATE+2);
INSERT INTO TBL_EMP_SALES VALUES (1004,'D',250,SYSDATE+3);
INSERT INTO TBL_EMP_SALES VALUES (1005,'E',50,SYSDATE+4);
INSERT INTO TBL_EMP_SALES VALUES (1006,'F',50,SYSDATE+5);
INSERT INTO TBL_EMP_SALES VALUES (1007,'G',340,SYSDATE+6);
INSERT INTO TBL_EMP_SALES VALUES (1008,'H',120,SYSDATE+7);
COMMIT;
Partitions Created :
select segment_name,partition_name,bytes from user_segments where segment_name = 'TBL_EMP_SALES';
segment_name partition_name bytes
TBL_EMP_SALES     P0     8388608
TBL_EMP_SALES     SYS_P602     8388608
TBL_EMP_SALES     SYS_P603     8388608
TBL_EMP_SALES     SYS_P604     8388608
TBL_EMP_SALES     SYS_P605     8388608
TBL_EMP_SALES     SYS_P606     8388608
TBL_EMP_SALES     SYS_P607     8388608
TBL_EMP_SALES     SYS_P608     8388608
Thanks,
Varun
Edited by: 900575 on Aug 22, 2012 1:18 AM

Hi Kev82Fr,
Thanks for the useful post, I have tried your after trigger concept it works well and i have modified the code as below. Is their any other way where i can drop all the partition in the table in one shot ?
--------------------------------------Drop Partition Procedure--------------------------------
create or replace
PROCEDURE USP_PARTITION_DROP_TEST
AS
lv_cmd VARCHAR2(2000);
CURSOR parition_names IS
SELECT partition_name FROM user_segments WHERE segment_name = 'TBL_EMP_SALES';
parition_record parition_names%ROWTYPE;
BEGIN
OPEN parition_names;
LOOP
FETCH parition_names INTO parition_record;
EXIT WHEN parition_names%NOTFOUND;
SELECT 'ALTER TABLE TBL_EMP_SALES DROP PARTITION '||parition_record INTO lv_cmd FROM DUAL;
EXECUTE IMMEDIATE lv_cmd;
END LOOP;
CLOSE parition_names;
END USP_PARTITION_DROP_TEST;
---------------- After Truncate Trigger-----------------------------------
CREATE OR REPLACE TRIGGER TRG_PARTITION_DROP
after truncate on <SCHEMA NAME>.SCHEMA
BEGIN
USP_PARTITION_DROP_TEST();
END;
Thanks,
Varun

Range interval partitioning

Hi,
Using Oracle 11.20.3
We wish to have a range-hash composite partitioned table, one partition for each month.
However, want to esnure are always a partition tehrfore would like to use range interval partitioning.
Have a few questions, if have partition say 201301 to 201312 but get somew rosw which have value in date in June 2014 would it create
a new partition for each month i.e 201401, 201402 etc or just one for 201406?
Wanyt esnure system can cope automatically with following scenario
Daty1 have partitions 201301 to 201312
Day2 get record for 201406 (June 2014)
Day 3 get record for 201403 (March 2014)
We have no control of the range of dates we could get but don't want tpo have to manually create partitions fro all tehse dates in advance - want system to handled it automatically.
Also can you simply rename the system generated partition names to something more meaningful later.

>
Using Oracle 11.20.3
We wish to have a range-hash composite partitioned table, one partition for each month.
However, want to esnure are always a partition tehrfore would like to use range interval partitioning.
Have a few questions, if have partition say 201301 to 201312 but get somew rosw which have value in date in June 2014 would it create
a new partition for each month i.e 201401, 201402 etc or just one for 201406?
Wanyt esnure system can cope automatically with following scenario
Daty1 have partitions 201301 to 201312
Day2 get record for 201406 (June 2014)
Day 3 get record for 201403 (March 2014)
We have no control of the range of dates we could get but don't want tpo have to manually create partitions fro all tehse dates in advance - want system to handled it automatically.
>
Do NOT be afraid of breaking Oracle by actually trying things yourself.
DROP TABLE emp_part
CREATE TABLE emp_part (empno number(4), ename varchar2(10),
deptno number(2), created_date DATE default sysdate)
partition by range (created_date)
SUBPARTITION BY HASH(deptno) subpartitions 4
( partition p_prior_to_2014 values less than (to_date('01-01-2014', 'mm-dd-yyyy')));Add some data for 2014 and see for yourself what happens.
>
Also can you simply rename the system generated partition names to something more meaningful later.
>
Yes - assuming you mean more meaninful to a human. Oracle doesn't care what the name is.
And you can just as easily manipulate the partition (delete, insert, drop truncate) regardless of the name since you don't need to use the name to do those things.
You either know the date for the partition you want to work with or you don't. If you know then just tell Oracle and it will work with the correct partition. If you don't believe me try it with the sample code I gave you. Add some data to get a couple of interval partitions created and then drop one of them using Oracle's extended partition syntax. See this example in the 'Dropping Interval Partitions in the VLDB and Partitioning Guide
http://docs.oracle.com/cd/B28359_01/server.111/b32024/part_admin.htm#i1007479
>
The following example drops the September 2007 interval partition from the sales table. There are only local indexes so no indexes will be invalidated.
ALTER TABLE sales DROP PARTITION FOR(TO_DATE('01-SEP-2007','dd-MON-yyyy'));
>
That code doesn't require the partition name. You just need to specify a date that falls IN the partition that you want to drop. You have to do that whether you know the name of the partition or not. Don't 'gunk up' your system with code to rename things unless there is some real need to.

INTERVAL PARTITION NAMING

hi,
is it possible to identify a syntax or wildcard for interval partition naming while creating interval partitioned table?
(of course, a job, sched. job or a script can be used to rename partitions, but my questions is is it possible when creating?)
thanks

>
is it possible to identify a syntax or wildcard for interval partition naming while creating interval partitioned table?
(of course, a job, sched. job or a script can be used to rename partitions, but my questions is is it possible when creating?)
>
No - that is not possible.
Why do you care what the name is?
You can use the PARTITION FOR syntax to refer to a particular partition in queries.
alter table DEMO_INTERVAL_DATA_LOAD1 drop partition for (TO_DATE('01-APR-2000','DD-MON-YYYY'));
select count(*) from PART_TEST_TBL subpartition for(10,'BLUE');See the 'partition_extension_clause' of the SELECT statement in the SQL Language doc
http://docs.oracle.com/cd/B28359_01/server.111/b28286/sql_elements009.htm#i165979
>
References to Partitioned Tables and Indexes Tables and indexes can be partitioned. When partitioned, these schema objects consist of a number of parts called partitions, all of which have the same logical attributes. For example, all partitions in a table share the same column and constraint definitions, and all partitions in an index share the same index columns.
Partition-extended and subpartition-extended names let you perform some partition-level and subpartition-level operations, such as deleting all rows from a partition or subpartition, on only one partition or subpartition. Without extended names, such operations would require that you specify a predicate (WHERE clause). For range- and list-partitioned tables, trying to phrase a partition-level operation with a predicate can be cumbersome, especially when the range partitioning key uses more than one column. For hash partitions and subpartitions, using a predicate is more difficult still, because these partitions and subpartitions are based on a system-defined hash function.
Partition-extended names let you use partitions as if they were tables. An advantage of this method, which is most useful for range-partitioned tables, is that you can build partition-level access control mechanisms by granting (or revoking) privileges on these views to (or from) other users or roles. To use a partition as a table, create a view by selecting data from a single partition, and then use the view as a table.

Index issue with or and between when we set one partition index to unusable

Need to understand why optimizer unable to use index in case of "OR" whenn we set one partition index to unusable, the same query with between uses index.
“OR” condition fetch less data comparing to “BETWEEN” still oracle optimizer unable to use indexes in case of “OR”
1. Created local index on partitioned table
2. ndex partition t_dec_2009 set to unusable
-- Partitioned local Index behavior with “OR” and with “BETWEEN”
SQL> CREATE TABLE t (
2    id NUMBER NOT NULL,
3    d DATE NOT NULL,
4    n NUMBER NOT NULL,
5    pad VARCHAR2(4000) NOT NULL
6 )
7 PARTITION BY RANGE (d) (
8    PARTITION t_jan_2009 VALUES LESS THAN (to_date('2009-02-01','yyyy-mm-dd')),
9    PARTITION t_feb_2009 VALUES LESS THAN (to_date('2009-03-01','yyyy-mm-dd')),
10    PARTITION t_mar_2009 VALUES LESS THAN (to_date('2009-04-01','yyyy-mm-dd')),
11    PARTITION t_apr_2009 VALUES LESS THAN (to_date('2009-05-01','yyyy-mm-dd')),
12    PARTITION t_may_2009 VALUES LESS THAN (to_date('2009-06-01','yyyy-mm-dd')),
13    PARTITION t_jun_2009 VALUES LESS THAN (to_date('2009-07-01','yyyy-mm-dd')),
14    PARTITION t_jul_2009 VALUES LESS THAN (to_date('2009-08-01','yyyy-mm-dd')),
15    PARTITION t_aug_2009 VALUES LESS THAN (to_date('2009-09-01','yyyy-mm-dd')),
16    PARTITION t_sep_2009 VALUES LESS THAN (to_date('2009-10-01','yyyy-mm-dd')),
17    PARTITION t_oct_2009 VALUES LESS THAN (to_date('2009-11-01','yyyy-mm-dd')),
18    PARTITION t_nov_2009 VALUES LESS THAN (to_date('2009-12-01','yyyy-mm-dd')),
19    PARTITION t_dec_2009 VALUES LESS THAN (to_date('2010-01-01','yyyy-mm-dd'))
20 );
SQL> INSERT INTO t
2 SELECT rownum, to_date('2009-01-01','yyyy-mm-dd')+rownum/274, mod(rownum,11), rpad('*',100,'*')
3 FROM dual
4 CONNECT BY level <= 100000;
SQL> CREATE INDEX i ON t (d) LOCAL;
SQL> execute dbms_stats.gather_table_stats(user,'T')
-- Mark partition t_dec_2009 to unusable:
SQL> ALTER INDEX i MODIFY PARTITION t_dec_2009 UNUSABLE;
--- Let’s check whether the usable index partition can be used to apply a restriction: BETWEEN
SQL> SELECT count(d)
    FROM t
    WHERE d BETWEEN to_date('2009-01-01 23:00:00','yyyy-mm-dd hh24:mi:ss')
                AND to_date('2009-02-02 01:00:00','yyyy-mm-dd hh24:mi:ss');
SQL> SELECT * FROM table(dbms_xplan.display_cursor(format=>'basic +partition'));
| Id | Operation               | Name | Pstart| Pstop |
|   0 | SELECT STATEMENT        |      |       |       |
|   1 | SORT AGGREGATE         |      |       |       |
|   2 |   PARTITION RANGE SINGLE|      |    12 |    12 |
|   3 |    INDEX RANGE SCAN     | I    |    12 |    12 |
--- Let’s check whether the usable index partition can be used to apply a restriction: OR
SQL> SELECT count(d)
    FROM t
    WHERE
    (d >= to_date('2009-01-01 23:00:00','yyyy-mm-dd hh24:mi:ss') and d <= to_date('2009-01-01 23:59:59','yyyy-mm-dd hh24:mi:ss'))
    or
    (d >= to_date('2009-02-02 01:00:00','yyyy-mm-dd hh24:mi:ss') and d <= to_date('2009-02-02 02:00:00','yyyy-mm-dd hh24:mi:ss'))
SQL> SELECT * FROM table(dbms_xplan.display_cursor(format=>'basic +partition'));
| Id | Operation           | Name | Pstart| Pstop |
|   0 | SELECT STATEMENT    |      |       |       |
|   1 | SORT AGGREGATE     |      |       |       |
|   2 |   PARTITION RANGE OR|      |KEY(OR)|KEY(OR)|
|   3 |    TABLE ACCESS FULL| T    |KEY(OR)|KEY(OR)|
----------------------------------------------------“OR” condition fetch less data comparing to “BETWEEN” still oracle optimizer unable to use indexes in case of “OR”
Regards,
Sachin B.

Hi,
What is your database version????
I ran the same test and optimizer was able to pick the index for both the queries.
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod
PL/SQL Release 10.2.0.4.0 - Production
CORE    10.2.0.4.0      Production
TNS for 32-bit Windows: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
SQL>
SQL> set autotrace traceonly exp
SQL>
SQL>
SQL> SELECT count(d)
2 FROM t
3 WHERE d BETWEEN to_date('2009-01-01 23:00:00','yyyy-mm-dd hh24:mi:ss')
4              AND to_date('2009-02-02 01:00:00','yyyy-mm-dd hh24:mi:ss');
Execution Plan
Plan hash value: 2381380216
| Id | Operation                 | Name | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
|   0 | SELECT STATEMENT          |      |     1 |     8 |    25   (0)| 00:00:01 |       |       |
|   1 | SORT AGGREGATE           |      |     1 |     8 |            |          |       |       |
|   2 |   PARTITION RANGE ITERATOR|      | 8520 | 68160 |    25   (0)| 00:00:01 |     1 |     2 |
|* 3 |    INDEX RANGE SCAN       | I    | 8520 | 68160 |    25   (0)| 00:00:01 |     1 |     2 |
Predicate Information (identified by operation id):
   3 - access("D">=TO_DATE(' 2009-01-01 23:00:00', 'syyyy-mm-dd hh24:mi:ss') AND
              "D"<=TO_DATE(' 2009-02-02 01:00:00', 'syyyy-mm-dd hh24:mi:ss'))
SQL> SELECT count(d)
2 FROM t
3 WHERE
4 (
5 (d >= to_date('2009-01-01 23:00:00','yyyy-mm-dd hh24:mi:ss') and d <= to_date('2009-01-01 23:59:59','yyyy-mm-dd hh24:mi:ss'
6 or
7 (d >= to_date('2009-02-02 01:00:00','yyyy-mm-dd hh24:mi:ss') and d <= to_date('2009-02-02 02:00:00','yyyy-mm-dd hh24:mi:ss'
8 );
Execution Plan
Plan hash value: 3795917108
| Id | Operation                | Name | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
|   0 | SELECT STATEMENT         |      |     1 |     8 |     4   (0)| 00:00:01 |       |       |
|   1 | SORT AGGREGATE          |      |     1 |     8 |            |          |       |       |
|   2 |   CONCATENATION          |      |       |       |            |          |       |       |
|   3 |    PARTITION RANGE SINGLE|      |    13 |   104 |     2   (0)| 00:00:01 |     2 |     2 |
|* 4 |     INDEX RANGE SCAN     | I    |    13 |   104 |     2   (0)| 00:00:01 |     2 |     2 |
|   5 |    PARTITION RANGE SINGLE|      |    13 |   104 |     2   (0)| 00:00:01 |     1 |     1 |
|* 6 |     INDEX RANGE SCAN     | I    |    13 |   104 |     2   (0)| 00:00:01 |     1 |     1 |
Predicate Information (identified by operation id):
   4 - access("D">=TO_DATE(' 2009-02-02 01:00:00', 'syyyy-mm-dd hh24:mi:ss') AND
              "D"<=TO_DATE(' 2009-02-02 02:00:00', 'syyyy-mm-dd hh24:mi:ss'))
   6 - access("D">=TO_DATE(' 2009-01-01 23:00:00', 'syyyy-mm-dd hh24:mi:ss') AND
              "D"<=TO_DATE(' 2009-01-01 23:59:59', 'syyyy-mm-dd hh24:mi:ss'))
       filter(LNNVL("D"<=TO_DATE(' 2009-02-02 02:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR
              LNNVL("D">=TO_DATE(' 2009-02-02 01:00:00', 'syyyy-mm-dd hh24:mi:ss')))
SQL> set autotrace off
SQL>Asif Momen
http://momendba.blogspot.com

Parallel creation of partitionned index and tablespace Temp size

Hi,
I'am not able to find the information if when building in parallel a locally partitionned index, Oracle will iterate on all the partition and then use temp tbs for one partitionned or it will compute for all the partitionned simultaneously ?
Thanks for your help

If I understand your question correctly, the temp tablespace is used for sorting, but there are temp segments created in the tablespaces where the indices will actually belong. See the demo on how to work it out for yourself: http://hemantoracledba.blogspot.com/2008/05/temporary-segments-in-dataindex.html
Also find Randolf's blog for some other interesting factoids: http://oracle-randolf.blogspot.com/2011/02/parallel-dml-conventional-non-direct.html

Partition index are not visible after import in 11g

Hi,
target database : oracle version : 11.2.0.1
Source database : 10.2.0.4
i have a table in 10.2.0.4 and need to transfer to 11.2.0.1
SQL> SELECT i.index_name, i.partition_name
FROM dba_ind_partitions i, dba_tab_partitions t
WHERE i.partition_name = t.partition_name
AND t.table_name = 'BKPG';
2    3    4
INDEX_NAME                     PARTITION_NAME
I_BKPG_ACT_REC_IDX             BKPG_2010_JUN_DEC
I_BKPG_ACCT_ACTD_REC_IDX       BKPG_2010_JUN_DEC
I_BKPG_ACCT_REC_ACT_IDX        BKPG_2010_JUN_DEC
I_BKPG_STLM_REC_ACC_IDX        BKPG_2010_JUN_DEC
I_BKPG_STLM_ACC_REC_IDX        BKPG_2010_JUN_DEC
I_BKPG_ORD_IDX                 BKPG_2010_JUN_DEC
I_BKPG_TDATE_REC_BS_IDX        BKPG_2010_JUN_DEC
I_BKPG_CUSIP                   BKPG_2010_JUN_DEC
I_BKPG_ACCT_TRDDTE_REC_IDX     BKPG_2010_JAN_JUN
I_BKPG_ACCT_ACTD_REC_IDX       BKPG_2010_JAN_JUN
I_BKPG_TDATE_REC_BS_IDX        BKPG_2010_JAN_JUN
INDEX_NAME                     PARTITION_NAME
I_BKPG_ACCT_REC_ACT_IDX        BKPG_2010_JAN_JUN
I_BKPG_ACT_REC_IDX             BKPG_2010_JAN_JUN
I_BKPG_ORD_IDX                 BKPG_2010_JAN_JUN
I_BKPG_STLM_ACC_REC_IDX        BKPG_2010_JAN_JUN
I_BKPG_ACCT_TRDDTE_REC_IDX     BKPG_2010_JUN_DEC
I_BKPG_CUSIP                   BKPG_2010_JAN_JUN
I_BKPG_STLM_REC_ACC_IDX        BKPG_2010_JAN_JUN
18 rows selected.i took the export of this table and during import i used follwing parameters
impdp directory=TEST transform=segment_attributes:n REMAP_SCHEMA=dev:prakash1 dumpfile=BKPG1.dmp -> as to avoid the storage clause error i used transform=segment_attributes:n
import went sucessfull but if i query below sql zero rows returns
SQL> SELECT i.index_name, i.partition_name
FROM dba_ind_partitions i, dba_tab_partitions t
WHERE i.partition_name = t.partition_name
AND t.table_name = 'BKPG';
2    3    4
no rows selectedwhy i am not able to query partitions index , please advice
Thanks

Thanks for the update,
i am unbale to see these index partitions in the views dba_ind_partitions but i am able to see in dba_objects;
I_BKPG_ACCT_TRDDTE_REC_IDX               INDEX PARTITION
OBJECT_NAME                              OBJECT_TYPE
I_BKPG_ACCT_TRDDTE_REC_IDX               INDEX PARTITION
I_BKPG_ACCT_TRDDTE_REC_IDX               INDEX PARTITION
I_BKPG_ACCT_TRDDTE_REC_IDX               INDEX PARTITION
I_BKPG_ACCT_TRDDTE_REC_IDX               INDEX PARTITION
I_BKPG_ACCT_TRDDTE_REC_IDX               INDEX PARTITION
I_BKPG_ACCT_TRDDTE_REC_IDX               INDEX PARTITION
I_BKPG_ACCT_TRDDTE_REC_IDX               INDEX PARTITION
I_BKPG_ACCT_TRDDTE_REC_IDX               INDEX PARTITION
I_BKPG_ACCT_TRDDTE_REC_IDX               INDEX PARTITION
I_BKPG_CUSIP                             INDEX PARTITION
I_BKPG_CUSIP                             INDEX PARTITION
OBJECT_NAME                              OBJECT_TYPE
I_BKPG_CUSIP                             INDEX PARTITION
I_BKPG_CUSIP                             INDEX PARTITION
I_BKPG_CUSIP                             INDEX PARTITION
I_BKPG_CUSIP                             INDEX PARTITION
I_BKPG_CUSIP                             INDEX PARTITION
I_BKPG_CUSIP                             INDEX PARTITION
I_BKPG_CUSIP                             INDEX PARTITION
I_BKPG_CUSIP                             INDEX PARTITION
I_BKPG_CUSIP                             INDEX PARTITION
I_BKPG_CUSIP                             INDEX PARTITION
I_BKPG_CUSIP                             INDEX PARTITION
.why i am unable to see in dba_ind_partitions view
Thanks

SDO_UTIL.PREPARE_FOR_TTS and Partitioned Indexes

Does this procedure work with partitioned indexes?
After executing this procedure on tablespace that contains the first partition of the partition index, the table SDO_INDEX_TTS_METADATA$ is empty. In addition, I can only run this procedure once, it fails for each subsequent tablespace which has a partition.
When I execute the procedure on a tablespace with a non partitioned index the SDO_INDEX_TTS_METADATA$ table is populated.

Thanks Dear ,
for your immediate reply .....
As u suggest I have tried all the following combitation but still it does not work;
SDO_UTIL.INITIALIZE_INDEX*ES*FORTTS;
SDO_UTIL.INITIALIZE_INDEXES_FOR_TTS;
SDO_UTIL.INITIALIZE_INDEX_FOR_TTS;
it gives same error....
Thanks & Regards
Chandrakishore Bankhede

Re-org oracle 11.1.0.7 partitioned and sub partitioned index not validiting

Hi,
As part of maintenance i did the following thing on the oracle 11.1.0.7 on windows (no archive log mode);
     Re-orgnaized the tables in application- data tablespace - done
     Re-orgnaized large table in SYSAUX tablespace - only one table (alter table sys.WRI$_OPTSTAT_HISTGRM_HISTORY move tablespace sysaux
alter index sys.I_WRI$_OPTSTAT_H_OBJ#_ICOL#_ST rebuild nologging;
alter index sys.I_WRI$_OPTSTAT_H_ST rebuild nologging;)
     Re-built the indexes on applicaton index tbs- done
     Re-built the partition indexes on application index tbs - done
     rebuilding of indexes in SYSAUX - done since it was invalid
     Run the analyze job –
     Re-claim the space at database level and OS level
but i have the issues of partitioned and subpartition indexes are not validating..how to validate the indexes i am using the below querires but:
ORA-14287: cannot REBUILD a partition of a Composite Range partitioned i

i am using the below sqls:
set head off
set linesize 200
select 'alter index '||index_owner||'.'||index_name||' rebuild partition '||partition_name||' ; ' from dba_ind_partitions where status <> 'VALID' and index_owner not in ('SYS','SYSTEM')
set head off
set linesize 200
select 'alter index '||index_owner||'.'||index_name||' rebuild subpartition '||subpartition_name||' ;'
from dba_ind_subpartitions
where status <> 'VALID'

Interval partitioning indexes

Similar Messages

Maybe you are looking for