Partitioning of an existing partitioned table

Similar Questions

• Creating a partitioned table to an existing table interval.

  Hello

  Is there a way I can create a partitioned table interval of an existing table using DEC? I know how to create a partitioned table in range.

  create the table range_partitioned_table

  partition by range (date_column)

  (

  partition p1 lower ((to_date (' 08/01/2012 ',' mm/dd/yyyy'))),

  lower partition p2 values (to_date (' 09/01/2012 ',' mm/dd/yyyy')),

  PN VALUES LESS THAN (MAXVALUE) PARTITION

  )

  AS SELECT * from existing_table;

  Is there a similar way to the Interval partition an existing table?

  create the table interval_partitioned_table

  partition by range (date_column)

  interval (provide the interval)

  (

  partition p1 lower ((to_date (' 08/01/2012 ',' mm/dd/yyyy'))),

  partition p2 values less (to_date (' 09/01/2012 ',' mm/dd/yyyy')),

  -PN SCORE VALUES LESS THAN (MAXVALUE)

  )

  AS SELECT * from existing_table;

  For example:

  SQL > create table interval_partitioned_table
  2 partition by range (hiredate)
  interval of 3 (numtoyminterval(1,'YEAR'))
  (4)
  5 score below p1 ((to_date (' 08/01/2012 ',' mm/dd/yyyy'))),
  6 partition p2 values less (to_date (' 09/01/2012 ',' mm/dd/yyyy')),
  7 - PARTITION pN VALUES LESS THAN (MAXVALUE)
  8)
  9 AS SELECT * FROM emp;

  Table created.

  SQL >

  SY.

• modifies an existing large partitioned table to automatically add the partitions

  Hello world
  
  According to me, it is not possible to modify an existing large partitioned table, to add partitions automatically as you insert it into this one. What would be the best way to do this? Dbms_redefinition? DEC + copy dependant rename?
  
  Any ideas?
  
  Thank you.
  
  current version:
  Oracle Database 11 g Enterprise Edition Release 11.2.0.3.0 - 64 bit Production
  With partitioning, Real Application Clusters, Automatic Storage Management, OLAP,.
  Options of Data Mining and Real Application Testing

  >
  According to me, it is not possible to modify an existing large partitioned table, to add partitions automatically as you insert it into this one. What would be the best way to do this? Dbms_redefinition? DEC + copy dependant rename?

  Any ideas?
  . . .
  I guess what I'm looking for is
  ALTER TABLE XXX INTERVAL DEFINED (NUMTOYMINTERVAL(1,'MONTH'));

  The following problem, I see is my required interval varies 01 hours of daylight at the time month 01 day 01 01 of the following month.
  >
  The best way to do it is to change your way of thinking.

  Do not be afraid to break the Oracle actually trying things. Just ALTER the table.

  drop table part_test cascade constraints;
  
  create table part_test(id number, entry_date date)
  partition by range (entry_date)
  (
  partition old_years values less than (to_date('01/01/2013 01:00:00', 'mm/dd/yyyy hh24:mi:ss')),
  partition jan_2013 values less than (to_date('02/01/2013 01:00:00', 'mm/dd/yyyy hh24:mi:ss'))
  )
  
  insert into part_test values(1, to_date('01/01/2013 00:00:00', 'mm/dd/yyyy hh24:mi:ss'));
  
  insert into part_test values(2, to_date('01/01/2013 02:00:00', 'mm/dd/yyyy hh24:mi:ss'));
  
  alter table part_test set interval(numtoyminterval(1,'MONTH')); 
  
  insert into part_test values(2, to_date('02/01/2013 02:00:00', 'mm/dd/yyyy hh24:mi:ss'));
  
  SQL> set serveroutput on
  SQL> select partition_name, high_value
    2  from dba_tab_partitions
    3  where table_name = 'PART_TEST';
  
  PARTITION_NAME
  ------------------------------
  HIGH_VALUE
  --------------------------------------------------------------------------------
  
  OLD_YEARS
  TO_DATE(' 2013-01-01 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIA
  
  JAN_2013
  TO_DATE(' 2013-02-01 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIA
  
  SYS_P225
  TO_DATE(' 2013-03-01 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIA
  
  SQL>
  

  Note the limit of the score for SYS_P225 that was created? It includes the same ' time 1' of the highest range partition that existed before the ALTAR.

• Create no partition Table partitioning

  Dear all,

  I have a table that is not partition, and it has about 20 G data... If I want that table with say DATE_M partition column

  Please can anyone suggest the best way to do it.

  Thank you

  To create a partitioned table

  (1) you must make a backup of the existing one you can take expdp or DEC

  (2) remove the table and create the same table now with partitions (a minimum score is required)

  you want a range of ex-based partition if you use a date column

  (3) loading data from the previous table into the new partitioned table, either by DEC or impdp, the inserts will be automatically in their respective partitions and you don't mention explicitly.

  Their is no other possible way to partition a non partitioned table, you can do than workarounds to minimize the downtime of the table trying different ways to load data into the partitioned table.

  You can use the enable row movement clause of create table and also use local indexes for easy maintenance partition.

• Order by in a partitioned table

  Hi all

  I recently list partitioned table. After the partition, the existing query result was completely different from that of a non-partitioned table.

  CREATE TABLE 'BALANCE_TMP '.

  ("BRANCHID" VARCHAR2 (10 CHAR) NOT NULL,)

  VARCHAR2 (1 CHAR) 'ACCOUNTTYPE' NOT NULL,

  VARCHAR2 (20 CHAR) 'ACCOUNTID' NOT NULL,

  "BUSINESSDATE" DATE NOT NULL,

  'BALANCETYPE' VARCHAR2 (1 CHAR) NOT NULL,

  ("BALANCE" NUMBER (18.3) NOT NULL)

  LIST PARTITION (BRANCHID)

  (

  PARTITION bal_100 VALUES ("100")

  PARTITION bal_101 VALUES ('101')

  PARTITION bal_102 VALUES ('102')

  );

  The query:

  SELECT * OF balance b WHERE ROWNUM < = 1 AND BranchID = '100' AND

  AccountType = 'N' AND AccountID = "100999999613USD" AND BusinessDate <= May 12, 2014 ' AND

  BalanceType = 'A' ORDER BY BusinessDate DESC

  "The account has dates of business March 12, 2003 '-may 12, 2014. The SQL above on partitioned table gives me the folder that has the date of the company March 12, 2013 "and when partitioned may 12, 2014".

  Please let me know what I'm missing here. I'm assuming that partitioning atleast, in this case, is transparent to the SQL code.

  1543042 wrote:

  The same SQL on a non-partitioned table gives me the results expected is the last album of businessdate. On the partitioned table version, it gives me a record earlier.

  I believe you. Most likely date column is indexed. Optimizer decides to use the SORTED INDEX RANGE SCAN and first rank is rank of more recent date. That's why you get the desired result. But it's only because you're lucky optimizer chose a plan where the last line is read first. It is a time bomb which had sooner or later go off.  And that's exactly what happened with the partitioned table. Optimizer realized account of the table is partitioned and probably the use parallel execution plan. Now you have several slave process every single partition handling and using the INDEX RANGE SCAN SORTED for that. So each slave will get the last row in a respective score but then master process will choose one of them when applying ROWNUM<= 1="" and="" here="" you="" are="" at="" the="" mercy="" of="" which="" row="" will="" it="" be.="" and,="" as="" you="" already="" know,="" you="" didn't="">

  SY.

• Conversion of non partitioned in partitioned table

  
  Hi gurus,

  I need to convert the partition table not in the partition.  More flexible way is to use the DBMS_REDEFINITION package for this.
  I do not have access to run this package, when I asked the EXECUTE permission for my dev
  CUSTOMER rejected suggestion that
  "DBMS_REDEFINITION is a method very slow migration that has never been used before here for these migrations.
  so I do not recommend using it as it can trigger bugs and unexpected side effects.

  
  is this true?

  What will be the alternative method, I can go away?

  Please suggest

  S

  I don't think DBMS_REDEFINITION has bugs.  However, you (and the client) should be familiar with the steps involved.

  Other that that, you will need to create a partitioned table and insert data to the existing table.  You can speed up integration through parallel direct-path insert.

  You will also need to build indexes on the new (partitioned) table.  Define constraints if necessary.  Run grants to other patterns, if necessary.

  Hemant K Collette

• Possible to Exchange temporary table with composite range-hash partitioned table?

  Hello

  Using oracle 11.2.0.3

  We want to clean up the data in some of our existing partitioned table.

  Afetr updates check spped that is too slow for us.

  Current table is partitioned the inetrval compoiste range-hash table.  Also it is compressed - enabled for compression of basis as well

  An interval of 1 month and 1 partition by month and 4 secondary partitions in the partition of ecah.

  You want to create tenp table with the data of celan and exchange the data in this table in the 'dirty' uisng existing partitions partition exchnage.

  Is this possible?

  The plan is

  1) create temporary table containing data for 1 partition (1 month worth of data)

  (2) clean the data here

  (3) create new temporary table with these specific data which compressed and discovered partitioned with 4 secondary partitions

  (4) table 3 for swap partition dirty using partition excahnge.

  Thaks

  I think that this can be done with a combination of Exchange and Split partition partitions. Prior to Oracle 11 g, only way of redefining tables online was DBMS_REDEFINITION package. Now, you can redefine the use of partitions for Exchange & Split. Check

  http://www.Oracle-base.com/articles/Misc/partitioning-an-existing-table-using-Exchange-partition.php

  Maintenance of Partitions

  Kind regards

• Try to convert the partitioned Table of interval in the range... Swap partition...

  Requirement:
  
  Interval of replacement partitioned Table by range partitioned Table
  

  DROP TABLE A;
  
  CREATE TABLE A
  (
     a              NUMBER,
     CreationDate   DATE
  )
  PARTITION BY RANGE (CreationDate)
     INTERVAL ( NUMTODSINTERVAL (30, 'DAY') )
     (PARTITION P_FIRST
         VALUES LESS THAN (TIMESTAMP ' 2001-01-01 00:00:00'));
  
  
  INSERT INTO A
       VALUES (1, SYSDATE);
  
  INSERT INTO A
       VALUES (1, SYSDATE - 30);
  
  INSERT INTO A
       VALUES (1, SYSDATE - 60);

  I need to change this partitioned Table apart to a partitioned range Table. I can do using the EXCHANGE PARTITION. Like if I use the classic method to create another table range partitioned, then:
  
  

  DROP TABLE A_Range
  CREATE TABLE A_Range
  (
  a NUMBER,
  CreationDate DATE
  )
  PARTITION BY RANGE (CreationDate)
     (partition MAX values less than (MAXVALUE));
  
  Insert  /*+ append */  into A_Range Select * from A; --This Step takes very very long..Trying to cut it short using Exchange Partition.

  Problems:
  
  I can't do
  

   ALTER TABLE A_Range
    EXCHANGE PARTITION MAX
    WITH TABLE A
    WITHOUT VALIDATION;
   

  ORA-14095: ALTER TABLE CHANGE requires a not partitioned table nonclustered
  This is because the tables are partitioned. So it does not allow me.
  
  If I instead:
  
  
  Create a table that is not partitioned for exchanging data by partition.
  

    Create Table A_Temp as Select * from A;
    
     ALTER TABLE A_Range
    EXCHANGE PARTITION MAX
    WITH TABLE A_TEMP
    WITHOUT VALIDATION;
     
    select count(*) from A_Range partition(MAX);
   

  -The problem is that all the data is in MAX Partition.
  Even after the creation of a large number of partitions by walls of separation, the data is still in MAX Partition only.
  
  So:
  
  -What we cannot replace a partitioned Table to the Table partitioned using the EXCHANGE PARTITION range interval. that is, we have to insert in...
  -We can do it, but I'm missing something here.
  -If all the data is in MAX Partition due to "WITHOUT VALIDATION", can say us be redistributed in the right type of range partitions.

  You must pre-create the partitions in a_range and then swap one for one for a tmp, and then to arange. With the help of your sample (thanks to proviing code, incidentally).

  SQL> CREATE TABLE A
    2  (
    3     a              NUMBER,
    4     CreationDate   DATE
    5  )
    6  PARTITION BY RANGE (CreationDate)
    7     INTERVAL ( NUMTODSINTERVAL (30, 'DAY') )
    8     (PARTITION P_FIRST
    9         VALUES LESS THAN (TIMESTAMP ' 2001-01-01 00:00:00'));
  
  Table created.
  
  SQL> INSERT INTO A VALUES (1, SYSDATE);
  
  1 row created.
  
  SQL> INSERT INTO A VALUES (1, SYSDATE - 30);
  
  1 row created.
  
  SQL> INSERT INTO A VALUES (1, SYSDATE - 60);
  
  1 row created.
  
  SQL> commit;
  
  Commit complete.
  

  You can find the form of existing partitions assistance:

  SQL> select table_name, partition_name, high_value
    2  from user_tab_partitions
    3  where table_name = 'A';
  
  TABLE_NAME PARTITION_NAME HIGH_VALUE
  ---------- -------------- --------------------------------------------------------------------------------
  A          P_FIRST        TO_DATE(' 2001-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIA
  A          SYS_P44        TO_DATE(' 2013-01-28 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIA
  A          SYS_P45        TO_DATE(' 2012-12-29 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIA
  A          SYS_P46        TO_DATE(' 2012-11-29 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIA
  

  You can then create the table a_range with apporopriate partitions. Note that you may need to create additional in a_range partitions because the partitioning interval does not create the partitions has no data for, even if that leaves 'holes' in the partitioning scheme. So, on that basis:

  SQL> CREATE TABLE A_Range (
    2     a NUMBER,
    3     CreationDate DATE)
    4  PARTITION BY RANGE (CreationDate)
    5     (partition Nov_2012 values less than (to_date('30-nov-2012', 'dd-mon-yyyy')),
    6      partition Dec_2012 values less than (to_date('31-dec-2012', 'dd-mon-yyyy')),
    7      partition Jan_2013 values less than (to_date('31-jan-2013', 'dd-mon-yyyy')),
    8      partition MAX values less than (MAXVALUE));
  
  Table created.
  

  Now, create a regular table to use in the constituencies:

  SQL> CREATE TABLE A_tmp (
    2     a              NUMBER,
    3     CreationDate   DATE);
  
  Table created.
  

  and all partitions in Exchange:

  SQL> ALTER TABLE A
    2    EXCHANGE PARTITION sys_p44
    3    WITH TABLE A_tmp;
  
  Table altered.
  
  SQL> ALTER TABLE A_Range
    2    EXCHANGE PARTITION jan_2013
    3    WITH TABLE A_tmp;
  
  Table altered.
  
  SQL> ALTER TABLE A
    2    EXCHANGE PARTITION sys_p45
    3    WITH TABLE A_tmp;
  
  Table altered.
  
  SQL> ALTER TABLE A_Range
    2    EXCHANGE PARTITION dec_2012
    3    WITH TABLE A_tmp;
  
  Table altered.
  
  SQL> ALTER TABLE A
    2    EXCHANGE PARTITION sys_p46
    3    WITH TABLE A_tmp;
  
  Table altered.
  
  SQL> ALTER TABLE A_Range
    2    EXCHANGE PARTITION nov_2012
    3    WITH TABLE A_tmp;
  
  Table altered.
  
  SQL> select * from a;
  
  no rows selected
  
  SQL> select * from a_range;
  
           A CREATIOND
  ---------- ---------
           1 23-NOV-12
           1 23-DEC-12
           1 22-JAN-13
  

  John

• Create index partition in the partition table tablespace

  Hello
  
  I am running a work custom that
  
  * Creates a tablespace by day
  * Creates the daily table partition in the created tablespace
  * Removes the days tablepartition X
  * Removes the storage space for this partition of X + 1 day.
  
  The work above works perfectly, but it has problems with the management of the index for these partitioned tables. In the old database (10g - single node), all indexes and partitions exist in a BIG tablespace and when I imported the table creation script in the new database, I changed all the partitions table & index to go in their respective space.
  
  For example:
  
  Table_name... Nom_partition... Index_Part_name... Tablespace_name
  ============...================............====================...........=================
  TABL1... TABL1_2012_07_16... TABL1_IDX_2012_07_16... TBS_2012_07_16
  TABL1... TABL1_2012_07_15... TABL1_IDX_2012_07_15... TBS_2012_07_15
  
  
  But now, when the job is run, it creates the index in the tablespace TBS_DATA default.
  
  Table_name... Nom_partition... Index_Part_name... Tablespace_name
  ============...================.............====================...........=================
  TABL1... TABL1_2012_08_16... TABL1_IDX_2012_08_16... TBS_DATA
  TABL1... TABL1_2012_08_15... TABL1_IDX_2012_08_15... TBS_DATA
  
  
  I can issue alter index rebuild to move the index to its tablespace default, but how can I make sure that the index is created in the designated tablespace?
  
  NOTE: the partition/tablespace management work that I run only creates the partition of the table and not the index.
  
  
  The new env is a cluster of CARS of 2 nodes 11 GR 2 on Linux x86_64.
  
  
  Thanks in advance,
  aBBy.

  try something like this

  ALTER table tab_owner.tab_name add the partition v_new_part_nm
  values less (to_date('''|| v_new_part_dt_formatted ||'') ((', "DD-MON-YYYY)) tablespace ' | part_tbs
  update the index (ind1_name (partition ind_partition_name tablespace ind_part_tbs)
  ind2_name (partition tablespace ind_part_tbs ind_partition_name))
  ;

• Adding Partition for a partitioned Table

  Hello
  I have a partitioned table with 7 existing Partitions that follow this structure:
  
  PARTITION 'TRANSACTIONS_JAN2012' VALUES (TO_DATE () LOWER
  "2012-02-01 00:00:00 ', ' SYYYY-MM-JJ HH24:MI:SS»(, ' NLS_CALENDAR = GRÉGORIEN ')"
  ) PCTFREE, PCTUSED 10 0 INITRANS 1 MAXTRANS 255 NOLOGGING (INITIAL STORAGE
  1073741824 THEN 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0
  FREELISTS 1 FREELIST GROUPS 1 USER_TABLES DEFAULT FLASH_CACHE
  DEFAULT CELL_FLASH_CACHE) TABLESPACE "FTSV1" NOCOMPRESS
  
  I am trying to add a new Partition:
  ALTER table movements Add partition
  (partition TRANSACTIONS_JTS VALUES LESS THAN (TO_DATE (' 2012-03-01 00:00:00 ',' SYYYY-MM-DD HH24:MI:SS ',' NLS_CALENDAR = GREGORIAN ')));
  
  But get this error:
  SQL error: ORA-00902: invalid data type
  00902 00000 - "invalid data type".
  
  Any help is greatly appreciated.
  
  Thanks in advance,
  Johnny

  Hi Johnny,.

  Looks like you have one to several "Partition", delete this as well as the unnecessary parentheses.

  ALTER TABLE transactions
      ADD PARTITION transactions_jts
      VALUES LESS THAN
          (TO_DATE(' 2012-03-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'));
  

  Concerning
  Peter

• Migration to a new transportable tablespace partition table

  I created a table that is partitioned with 2 partitions (2010 & 2011) and transportable tablespace to migrate data to a new envionment. My question is, if I decide to add a partition (2012) in the future, can I simply move as new portable partition as well as the associated through tablespace data file or I have to spend all the partitions (2010, 2011, 2012).

  user564785 wrote:
  I created a table that is partitioned with 2 partitions (2010 & 2011) and transportable tablespace to migrate data to a new envionment. My question is, if I decide to add a partition (2012) in the future, can I simply move as new portable partition as well as the associated through tablespace data file or I have to spend all the partitions (2010, 2011, 2012).

  Yes, why not.
  (1) create a table like new Tablespace on source 2012 DEC
  (2) transport the tablespace
  (3) add the existing partition table partition or swap partition

  Oracle has also documented this procedure:
  http://docs.Oracle.com/CD/B28359_01/server.111/b28310/tspaces013.htm#i1007549

• How to find the partitioned tables and the number of sheets in each table

  Hello friends,
  
  I have a scheme called ICS_OWNER where I partitioned and tables not partitoined.
  
  I want to list all the tables that are partitioned.
  
  and also
  
  I want to know what partitions exists in every partitioned table.
  
  with respective schema specified
  
  Thank you/Kumar

  When you have questions like this, you don't ask here.
  but you take your (or should I say 'your') keyboard
  and type
  Select *.
  dict
  where table_name like ' % PART %.
  /

  All the dictionary views are listed in the DICT.

  ----------
  Sybrand Bakker
  Senior Oracle DBA

• I need to change the column of the range on my partition table

  Hello
  
  I created a partition table, but I need to change column of the range "CREATED" to "PREPARED". Two of them date format, but I can't modify this table.
  
  PARTITION OF RANGE (CREATED)--> I need to change column "CREATED" as "PREPARED".
  (
  INV08 PARTITION VALUES LESS (TO_DATE('01-SEP-2010','DD-MON-YYYY')).
  INV09 PARTITION VALUES LESS (TO_DATE('01-OCT-2010','DD-MON-YYYY')).
  INV10 PARTITION VALUES LESS (TO_DATE('01-NOV-2010','DD-MON-YYYY')).
  PARTITION INV VALUES LESS THAN (MAXVALUE)
  )
  
  How can I do?
  
  Published by: user567352 on December 23, 2010 04:10

  Hello

  As far as I know, dbms_redefinition didn't even know about the partitioning:

  1. you create a new empty table that matches your need + (that is where you defined you new partition key) +.
  2. you start the names of submiting of redefinition of existing and newly created table 'interim' table
  3. you leave enough time to get the work done
  4. you have finished redefining (the name of the table are swapped)
  And voila!

  Be sure to test thorougly the process of redefinition and the performance impact that may occur until you make it to your production !
  ;-)

• Adding a new partition to a partitioned table

  Hi all
  
  I try to add a new partition to an existing table in compartmentalized but I need the new partition of 'table' to go to tablespace DATA_2011 and partition "index" to go to INDEX_2011. I tried but it wrong on what follows.
  
  CREATE TABLE employees
  (employee_id number 4 NOT NULL,
  last_name VARCHAR2 (10),
  department_id NUMBER (2))
  PARTITION OF RANGE (department_id)
  (PARTITION employees_part1 VALUES LESS THAN (11) TABLESPACE DATA_2010,)
  PARTITION employees_part2 VALUES LESS THAN (21) TABLESPACE DATA_2010;
  PARTITION employees_part3 VALUES LESS THAN (31) TABLESPACE DATA_2010);
  
  CREATE INDEX employees_local_idx ON employees (employee_id) LOCAL
  (PARTITION TABLESPACE INDEX_2010 employees_part1,
  PARTITION employees_part2 TABLESPACE INDEX_2010,
  PARTITION employees_part3 TABLESPACE INDEX_2010);
  
  
  Here's what I'm trying to run but it fails...
  ALTER table employees add PARTITION "EMPLOYEES_PART4" VALUES LESS THAN (41) DATA_2011 index tablespace tablespace INDEX_2011;
  
  ERROR on line 1:
  ORA-14020: this physical attribute may not be specified for the partition table
  
  
  
  Succeeds what follows, but in this case the index partition "EMPLOYEES_PART4" is also assigned to DATA_2011 tablespace.
  
  ALTER table employees add PARTITION "EMPLOYEES_PART4" VALUES LESS THAN (41) tablespace DATA_2011;
  
  
  Any ideas... I am currently looking in the documentation to see if it would be possible?
  
  Thanks for your time...

  Hello

  ALTER table employees add PARTITION "EMPLOYEES_PART4" VALUES LESS THAN (41) tablespace DATA_2011;

  The foregoing is the corect order and therefore succeeded.

  but in this case the index partition "EMPLOYEES_PART4" is also assigned to DATA_2011 tablespace.

  You need rebuild the index of the partition with the name desired tablespace. /

  ALTER index rebuild partition tablespace

  Anand

• importing into a partitioned table of interval 11g

  as I took export utility simple partition table 8i exp not rained so 100 k lines in there.
  
  and imported with the import utility in the interval of 11g partitioned based on the date column.
  
  There were imported, but did not what I expected...
  
  If we execute the simple insert for partition interval 11g command, it create new partition automatically according to the strategy of partition.
  
  Here's the demo...
  
  created range partitioned table on the date with shift interval column...
  
  CREATE TABLE TEST.xxx_HIST
  (
  xxx_DATE DATE NOT NULL,
  P_ROLL_CONVENTION CHAR (2),
  R_ROLL_CONVENTION CHAR (2),
  P_COMPOUNDING_IND CHAR (2),
  R_COMPOUNDING_IND CHAR (2),
  P_CALC_METHOD CHAR (2),
  R_CALC_METHOD CHAR (2),
  P_SPREAD_AMT NUMBER (28,12).
  R_SPREAD_AMT NUMBER (28,12).
  
  )
  partition by range (xxx_DATE)
  interval (numtoyminterval(3,'MONTH'))
  store (security)
  (
  values of pQ1 lower partition (to_date('2010-01-01','yyyy-mm-dd'))
  ) IN PARALLEL.
  
  
  -IMPORTED FROM ROWS IN THE TABLE...
  
  ======================================================================
  Connected to: Oracle Database 11 g Enterprise Edition Release 11.1.0.7.0 - 64 bit Production
  With partitioning, OLAP, Data Mining and Real Application Testing options
  
  Export file created by EXPORT: V08.01.07 direct
  
  CAUTION: objects have been exported by SYSTEM, not by you
  
  . import of xx_ARCH in TEST objects
  . . import of 141749 lines imported from the table 'xxx_HIST '.
  Import completed successfully without warnings.
  ========================================================================
  
  
  
  -HE HAS A LOT OF DATES OF DIFF IN THERE...
  
  
  
  SQL > SELECT COUNT (DISTINCT xxx_DATE) TEST.xxx_HIST;
  
  COUNT (DISTINCT xxx_DATE)
  -----------------------------
  1371
  
  
  28-MARCH 06
  10 FEBRUARY 06
  9 FEBRUARY 05
  20 FEBRUARY 02
  3 JUNE 02
  10 MAY 04
  26 DECEMBER 03
  31 JANUARY 03
  
  xxx
  ---------
  21 JULY 08
  31 OCTOBER 05
  25 APRIL 08
  28 APRIL 08
  12 OCTOBER 06
  DECEMBER 21 07
  28 DECEMBER 04
  
  
  -BUT STILL ALL DUMPED INTO A PARTITION
  
  
  SQL > SELECT nom_partition FROM DBA_TAB_PARTITIONS WHERE TABLE_OWNER = 'TEST ';
  
  NOM_PARTITION
  ------------------------------
  PQ1
  
  It all dumped in a partition...
  
  fact partition interval 11g creates the partition automatically in function whose lines if imported... when we import lines in there...? or am I missing something?
  
  any idea guys?

  Seems to be a poor strategy for me because if I am not mistaken, there is no way to specify the order of the imported lines. If you import a line with the date max as your first row... bang, you get a range partition created for you and the rest falling.

  I think you'd be better import these data into a table in step and then by a

  insert into new_fancy_partition_table
  select *
  from old_8_temporary_imported_table
  order by date_column asc
  

  Or create the partitions manually.

  I just realized that you specify a partition in your create table statement (missed that on cursory inspection). And I think you misunderstand how the interval works... it's for values LARGER than the existing partitions ONLY...

  http://download.Oracle.com/docs/CD/E11882_01/server.112/e10592/statements_7002.htm#SQLRF01402

  "
  INTERVAL clause

  Use this clause to set the interval of partitioning the table. Range partitions are partitions based on a digital range interval or datetime. * They extend from range partitioning by commanding the database to automatically create partitions of the specified range or interval when the data inserted in the table exceed all the partitions.* range
  "

  Published by: Tubby on August 16, 2010 18:32

  Additional document link.