Partition key would exist in local index, if so it should be first or last or is not serious?

Similar Questions

• Global and local index with respect to table partitioned

  Hello
  I am very confused about local and global index in a partitioned table.
  In addition, local index can be partitioned and unpartitioned.
  In addition, what is the difference between global partitioned and unpartitioned
  the index?
  
  As far as I know,
  If there is local index then there will be as many partitions as the partition table
  and local parition will index contains the index of only the lines of their corresponding scores.
  In addition, the local index maintananence is easier because drop us or create a partition, only index corresponding partition is affected then that in the case of the overall index,
  If we create a new partition of the table, to rebuild the global index.
  Am I wrong?
  
  Concerning

  Hello

  This means that when you add/drop/split/merge table any partition (maintaiance) lying below, its corresponding partition in index is automatically added/deleted/split/merged. Oracle takes care of it internally without user intervention.

  Concerning
  Anurag

• Local index: prefix or no prefix

  Hello
  
  I understand that in order to effectively use the local index, WHERE the sql clause must have the partition column
  as a predicate.
  
  in general, the partition column will not be a very selective specific column to the individual partition (even at the level of the table).
  
  in which case, with the local index prefix (where the partition column will be the leading index) will benefit?
  in my case, I partitioned tables list with 2 partitions, 1) 2) obsolete current.
  
  Thank you
  Charles

  Uwe Hesse wrote:

  Uwe,

  In short: If you manage to include the partition key of the table to your where condition, size of the partition to the level of the index for the index is possible. But maybe it's not always possible.

  But if the where clause does not contain the partition key, then you need to visit each partition of the index (and, possibly, table) anyway - and the index cannot be used for high precision range scans because it begins with a column that is not in the where clause (you might get lucky with skip scans However).

  There are four conditions to study once you have chosen a possible local index and think that you are supposed to decide whether or not the index should include:

  When the clause includes partition key, index is not prefixed (even to the extent where the partition key is not part of the index)
  Partition elimination can occur

  When the clause includes partition key, the index is prefixed
  Partition elimination can occur

  When the clause does not partition key, index is not prefixed (even to the extent where the partition key is not part of the index)
  Partition elimination cannot take place-, but the index could still be very accurate and very effective

  When the clause does not partition key, the index is prefixed
  Partition elimination cannot take place, and the index cannot be used by a jump search or complete analysis because it begins with a column that is not the case clause.

  The first pair of options shows that there is no inherent advantage to the addition of the prefix, the second pair shows that there is a potential threat.

  Since something like 8.1.6 the only factors including the key partitioning in all indexes them are that the standard ones - how does improve accuracy, where - in the index, the column order - is this is a most useful position. The concept of all prefix/non-prefixe has been buried years ago.

  Concerning
  Jonathan Lewis

• I would like to change the name in my profile my name and my company name, so when my clients receive a signature on the Forms application, my company name is displayed in the email as opposed to my first and last name. How can I change

  I would like to change the name in my profile my name and my company name, so when my clients receive a signature on the Forms application, my company name is displayed in the email as opposed to my first and last name. How can I change this? I tried to edit my profile however my first and last name are not editable fields.

  Hello Laurag92400722,

  You connect with Adobe ID account E-Sign? If Yes, then you can directly connect to your Adobe ID account and can update the name as the name of the company and it will reflect in your E-Sign account as well.

  -Usman

• What happens to the existing after the partition of table index and created with local index

  Hi guys,.

  / / DESC part id name number, varchar2 (100), number of wage

  In an existing table PART I add 1 column DATASEQ MORE. I wonder the part of table based on dataseq.now, the table is created with this logic of partition

  create the part table partition (identification number, name varchar2 (100), number of salary, number DATASEQ) in list (dataseq) (values partition PART_INITIAL (1));

  Suggestionn necessary. given that the table is partitioned based on DATASEQ I wonder to add local indexes on dataseq. to dataseq, I have added a local index create index idx on share (dataseq) LOCAL; Now my question is, already, there are the existing index is the column ID and salary.

  (1) IDX for dataseq is created locally so that it will be partition on each partition on the main table. Please tell me what is happening to the index on the column ID and salary... it will create again in local?

  Please suggest

  S

  Hello

  first of all, in reality 'a partition table' means create a new table a migration of existing data it (although, theoretically, you can use dbms_redefinition to partition an existing table - however, it's just doing the same thing behind the scenes). This means that you also get to decide what to do with the index - index will be local, who will be global (you can also reassess some of existing indexes and decide that they are not really necessary).

  Second of all, the choice of the partitioning key seems weird. Partitioning is a data management technique more that anything else, in order to be eligible, you must find a good partitioning key. A column recently added, named "data_seq" is not a good candidate. Can you give us more details about this column and why it was chosen as a partitioning key?

  I suspect that the person who proposed this partitioning scheme made a huge mistake. A non-partitioned table is much better in all aspects (including the ease of management and performance) that divided one wrongly.

  Best regards

  Nikolai

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

• 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/

• Index BITMAP Advisor Advisor access SQL on the Partition key

  I ran SQL and SQL Access Advisor as below he recommends index bitmap on p_key... Given that the cust table is partitioned on the p_key, does make sense to create indexes on p_key?
  
  Not sure if SQL Access Advisor look just in ' where clause conditions/predicates "and the cardinality of such columns and not look at whether the table is partitioned or not. T it?
  
  Is it wise to create BITMAP indexes on the partition key? If so what scenario would be beneficial?
  

  SELECT * FROM cust
  WHERE 
      'T' = 'T' AND 
      part_key IN 
      (   2, 3, 4 )) AND 
      (   p_key, act_key) IN ( select p_key, act_key from account where act_type = 'PENDING' and p_key in (2,3,4) )

  user4529833 wrote:
  Jonathan, I have exactly one value per partition for the partition key.   However, most SQLs use 'IN' as predicate of partitioning pruning so overall stats are always used and they are always a bit bland compared to the partition level stats. Then this led SQL Access advisor recommendations?

  Yes, the Counselor also recommended to create Bitmap indexes on act_type... Given this does make sense to have the Bitmap index on the partition key?

  I'll post the execution plan as soon as I have access to the system...

  The fact that statistics are "a little stale" was not much of a difference.

  The fact that Oracle has probably used statistics at the level of the tables is likely to be the underlying issue. Is the partitioned table list or you have rigged it with partitioning range: If you faked list partitioning using partitioning of the range which MAY have contributed to the issue (but it's an assumption that I have not tested).

  Unofficially, the optimizer has said something like:

  + "There are 25 possible values for pkey, there are 4 possible values for act_type, there seems to be 100 different combinations - so your query will pick up X lines. 80% of these lines will be packed in Y blocks and 20% of them will be scattered through the Z blocks if we have two bitmap index, and we will have to do sequential reading of the db file SSS. If we do an analysis through the affected partitions, we do MMM db file scattered reads. What are those cheaper. » +

  You know how false it's - if you know that you need not the pkey index. You also know what is the efficiency of the column act_type is in the identification of data, so you can decide whether or not an index on act_key may be useful.

  Concerning
  Jonathan Lewis
  http://jonathanlewis.WordPress.com
  http://www.jlcomp.demon.co.UK

  "The premature temptation to theories of shape on the lack of data is the scourge of our profession."
  Sherlock Holmes (Sir Arthur Conan Doyle) in "the Valley of fear."

• Remove the local index partitions

  Hello

  How can I provide clues the only from a few partitions in oracle 10.2.0.4?

  Index partitions a fall

  You cannot explicitly delete a partition of a local index. Instead, the local index partitions are removed only when you delete a partition of the underlying table.

  http://docs.Oracle.com/CD/E18283_01/server.112/e16541/part_admin002.htm#i1007542

• Rebuild the range-Hash partitioned local index

  Hi all
  
  We have a table with 400 million records in our dataware House environment. It is partitioned using range-Hash Partitioning composit. He used a global Indexes previously. Last month the global indices have been changed to the index the. Since then, Exchange and index rebuild partition takes twice against the take used previously. From my understanding local index should provide availability high and more usable in the warehouse environment. Please correct me if I'm wrong and give me your suggestion. Also, I'm looking for a good material for the exchange of the partition and Index rebild with locally manage the range-hash partitioned index. Let me know if you know a good link for this...
  
  
  Thanks in advance...

  Dear krmreddy,

  Carefully read the following link and I hope this will guide you;

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

  Kind regards.

  Ogan

• What is the index that is created automatically on the partitioning key?

  What is the index that is created automatically on the partitioning key?

  CREATE TABLE sales
  ( prod_id NUMBER(6)
  , cust_id NUMBER
  , time_id DATE
  , channel_id CHAR(1)
  , promo_id NUMBER(6)
  , quantity_sold NUMBER(3)
  , amount_sold NUMBER(10,2)
  )
  STORAGE (INITIAL 100K NEXT 50K) LOGGING
  PARTITION BY RANGE (time_id)
  ( PARTITION sales_q1_2006 VALUES LESS THAN (TO_DATE('01-APR-2006','dd-MON-yyyy'))
  TABLESPACE tsa STORAGE (INITIAL 20K NEXT 10K)
  , PARTITION sales_q2_2006 VALUES LESS THAN (TO_DATE('01-JUL-2006','dd-MON-yyyy'))
  TABLESPACE tsb
  , PARTITION sales_q3_2006 VALUES LESS THAN (TO_DATE('01-OCT-2006','dd-MON-yyyy'))
  TABLESPACE tsc
  , PARTITION sales_q4_2006 VALUES LESS THAN (TO_DATE('01-JAN-2007','dd-MON-yyyy'))
  TABLESPACE tsd
  )
  ENABLE ROW MOVEMENT;

  N ° you must create indexes for yourself.

• How add us partition on an existing table?

  Hi gurus,

  What would be the best way to add a partition to an existing table?

  Is there a simple documentation for example?

  Thank you

  What would be the best way to add a partition to an existing table?

  Is there a simple documentation for example?

  Was it something you were ask in an interview?

  You cannot add a partition to a table unless this table is a partitioned table.

  The table is already partitioned? If so, after the DDL.

  The Oracle documentation has examples of adding partitions to a table that is already partitioned

  Partition management

  Adding Partitions

  This section explains how to manually add partitions of a partitioned table and explains why partitions can be added specifically for partitioned more indexes.

  Adding a Partition to a partitioned Table range

  Use of the ALTER TABLE ... ADD PARTITION statement to add a new partition at the end 'high' (the point after the last existing partition). To add a partition at the beginning or in the middle of a table, use the SPLIT PARTITION clause.

• How to assign the tablespace name local index when converted to INTERVAL

  Hello
  I'm converting a range partition table in the table to partition INTERVAL. The storage space for the tables is GIVEN. After this operation, all the indexes the world and are valid and usable. However, when the next interval partition is created, the local index is also created in the tablespace DATA. How can I make sure that new partitions of the interval for the index will be created them within the existing Index table?
  
  Thank you
  Murali

  Change the index to specify the desired storage space, and new partitions will be created there.

  ALTER INDEX my_index MODIFY DEFAULT ATTRIBUTES TABLESPACE my_preferred_tablespace;
  

• Partitioning of an existing partitioned table

  Dear Experts,

  I have a problem with redefinition of partitioning of an existing partitioned table. I have a parent table separated by a virtual column by range:

  CREATE THE PARENT TABLE

  (

  PARENT_ID NUMBER NOT NULL,

  INSERT_TIMESTAMP TIMESTAMP (6) NOT NULL,

  CLOB PARENT_DATA NOT NULL,

  BATCH NUMBER,

  DATE of INSERT_DATE generated always as (TRUNC("INSERT_TIMESTAMP"))

  )

  LOB (PARENT_DATA) AS STORE NAVIGATION (ACTIVATE ONLINE STORAGE)

  PARTITION BY RANGE (INSERT_DATE)

  (

  P2015_11 PARTITION VALUES LESS THAN (TO_DATE (' 2015-12-01 00:00:00 ',' SYYYY-MM-DD HH24:MI:SS ',' NLS_CALENDAR = GREGORIAN '))

  CRAFT STORE (PARENT_DATA) AS (SECUREFILE

  ACTIVATE THE ONLINE STORAGE),

  P2015_12 PARTITION VALUES LESS THAN (TO_DATE (' 2016-01-01 00:00:00 ',' SYYYY-MM-DD HH24:MI:SS ',' NLS_CALENDAR = GREGORIAN '))

  CRAFT STORE (PARENT_DATA) AS (SECUREFILE

  ACTIVATE THE ONLINE STORAGE),

  P2016_01 PARTITION VALUES LESS THAN (TO_DATE (' 2016-02-01 00:00:00 ',' SYYYY-MM-DD HH24:MI:SS ',' NLS_CALENDAR = GREGORIAN '))

  CRAFT STORE (PARENT_DATA) AS (SECUREFILE

  ALLOW ONLINE STORAGE,

  PARTITION P_DEFAULT VALUES LESS THAN (MAXVALUE)

  CRAFT STORE (PARENT_DATA) AS (SECUREFILE

  ALLOW ONLINE STORAGE

  ))

  );

  and a child table partitioned by reference:

  CREATE ACCOUNTS FROM THE TABLE. CHILD

  (

  PARENT_ID NUMBER NOT NULL,

  DATAACC DATAACC_TBL,

  CREATION_DATE DATE,

  CONSTRAINT PARENT_D_E_PRT_FK

  FOREIGN KEY (PARENT_ID)

  (PARENT_ID) REFERENCES PARENT

  ENABLE VALIDATE

  )

  NESTED TABLE, STORE DATAACC AS DATAACC_NT

  PARTITION OF REFERENCE (PARENT_D_E_PRT_FK)

  (

  P2015_11 PARTITION,

  P2015_12 PARTITION,

  P2016_01 PARTITION,

  PARTITION P_DEFAULT);

  However, now in Oracle 12 c I am able to use the reference interval partitioning. How can I redefine the partitioning of the parent table so that there can be scope-level?

  Thank you for your help.

  Best regards, Atanas.

  To change range partition to partition interval, the table should not have MAXVALUE partition... Follow the steps below to convert to partition interval

  (1) check if all data of the MAXVALUE partition (p_default) using query below

  SELECT COUNT (*) FROM parent PARTITION (p_default).

  (2) if there is no trace in the p_default partition, drop the help below

  ALTER TABLE DROP PARTITION parent p_default;

  (3) use the clause SET INTERVAL to convert the range partition partition interval as below

  ALTER TABLE parent SET INTERVAL (NUMTOYMINTERVAL(1,'MONTH'));

  I guess, you have the range partition up to until, so there should not be any folder in p_default partition.

• How do I know it's global index or local index?

  Hi all
  
  How will I know if it's overall index or local index?
  
  Thank you!
  
  Dan.

  Salvation;

  Check defination of index? Overall index below has defination

  CREATE INDEX month_ix ON sales (sales_month)
  GLOBAL PARTITION BY RANGE (sales_month)

  For more information, please visit:

  http://download.Oracle.com/docs/CD/B13789_01/server.101/b10739/partiti.htm

  Respect of
  HELIOS