create partitioned indexes

Similar Questions

• Creating Local index on an existing partitioned table

  I have an existing table partitioned by list. I'm supposed to create local indexes on this subject.

  I'm using Oracle 11 g.

  I have an existing table partitioned by list. I'm supposed to create local indexes on this subject.

  I'm using Oracle 11 g.

  The skill the MOST IMPORTANT you can learn, is at present, how to find information.

  A search on the SIMPLE web for 'local index of oracle 11g' returns this as the FIRST link

  https://docs.Oracle.com/CD/B28359_01/server.111/b28286/statements_5011.htm

  The "local_partitioned_index" section has all the information you need and it has code example showing you how do it.

• It's a good idea to create an index on a column used for partitioning

  I'm new to using partitions as well as the index. Can someone help me with the situation below?
  
  I have a table defined as below
  
  
  CREATE TABLE FACT_MASTER
  (
  PERIODCODE NUMBER (8) NOT NULL,
  PRODUCT_CD NUMBER (10) NOT NULL,
  DPT_CD NUMBER (3).
  FACT_VALUE1 NUMBER,
  FACT_VALUE2 NUMBER,
  FACT_VALUE3 NUMBER,
  .....
  .....
  .....
  .....
  .....
  FACT_VALUE50 NUMBER
  )
  PARTITION BY RANGE (PERIODCODE)
  (
  partition P1 lower values (2002),.
  partition P2 lower values (2003).
  lower partition P3 values (2004),
  ...
  ..
  )
  
  This table is partitioned on the shop period code.
  
  In a select query on the table, period code and product code are used. I intend to create an index to improve performance. Does make sense to include the period code column in the index? I intend to create indexes only for the product code column. I think that the partition itself behaves as an index for periodcode. Can someone tell me if this is correct? I use 10g.
  
  Published by: user6794035 on January 21, 2010 08:47
  
  Published by: user6794035 on January 21, 2010 08:50

  If the index is an overall index, then yes it is worth including. But check that your SQL would actually benefit an overall index.

  If your period still code in SQL, then the partition pruning will natuarally and would therefore not be required to be part of the index!

  P;

• Can I create an index on a partitioned table bitmap?

  Can I create an index on a partitioned table bitmap?

  Yes, you can. But an index on a partitioned table bitmap must be a local index.
  Image bitmap index on non partitioned tables cannot be partitioned.

• Creating partitioned local index

  Hi all
  
  Planing to run the range-partitioned on a table and creating Local partitioned index, but in the table is seen forced composite primary key thought to previously create Composite Unique Local partitioned index.
  
  Problem is when creating index its error ORA-14039 giving, of course it is not possible as partitioning column is not a subset of columns in a UNIQUE index key.
  
  Is there no workaround solution to create Local partitioned indexes... otherwise I'll be forced to create the overall index part?
  
  Y at - it no drawback if I create Composite Unique Local partitioned indexes including the columns of partitioning on purpose?
  
  There will be no impact if I create the index Composite Unique Local partitioned by including the columns voluntarily on the SQL QUERIES, access this table partitioning?
  
  Please suggest me a workaround solution.
  

  CREATE TABLE YASIR.CS_RESEARCH (ORDER_NBR NUMBER NOT NULL,
                        ORDER_DETAIL_NBR NUMBER NOT NULL,
                        SESSION_ID VARCHAR2(40),
                        PRODUCT_GROUP VARCHAR2(16) NOT NULL,
                        PRODUCT_SUBGROUP VARCHAR2(16) DEFAULT 'N/A',
                        FORMAT_TYPE VARCHAR2(10) NOT NULL,
                        CONTRIBUTOR VARCHAR2(60) NOT NULL,
                        DOCUMENT_NUMBER VARCHAR2(15) NOT NULL,
                        DOCUMENT_DATE DATE,
                        BILLABLE_PAGES NUMBER,
                        NON_BILLABLE_PAGES VARCHAR2(512),
                        PURCHASED_UNITS VARCHAR2(2000),
                        DELIVERY_METHOD VARCHAR2(6) DEFAULT 'ONLINE',
                        COMPANY_NAME VARCHAR2(120),
                        STATUS VARCHAR2(10) DEFAULT 'NEW',
                        CONTENT_CODE VARCHAR2(15) NOT NULL, 
                        CONTENT_CODE_DESC VARCHAR2(60),
                        ITEM_PRICE NUMBER NOT NULL,
                        PAGES_ORDERED NUMBER,
                        LAST_MNT_DATE_TIME DATE NOT NULL,
                        LAST_MNT_OPID VARCHAR2(120) NOT NULL,
                        CREATE_DATE DATE NOT NULL,
                        DML_FLAG CHAR(1) NOT NULL)
       PARTITION BY RANGE (CREATE_DATE) 
       (PARTITION CS_RESEARCH_2009_Q2 VALUES LESS THAN (MAXVALUE));
  
  ###Split partitions:
  ALTER TABLE YASIR.cs_research
    SPLIT PARTITION CS_RESEARCH_2009_Q2 AT (TO_DATE('30-SEP-2007 23:59:59', 'DD-MON-YYYY HH24:MI:SS'))
    INTO (PARTITION CS_RESEARCH_2007_Q3,
          PARTITION CS_RESEARCH_2009_Q2);
  
  ALTER TABLE YASIR.cs_research
    SPLIT PARTITION CS_RESEARCH_2009_Q2 AT (TO_DATE('31-DEC-2007 23:59:59', 'DD-MON-YYYY HH24:MI:SS'))
    INTO (PARTITION CS_RESEARCH_2007_Q4,
          PARTITION CS_RESEARCH_2009_Q2);
  
  ALTER TABLE YASIR.cs_research
    SPLIT PARTITION CS_RESEARCH_2009_Q2 AT (TO_DATE('31-MAR-2008 23:59:59', 'DD-MON-YYYY HH24:MI:SS'))
    INTO (PARTITION CS_RESEARCH_2008_Q1,
          PARTITION CS_RESEARCH_2009_Q2);
  
  ALTER TABLE YASIR.cs_research
    SPLIT PARTITION CS_RESEARCH_2009_Q2 AT (TO_DATE('30-JUN-2008 23:59:59', 'DD-MON-YYYY HH24:MI:SS'))
    INTO (PARTITION CS_RESEARCH_2008_Q2,
          PARTITION CS_RESEARCH_2009_Q2);
  
  ALTER TABLE YASIR.cs_research
    SPLIT PARTITION CS_RESEARCH_2009_Q2 AT (TO_DATE('30-SEP-2008 23:59:59', 'DD-MON-YYYY HH24:MI:SS'))
    INTO (PARTITION CS_RESEARCH_2008_Q3,
          PARTITION CS_RESEARCH_2009_Q2);
  
  ALTER TABLE YASIR.cs_research
    SPLIT PARTITION CS_RESEARCH_2009_Q2 AT (TO_DATE('31-DEC-2008 23:59:59', 'DD-MON-YYYY HH24:MI:SS'))
    INTO (PARTITION CS_RESEARCH_2008_Q4,
          PARTITION CS_RESEARCH_2009_Q2);
  
  ALTER TABLE YASIR.cs_research
    SPLIT PARTITION CS_RESEARCH_2009_Q2 AT (TO_DATE('31-MAR-2009 23:59:59', 'DD-MON-YYYY HH24:MI:SS'))
    INTO (PARTITION CS_RESEARCH_2009_Q1,
          PARTITION CS_RESEARCH_2009_Q2);
  
  ###Create indexes on cs_research except primary key index CSR_PKEY:
  alter session set sort_area_size=262144000; -----(250MB Total will be 1GB for 4 parallel process)
  create index YASIR.CSR_DETAIL_NBR on YASIR.CS_RESEARCH(TO_NUMBER(REPLACE(TO_CHAR(ORDER_NBR,'999999999')||TO_CHAR(ORDER_DETAIL_NBR,'999999999'),' ',''),'999999999999')) LOCAL
            (PARTITION CS_RESEARCH_2007_Q3 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2007_Q4 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q1 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q2 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q3 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q4 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2009_Q1 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2009_Q2 TABLESPACE USERS)
       nologging parallel (degree 4);
  Index created.
  
  create index YASIR.CSR_SESSION on YASIR.CS_RESEARCH(SESSION_ID,ORDER_NBR) LOCAL
            (PARTITION CS_RESEARCH_2007_Q3 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2007_Q4 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q1 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q2 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q3 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q4 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2009_Q1 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2009_Q2 TABLESPACE USERS)
       nologging parallel (degree 4);
  Index created.
  
  create index YASIR.CSR_CREATED on YASIR.CS_RESEARCH(CREATE_DATE) LOCAL
            (PARTITION CS_RESEARCH_2007_Q3 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2007_Q4 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q1 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q2 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q3 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q4 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2009_Q1 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2009_Q2 TABLESPACE USERS)
       nologging parallel (degree 4); 
  Index created.
  
  create index YASIR.CSR_DOCUMENT_NUMBER on YASIR.CS_RESEARCH(DOCUMENT_NUMBER) LOCAL
            (PARTITION CS_RESEARCH_2007_Q3 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2007_Q4 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q1 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q2 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q3 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q4 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2009_Q1 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2009_Q2 TABLESPACE USERS)
       nologging parallel (degree 4); 
  Index created.
  
  create index YASIR.CSR_STATUS on YASIR.CS_RESEARCH(STATUS) LOCAL
            (PARTITION CS_RESEARCH_2007_Q3 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2007_Q4 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q1 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q2 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q3 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q4 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2009_Q1 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2009_Q2 TABLESPACE USERS)
       nologging parallel (degree 4);
  Index created.
   
  create unique index CSR_PRKEY_IND on YASIR.CS_RESEARCH(ORDER_NBR,ORDER_DETAIL_NBR) LOCAL
       (PARTITION CS_RESEARCH_2007_Q3 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2007_Q4 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q1 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q2 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q3 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2008_Q4 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2009_Q1 TABLESPACE USERS,
            PARTITION CS_RESEARCH_2009_Q2 TABLESPACE USERS)
       nologging parallel (degree 4);
  ERROR at line 1:
  ORA-14039: partitioning columns must form a subset of key columns of a UNIQUE
  index

  Thank you
  Yasser

  YasserRACDBA wrote:
  I want to create a unique partitioned index Local and use this primary key index.

  But my main question is if this create_date column will affect all sql queries that are not used in where clause?

  Yasser,

  your main question should not be about performance queries, but the consequence of adding the CREATE_DATE to the local unique index:

  1. you change the meaning of the primary key: adding the CREATE_DATE means that the unique character of ORDER_NBR, ORDER_DETAIL_NBR is only applied by CREATE_DATE. I guess that does not match the business experience that this primary key is supposed to enforce and defeated the original purpose of the uniqueness that is unique values of ORDER_NBR, ORDER_DETAIL_NBR across the table.

  2. If you want to use as a key in other tables you must add the CREATE_DATE to all child tables, because you need to refer to the primary key complete a relationship of key foreign primary key.

  So the only 'right' way to do this is to use a unique comprehensive index on ORDER_NBR, ORDER_DETAIL_NBR. Of course, this means you must rebuild whenever a partition maintenance is carried out which invalidates the overall index since you use 8i and you cannot use the UPDATE GLOBAL INDEXES clause.

  Kind regards
  Randolf

  Oracle related blog stuff:
  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/

• Hang partitioned index text on construction

  I have a partitioned table with 2 000 000 + lines with a blob column.  When you try to create an index of type CTXSYS. CONTEXT that is partitioned correctly finished 8 of 10 partitions but crashes right on the other 2 indefinitely.  I am building with a parallel degree of 8.  Three of these have expected of 'direct path read' while the rest are the "PX Deq: execution Msg.

  Any ideas?

  Ok.  18121298 patch solves this problem.  Discovered this while trying to make a service request.

• deletion of a partitioned index

  Hi friends,

  I use 10.2.0.4 oracle on solaris.

  I have several partitioned index with the 2011 created on a daily basis. I tried to drop one of the indexes and got the below error.

  SQL > ALTER INDEX QOSDEV. PK_RATE_CISCOMEMORYPOOL DROP PARTITION 'OCTOBER 5, 2012 '.

  ALTER INDEX QOSDEV. PK_RATE_CISMEPOOL DROP PARTITION 'OCTOBER 5, 2012 '.

  Error on line 2

  ORA-14076: submitted alter index partition/subpartition operation is not valid for local partitioned indexes

  Script done on line 2.

  I ask you how to remove these partitions.

  Thank you

  DBApps

  Hello

  Try-

  ALTER drop partition table RATE_CISCOMEMORYPOOL 'October 5, 2012;

  Anand

• Creating partitions by a transformation (javascript)

  Hello

  I have several tables of partition by list and add partitions to this table.

  How can I do with a transformation of javascript?

  Thanks for your help.

  Jan

  Hi Jan,

  I think you're looking for this:

  tables = model.getTableSet () .toArray ();

  for (var t = 0; t)<>

  relational model table

  rmTable = tables [t];

  physical model table

  pmTable = model.getStorageDesign () .getStorageObject (rmTable.getObjectID ());

  pmTable.setPartitioned ("YES");

  Create partition

  partition = pmTable.createPartitionOracle ();

  partition.setName ("partition_1");

  Browse columns if necessary

  pmTableColumns = pmTable.getColumns ();

  for (var c = 0; c)<>

  column = pmTableColumns [c];

  // }

  }

  It would be better if one day I discovered how use [code] tags in the new forum...

  In any case, its just example, you will need to extend it. There are other properties of the partition that can be set. Find them in /datamodeler/xmlmetadata/doc/index.html

  Search for TableProxyOracle, PartitionOracle

• Partitioned index

  Using Oracle 11.2.0.3
  
  We are evalauating partitiong stragetegies with a view to the realization of gains from perfomnace in reports in particular.
  
  How effeicient are partitioned indexes in this by example anti-terrorism just partitioned index aan table is not partitioned.
  
  One big fact to durrogate keys that have bitmpa indxese table which link to accentuate associated key dimensions.
  
  Patitioning given bitmap index which links to the largest dimension and partitiong Kay dimesnion dimension laregts.
  
  Reflections on partitioned indexes would be particularly useful.
  
  Thank you

  user5716448 wrote:
  Using Oracle 11.2.0.3

  We are evalauating partitiong stragetegies with a view to the realization of gains from perfomnace in reports in particular.

  How effeicient are partitioned indexes in this by example anti-terrorism just partitioned index aan table is not partitioned.

  One big fact to durrogate keys that have bitmpa indxese table which link to accentuate associated key dimensions.

  Patitioning given bitmap index which links to the largest dimension and partitiong Kay dimesnion dimension laregts.

  Reflections on partitioned indexes would be particularly useful.

  Thank you

  It is not possible to create a partitioned index bitmp on a non-partitioned table. Bitmap indexes can be local partitioned only.
  --
  John Watson
  Oracle Certified Master s/n
  http://skillbuilders.com

• partitioning index.

  Hi all
  Is it possible to partition the partion of maxvalue index created using index range partitioning.

  Hello

  If you talk to split a partition into several smaller, then Yes, you can do, see:

  http://asktom.Oracle.com/pls/asktom/f?p=100:11:0:P11_QUESTION_ID:660224234238

  If not, please clarify what you mean.

  Best regards
  Nikolai

• Global partitioned index shows State N/A sqldeveloper

  Hi again,
  
  I tried to create a global index divided by 4 hash partitions to be used as the primary key.
  
  I think I understand the syntax for creating an index of global hash (using 4 partitions) that is used by the primary key constraint.
  Here's my response:
  
  ALTER table vehicle_data
  Add the constraint of KEY PRIMARY C_PK_ID
  (
  ID
  )
  USING INDEX
  HASH PARTITION (LWVD_ID)
  4. THE PARTITIONS
  ENABLE;
  
  What I don't understand is this:
  When I take the sqldeveloper, go to the table and select the tab 'index' index status is indicated by n/a. When I create the index without partitioning it shows valid.
  What is the problem that I forgot?
  
  Thanks again,
  Andreas

  You forgot that it is partitioned.

  If you look in ALL_IND_PARTITIONS for the State.

• Local partitioned indexes

  Hi all
  
  I created 2 local partitioned index. The indexes are indexes of function. the table size is 2.3 T.
  I created the first clue that it took 14 hours to create, and even to analyze and it works fine now. Then, I created second index. But now it does not.
  What should I do?
  
  version 11.1.0.6
  RAC, ASM
  
  Thanks in advance
  
  Published by: disaster on April 10, 2011 21:43
  
  Published by: disaster on April 10, 2011 21:51

  Dear Sir

  ----------------------------------------------------------------------------------------------------------
  | Id  | Operation              | Name         | Starts | E-Rows | A-Rows |   A-Time   | Buffers | Reads  |
  ----------------------------------------------------------------------------------------------------------
  |   1 |  PARTITION RANGE SINGLE|              |      1 |      1 |     82 |00:03:37.92 |     534K|    534K|
  |*  2 |   TABLE ACCESS FULL    | TBL          |      1 |      1 |     82 |00:03:37.92 |     534K|    534K|
  ----------------------------------------------------------------------------------------------------------
  

  It is the plan of the real explanation followed by the SQL engine to run your query

  The Oracle optimizer is the estimate (based on the statistics that you have collected about index and table) that your query will return only 1 rank (E-lines = 1) while in reality (when the query has been executed) it's return of 82 lines (A-Rows = 82) within 3 minutes and 37 seconds (A-Time = 00:03:37.92)

  It is clear that your index function that is not used.

  You should be aware that when you create a function based index, oracle will create a virtual column that is hidden behind the scene.

  Try to gather statistics on this column using dbms_stats.

  Please, try first to TEST

  BEGIN
     DBMS_STATS.gather_table_stats
                   (ownname             => user,
                    tabname             => 'TBL',
                    CASCADE             => TRUE,
                    method_opt         => 'FOR ALL HIDDEN COLUMNS SIZE 1'
                           );
  END;
  /
  

  and re - run your query and post once again the new plan explain him like you did before

  Best regards

  Mohamed Houri

• Global partitioned index hash

  Is it possible to create an index of global partitioned hash on the columns of the primary key of a table that is not partitioned itself?
  If a table has a PK constraint there an index generated automatically on the PK columns.
  Y at - it a syntax to make the overall index partitioned hash when creating the constraint of PK,.
  or syntax to MODIFY the indexes after the creation of the constraint?

  When you add a Pk to a table, you can choose a place already in the index. Something like

  alter table t1 add constraint T_PK primary key (col1) using index T_IDX;
  

  Create the partitioned index as you like with the same columns as the primary key and use the foregoing.

• partitioning and partitioned index

  I created 1 table with partitions.
  
  CREATE TABLE SAMPLE_ORDERS
  (NUMBER OF ORDER_NUMBER,
  ORDER_DATE DATE,
  NUMBER OF CUST_NUM
  NUMBER OF TOTAL_PRICE
  NUMBER OF TOTAL_TAX
  NUMBER OF TOTAL_SHIPPING)
  PARTITION OF RANGE (ORDER_DATE)
  (
  SO99Q1 PARTITION VALUES LESS THAN (TO_DATE (APRIL 1, 1999 ',' MON-DD-YYYY "")),
  SO99Q2 PARTITION VALUES LESS THAN (TO_DATE (1 JULY 1999 ',' MON-DD-YYYY "")),
  SO99Q3 PARTITION VALUES LESS THAN (TO_DATE (OCTOBER 1, 1999 ',' MON-DD-YYYY "")),
  SO99Q4 PARTITION VALUES LESS THAN (TO_DATE (JANUARY 1, 2000 ',' MON-DD-YYYY "")),
  SO00Q1 PARTITION VALUES LESS THAN (TO_DATE (APRIL 1, 2000 ',' MON-DD-YYYY "")),
  SO00Q2 PARTITION VALUES LESS THAN (TO_DATE (JULY 1, 2000 ',' MON-DD-YYYY "")),
  SO00Q3 PARTITION VALUES LESS THAN (TO_DATE (OCTOBER 1, 2000 ',' MON-DD-YYYY "")),
  SO00Q4 PARTITION VALUES LESS THAN (TO_DATE (JANUARY 1, 2001 ',' MON-DD-YYYY ""))
  )
  ;
  
  
  Few questions is now.
  1. How can I create indexes on the table.
  2. How can I rebuild the index if it is partitioned index?
  3. What is the impact of the reconstruction of indexes on the table (all table locks or just locks partitioned index)
  4. If I want to create partition for future purposes, for example for each month do I need to partition manually created for the same thing?
  
  Thank you

  When you create an Index with the keyword LOCAL and do not specify the names of each partition, Oracle uses the default Partition of Table name.

  For example, to rebuild the index corresponding to the first partition of the table, partition

  alter index sales_orders_ndx_l rebuild partition SO99Q1 ;
  

  DML may continue to run against the other partitions of the table (and their corresponding indices).

  When you do the maintenance of the score as the addition of a new Partition or split an existing Partition, for each Partition of the 'new' Table, a corresponding Index Partition will be automatically created.
  In order to ensure that the affected Index partitions are not left in a State UNUSABLE but are also rebuilt with maintaining the Table Partition, add the clause INDEX of UPDATE of the ALTER TABLE statement you use.

• Table partition and no partition indexes

  Hello
  
  I have the partition table that contains about 1 ml recods and he have daily score.
  This partition table have only a unique index that is a partition No.
  
  CREATE UNIQUE INDEX xxxxxx WE yyyyyy
  (ITEM_GUID, IMAGE_SIDE)
  LOGGING
  TABLESPACE zzzzzz
  PCTFREE 10
  INITRANS 2
  MAXTRANS 255
  STORAGE)
  INITIAL 170M
  ACCORDING TO 1 M
  MINEXTENTS 1
  MAXEXTENTS 2147483645
  PCTINCREASE 0
  DEFAULT USER_TABLES
  )
  NOPARALLEL;
  
  I drop very first partition of
  
  Fall of ALTER TABLE wwww.yyyyy SCORE PT_20080706;
  
  But this isn't my unique INVALID index.
  
  Is it normal to have a VALID unique index after the fall of any partition?
  
  Do I have to rebuild a unique index again?
  
  DB: oracle 10.2.0.3
  platform: solaris
  
  Thanks in advance

  According to the Oracle doc, if you drop the bulkhead with an overall index,.

  All index global, or all partitions of global partitioned indexes are marked UNUSABLE unless one of the following are true:

  You specify the UPDATE INDEX (cannot be specified for tables organized by index. Use GLOBAL updating INDEXES.)

  The dropped partition or its subparts are empty

  more info here
  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14231/partiti.htm#sthref2751

  Check ALL_PART_INDEXES and ALL_INDEXES to check the State of your indexes.