ASM and table partitioning

hi gurus,
i was told by a colleague table level partitioning is not required if ASM is in place, ASM can manage load balancing etc.
your expert opinion please..
thanks in advance,
charles

Hi Charles,
Table partition and ASM are two different things.
ASM can perform load balance and manage the disks, table partitions split table to several smaller segments.
Table partitions allow partition pruning and the ability to manage data in smaller portions (such as drop or truncate an entire partition etc.). This has nothing to do with ASM and is very important advantages, regardless your disk and storage management
HTH
Liron Amitzi
Senior DBA consultant
[www.dbsnaps.com]
[www.orbiumsoftware.com]

Similar Messages

  • Question about Global index and Table Partitions

    I have created a global index for a partitioned table now in the future the partitions will be dropped in the table. Do I need to do anything to the global index? Does it need to be rebuilt or would it be ok if partitions get dropped in the table?

    >
    I have created a global index for a partitioned table now in the future the partitions will be dropped in the table. Do I need to do anything to the global index? Does it need to be rebuilt or would it be ok if partitions get dropped in the table?
    >
    You can use the UPDATE INDEXES clause. That allows users to keep using the table and Oracle will keep the global indexes updated.
    Otherwise, as already stated all global indexes will be marked UNUSABLE.
    See 'Dropping Partitions' in the VLDB and Partitioning Guide
    http://docs.oracle.com/cd/E11882_01/server.112/e25523/part_admin002.htm#i1007479
    >
    If local indexes are defined for the table, then this statement also drops the matching partition or subpartitions from the local index. All global indexes, or all partitions of partitioned global indexes, are marked UNUSABLE unless either of the following is true:
    You specify UPDATE INDEXES (Cannot be specified for index-organized tables. Use UPDATE GLOBAL INDEXES instead.)
    The partition being dropped or its subpartitions are empty

  • Large data sets and table partitioning : removing data

    Hi,
    I have to delete lines into a big table using partition.
    Someone says me it is more efficient for the performances to drop a whole partition (or subpartition if I use a composite partition) than to delete a line at the same time.
    He says me that data access (in my partition) should be very bad if I delete lines progressively (in this partition) instead of keeping the lines and deleting the whole partition when all its lines are no more used.
    What do you think about it?
    Thanks
    Sandrine

    Hi Sandrine,
    I agree with what you're being told. I'll be much more efficient to "clone" the data you want to keep from your patition somewhere (clone table, ...) and then drop the whole partition.
    Main thing is if you drop an object there's no BEFORE IMAGE stored in your UNDO structures (UNDO TS / RBS). SO you'll have way less disk I/Os.
    Hope this helps ^^

  • Large data sets and table partitioning

    I have an Oracle 9i database and I need to store huge volume of data in a table,
    so I use a composite partitioning.
    Is there a maximum size for my table to keep performances (if it's possible, I would
    like to store several Terra (1000 Mega) of data)?
    I would like to know if somebody works on a similar project
    and which tools and environment it uses (server, OS, memory
    size..).
    Thanks for your help.

    Yes, users can update data.
    I don't join data.
    This is an OLTP system.
    To estimate the size of 5 Tb, I just use the number of inserts per day and how many days I keep data in the table and I have an average size of one line (taken on an existing first version table).
    I have another question on partitioning : someone says me it is more efficient to drop a whole partition (or subpartition if I use a composite partition) than to delete a line at the same time, for the performances.
    He says me that data access (in my partition) should be very bad if I delete lines progressively (in this partition) instead of keeping the lines and deleting the whole partition when all its lines are no more used.
    What do you think about it?
    Thanks
    Sandrine

  • How can we use the table partitions feature and.........

    Hai friends when i tried to use the bitmap indexes and table partitions feature ,
    I got a message like this
    'table partiotion feature not enabled'
    so please tell me how can i enable those features so that i will be able to use those features..........

    Partitioning and Bitmap Indexes are features of Oracle Enterprise addition. In fact, I think that Partitioning is an extra option that needs to purchased with Oracle Enterprise - it is not a default feature.
    These features do not exist on Oracle Standard Edition (and likely Express Edition too).

  • Index Vs table partition

    I have table whose growth is 1 million per month and may increase in future. I currently place an index on column which is frequently uses in where clause. there is another column which contains months so it may possible that I make 12 partitions of that. I want to know what is suitable. is there any connection between index and table partition?
    Message was edited by:
    user459835

    I think the question is more of what type of queries are answered by this table?
    is it that most of the times the results returned span across several months?
    is there any relation to the column you use in where clause with the data belonging to a particular month (or range there-of)?

  • What is the best way to dynamically create table partition by year and month based on a date column?

    Hi,
    I have a huge table and it will keep growing. I have a date column in this table and thought of partition the table by year and month. Can any you suggest better approach so that partition will create automatically for new data also along with the existing
    data? Nothing but automatically/dynamically partition should create along with file group and partition files.
    Thanks in advance!
    Palash 

    Also this one
    http://weblogs.sqlteam.com/dang/archive/2008/08/30/Sliding-Window-Table-Partitioning.aspx
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • Alter table partition based on date and status

    Hi!
    I have a strange scenario where in 100,000 to 500,000 records are created every day and records are to be maintained for 3 yrs. So to manage this table we have it partitioned based on date (so every day one new partition is created). And any partition older than 3 years are to be purged. But the catch is - the table has a 'Creation_date' and 'Close_date' parameter and as per my company's rule, I can only purge the 3 yr old data based on the 'Closed_date'. Basically we end up getting some entries with 'Close_date' that don't fall in the 3+ yr category and hence we just cannot purge the whole partition and reclaim the space.
    What would be the ideal way to partition this table to make easy maintenance!?
    eg -
    Table_1: Partition_03152006
    Col-1 Creation-date Col-2 Close-date
    AAAA 03/15/2006 BBBB 03/16/2006 I can drop this entry+
    XXXX 03/15/2006 YYYY 05/20/2006 I cannot drop this entry+
    So, I am left with non-empty partitions which I cannot purge completely. Right now, I am moving these remaining entries to another partition and purging them when they complete the 3+yr time period.
    Hope I could put in my query properly.
    NOTE: RDBMS - ORACLE 10.2.0.4 on Solaris/SPARC 64Bit
    Thanks in advance,
    Arindam
    Edited by: AB007 on Jun 19, 2009 1:15 PM

    Hi! Below is the table description and the first 5 entries of the table.
    Hi,
    Thanks for your help. Below is the table structure with the index associated with it -
    CREATE TABLE "T3TKTHEADER"
    ( "TKTNUM" VARCHAR2(13) NOT NULL ENABLE,
    "ALTTKTNUM" VARCHAR2(20),
    "CREATEDTTM" DATE,
    "CREATEUSERID" NUMBER,
    "CREATEWKGRPID" NUMBER,
    "MASTERTKTNUM" VARCHAR2(13),
    "CUSID" VARCHAR2(15),
    "CUSNAME" VARCHAR2(80),
    "CUSCNCTNAME" VARCHAR2(80),
    "CUSCNCTPHN" VARCHAR2(22),
    "ALTCUSCNCTNAME" VARCHAR2(80),
    "ALTCUSCNCTPHN" VARCHAR2(22),
    "PRTY" VARCHAR2(1),
    "SVRITY" VARCHAR2(10),
    "CURACTSEQNUM" NUMBER(*,0),
    "LASTSTASTSCHANGETM" DATE,
    "ACKNOWLEDGEFLAG" VARCHAR2(1),
    "TMGRP" NUMBER,
    "TOPGRP" NUMBER,
    "TMUSER" NUMBER,
    "TOPUSER" NUMBER,
    "RECENTTKTSCOUNT" NUMBER,
    "PRINEID" VARCHAR2(53),
    "PRINEIDSVCTYPE" VARCHAR2(128),
    "PRINEIDDETDTTM" DATE,
    "PRINEIDLOCACITY" VARCHAR2(3),
    "PRINEIDLOCASTATE" VARCHAR2(21),
    "PRINEIDLOCZCITY" VARCHAR2(3),
    "PRINEIDLOCZSTATE" VARCHAR2(21),
    "TKTTYPE" VARCHAR2(10),
    "DOMAIN" VARCHAR2(10),
    "PRODTYPE" VARCHAR2(10),
    "SYMCODE" VARCHAR2(10),
    "SYMCODEDESC" VARCHAR2(50),
    "RPTSRC" VARCHAR2(10),
    "TOTALTKTTM" NUMBER,
    "SHELLTKTTM" NUMBER(*,0),
    "OTGCLOCKON" VARCHAR2(1),
    "OTGCLOCKSEQ" VARCHAR2(5),
    "OTGTM" NUMBER,
    "ORIGNEID" VARCHAR2(80),
    "NADCODE" VARCHAR2(30),
    "NADDTTM" DATE,
    "NADCODEDESC" VARCHAR2(50),
    "OTGCAUSE" VARCHAR2(50),
    "RESLCODE" VARCHAR2(10),
    "PLATFORM" VARCHAR2(30),
    "CATEQUIP" VARCHAR2(30),
    "RESOLVEDDT" DATE,
    "CLOSEDDT" DATE,
    "PROBSUMMARY" VARCHAR2(500),
    "TOPGRPESCSTS" VARCHAR2(1),
    "TOPGRPESCLEV" VARCHAR2(2),
    "TOPGRPLASTESCTM" DATE,
    "TMGRPESCSTS" VARCHAR2(1),
    "TMGRPESCLEV" VARCHAR2(2),
    "TMGRPLASTESCTM" DATE,
    "FAIFLAG" VARCHAR2(1),
    "MSIFLAG" VARCHAR2(1),
    "CHRONICFLAG" VARCHAR2(1),
    "SLAMTTR" NUMBER,
    "TSPCODE" VARCHAR2(13),
    "DEFERREDSTARTTM" DATE,
    "TOTALDEFERREDDUR" NUMBER,
    "CURSTA" VARCHAR2(10),
    "CURSTS" VARCHAR2(10),
    "STSCOMMENT" VARCHAR2(100),
    "ACTIVEINTREFERRALS" NUMBER(*,0),
    "ACTIVEEXTREFERRALS" NUMBER(*,0),
    "NUMOFXREFS" NUMBER(*,0),
    "LASTUPDDTTM" DATE,
    "LASTUPDUSERID" NUMBER,
    "CREATEUSERID_NAME" VARCHAR2(21),
    "CREATEWKGRPID_NAME" VARCHAR2(21),
    "TMGRP_NAME" VARCHAR2(21),
    "TOPGRP_NAME" VARCHAR2(21),
    "TMUSER_NAME" VARCHAR2(21),
    "TOPUSER_NAME" VARCHAR2(21),
    "RESLCODEDESC" VARCHAR2(50),
    "RDB_INSERT_DATE" DATE,
    "CUSCNCTHOMEPHN" VARCHAR2(22),
    "CUSCNCTCELLPHN" VARCHAR2(21),
    "CUSCNCTFAXNUM" VARCHAR2(22),
    "CUSCNCTEMAIL" VARCHAR2(47),
    "ALTCUSCNCTHOMEPHN" VARCHAR2(22),
    "ALTCUSCNCTCELLPHN" VARCHAR2(21),
    "ALTCUSCNCTFAXNUM" VARCHAR2(22),
    "ALTCUSCNCTEMAIL" VARCHAR2(47),
    "CUSCNCTALTPHN" VARCHAR2(22),
    "ALTCUSCNCTALTPHN" VARCHAR2(22),
    "CREATEUSERNAME" VARCHAR2(21),
    "CREATEWKGRPNAME" VARCHAR2(21),
    "TMGRPNAME" VARCHAR2(21),
    "TOPGRPNAME" VARCHAR2(21),
    "TMUSERNAME" VARCHAR2(21),
    "TOPUSERNAME" VARCHAR2(21),
    "LASTUPDUSERNAME" VARCHAR2(21),
    "CURINTROGNAME" VARCHAR2(22),
    "CURINTROUSERNAME" VARCHAR2(22),
    "CURETTRID" NUMBER,
    "CURLECNAME" VARCHAR2(21),
    "CUREXTRODTTM" DATE,
    "RESOLVEBYUSERNAME" VARCHAR2(21),
    "RESOLVEBYWKGRPNAME" VARCHAR2(21),
    "RESOLVEDBYUSERID" NUMBER,
    "RESOLVEDBYWKGRP" NUMBER,
    "NUMOFNEIDS" NUMBER,
    "PRINEIDLOCACTYNAME" VARCHAR2(40),
    "PRINEIDLOCZCTYNAME" VARCHAR2(40),
    "SYMPTCAT" VARCHAR2(32),
    "RECEIVEDVIA" VARCHAR2(32),
    "RECENTAPPERRORCODE" VARCHAR2(10),
    "CORPID" VARCHAR2(15),
    "KEYWORDS" VARCHAR2(25),
    "SLALEVEL" VARCHAR2(1),
    "ROGSTSCOMMENT" VARCHAR2(100),
    "TOGSTSCOMMENT" VARCHAR2(100),
    "TMGSTSCOMMENT" VARCHAR2(100),
    "CUSCNCTPAGER" VARCHAR2(47),
    "ALTCUSCNCTPAGER" VARCHAR2(47),
    "METANAMETBL" VARCHAR2(10),
    "NEXTACTIONDTTM" DATE,
    "TOPWKGRPSTATUS" VARCHAR2(10),
    "INTGRPID" VARCHAR2(21),
    "INTPUBFLAG" VARCHAR2(1),
    "INTTKTNUM" VARCHAR2(30),
    "BILLEVENTFLAG" VARCHAR2(1),
    "WHN_OTGTM" NUMBER DEFAULT 0,
    "ILEC_OTGTM" NUMBER DEFAULT 0,
    "EVENTID" VARCHAR2(15),
    "NUMCIRCUITS" NUMBER,
    "TMASSIGNDTTM" DATE,
    "TOPASSIGNDTTM" DATE,
    "ALERTCUSFLAG" VARCHAR2(1),
    "MCIPRODNAME" VARCHAR2(40),
    "ALTNEID" VARCHAR2(53),
    "CONTROLSITE" VARCHAR2(14),
    "CRITICALINDICATOR" VARCHAR2(1),
    "REPORTEDBYNAME" VARCHAR2(80),
    "REPORTEDBYPHN" VARCHAR2(22),
    "REPORTEDBYCELLPHN" VARCHAR2(21),
    "REPORTEDBYEMAIL" VARCHAR2(47),
    "REPORTEDBYFAXNUM" VARCHAR2(22),
    "REPORTEDBYHOMEPHN" VARCHAR2(22),
    "REPORTEDBYPAGER" VARCHAR2(47),
    "REPORTEDBYALTPHN" VARCHAR2(22),
    "DISPATCHIND" VARCHAR2(1),
    "BILLCUSTNOTIFY" VARCHAR2(1) DEFAULT 0,
    "ACCESSID" NUMBER DEFAULT 0 NOT NULL ENABLE,
    "GARMLEVEL" VARCHAR2(10) DEFAULT 1 NOT NULL ENABLE,
    "GARMID" VARCHAR2(100) DEFAULT ' ' NOT NULL ENABLE,
    "GARMIDTYPE" VARCHAR2(50) DEFAULT ' ' NOT NULL ENABLE,
    "T1AINDICATOR" VARCHAR2(15),
    "TKTSOURCE" VARCHAR2(20),
    "SOURCETEXT" VARCHAR2(40),
    "RCOCIRCUITID" VARCHAR2(53),
    "RCOTKTNUM" VARCHAR2(13)
    ) PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255 LOGGING
    STORAGE(INITIAL 134217728 NEXT 134217728
    BUFFER_POOL DEFAULT)
    TABLESPACE "TS_MED1"
    PARTITION BY RANGE ("TKTNUM")
    (PARTITION "PART_OLD" VALUES LESS THAN ('2003080100001')
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 134217728 NEXT 5242880 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_OLD" NOCOMPRESS ,
    PARTITION "PART04Q1" VALUES LESS THAN ('2004033199999')
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 52428800 NEXT 52428800 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_04_OLD" NOCOMPRESS ,
    PARTITION "PART04Q2" VALUES LESS THAN ('2004063099999')
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 52428800 NEXT 52428800 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_04_OLD" NOCOMPRESS ,
    PARTITION "PART04Q3" VALUES LESS THAN ('2004093099999')
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 52428800 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_04_OLD" NOCOMPRESS ,
    PARTITION "PART04Q4" VALUES LESS THAN ('2004123199999')
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 52428800 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_04_OLD" NOCOMPRESS ,
    PARTITION "PART05Q1Q2" VALUES LESS THAN ('2005063199999')
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 20971520 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEADER_05Q1Q2" NOCOMPRESS ,
    PARTITION "PART05Q3Q4" VALUES LESS THAN ('2005123199999')
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 20971520 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_05Q3Q4" NOCOMPRESS ,
    PARTITION "PART06Q1Q2" VALUES LESS THAN ('2006063199999')
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 20971520 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_06Q1Q2" NOCOMPRESS ,
    PARTITION "PART06Q3Q4" VALUES LESS THAN ('2006123199999')
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 5242880 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_06Q3Q4" NOCOMPRESS ,
    PARTITION "PART07Q1Q2" VALUES LESS THAN ('2007063199999')
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 5242880 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_07Q1Q2" NOCOMPRESS ,
    PARTITION "PART07Q3Q4" VALUES LESS THAN ('2007123199999')
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 5242880 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_07Q3Q4" NOCOMPRESS ,
    PARTITION "PART08Q1Q2" VALUES LESS THAN ('2008063199999')
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 5242880 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_08Q1Q2" NOCOMPRESS ,
    PARTITION "PART08Q3Q4" VALUES LESS THAN ('2008123199999')
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 5242880 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_08Q3Q4" NOCOMPRESS ,
    PARTITION "PART09Q1Q2" VALUES LESS THAN ('2009063099999')
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 5242880 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_09Q1Q2" NOCOMPRESS ,
    PARTITION "PART09Q3Q4" VALUES LESS THAN (MAXVALUE)
    PCTFREE 20 PCTUSED 50 INITRANS 1 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 5242880 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_09Q3Q4" NOCOMPRESS )
    CREATE INDEX "ETMS"."XTKTHDR9" ON "ETMS"."T3TKTHEADER" ("LASTUPDDTTM", "INTPUB
    FLAG", "CURSTS")
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(
    BUFFER_POOL DEFAULT) LOCAL
    (PARTITION "PART_OLD"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 5242880 NEXT 5242880 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_TKTHEAD_OLD" ,
    PARTITION "PART04Q1"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 20971520 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_IND_TKTHEAD_04_OLD" ,
    PARTITION "PART04Q2"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 20971520 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_IND_TKTHEAD_04_OLD" ,
    PARTITION "PART04Q3"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 20971520 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_IND_TKTHEAD_04_OLD" ,
    PARTITION "PART04Q4"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 20971520 NEXT 20971520 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_IND_TKTHEAD_04_OLD" ,
    PARTITION "PART05Q1Q2"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 10485760 NEXT 10485760 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_IND_TKTHEADER_05Q1Q2" ,
    PARTITION "PART05Q3Q4"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 10485760 NEXT 10485760 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_IND_TKTHEAD_05Q3Q4" ,
    PARTITION "PART06Q1Q2"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 5242880 NEXT 5242880 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_IND_TKTHEAD_06Q1Q2" ,
    PARTITION "PART06Q3Q4"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 1048576 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_IND_TKTHEAD_06Q3Q4" ,
    PARTITION "PART07Q1Q2"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 1048576 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_IND_TKTHEAD_07Q1Q2" ,
    PARTITION "PART07Q3Q4"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 1048576 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_IND_TKTHEAD_07Q3Q4" ,
    PARTITION "PART08Q1Q2"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 1048576 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_IND_TKTHEAD_08Q1Q2" ,
    PARTITION "PART08Q3Q4"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 1048576 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_IND_TKTHEAD_08Q3Q4" ,
    PARTITION "PART09Q1Q2"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 1048576 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_IND_TKTHEAD_09Q1Q2" ,
    PARTITION "PART09Q3Q4"
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 1048576 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "TS_IND_TKTHEAD_09Q3Q4" )
    PARALLEL 4
    DATA:
    2000120600662 06-Dec-2000 11:39:56 PM 12671 1243 UNKNOWN 5 11 0 1243 1243 -1 0 0 916 576 2675 06-Dec-2000 03:48:22 PM ANI CUSTOMER 0 0 -1 916 576 2675 0 06-Dec-2000 03:48:22 PM 0 06-Dec-2000 03:48:22 PM 0 0 0 0 CLOSED VOID 0 0 0 10-May-2001 10:17:18 PM 10873 unknown TXSAN.CSLOC TXSAN.CSLOC TXSAN.CSLOC 16-May-2008 05:50:29 PM unknowni TXSAN.CSLOC TXSAN.CSLOC TXSAN.CSLOC sburke 0 1 ALL PHONE 0 1
    2001021300976 23-Apr-2001 03:00:49 PM 50766 2113 UNKNOWN 5 2 0 2113 2113 -1 0 0 75fnode 13-Feb-2001 11:12:48 AM EQUIPMENT 0 0 1 75fnode 0 13-Feb-2001 11:12:48 AM 0 13-Feb-2001 11:12:48 AM 0 0 0 0 CLOSED VOID 0 0 0 22-May-2001 01:30:37 PM 10866 unknown MABST.3CMNOD MABST.3CMNOD MABST.3CMNOD 16-May-2008 05:50:29 PM unknown MABST.3CMNOD MABST.3CMNOD MABST.3CMNOD jcece 0 1 ALL PHONE 0 1
    2001022100287 21-Mar-2001 07:00:37 PM 62393 9974 UNKNOWN 5 14 0 9974 9974 -1 0 0 3P19S.S63.0031 20-Feb-2001 08:53:57 PM CIRCUIT CUSTOMER 0 0 0 -1 3P19S.S63.0031 0 20-Feb-2001 08:53:57 PM 0 20-Feb-2001 08:53:57 PM 0 0 0 0 CLOSED VOID 0 0 0 28-Apr-2001 03:47:18 PM 12782 mclement9486 CASAC.SSO CASAC.SSO CASAC.SSO 16-May-2008 05:50:29 PM mclement9486 CASAC.SSO CASAC.SSO CASAC.SSO unknown 0 01-Jan-1970 12:00:00 AM 1 ALL PHONE 1 N N 0 1
    2001022101367 21-Feb-2001 09:57:41 PM 42424 2935 UNKNOWN 5 4 0 2935 2935 -1 0 0 0808 105 0020 21-Feb-2001 10:46:50 AM SWITCHED CLI 0 0 -1 0808 105 0020 0 21-Feb-2001 10:46:50 AM 0 21-Feb-2001 10:46:50 AM 0 0 0 0 CLOSED VOID VOID 0 0 0 23-Apr-2001 05:54:57 PM 11063 unknown UKLN.CSCCO UKLN.CSCCO UKLN.CSCCO 16-May-2008 05:50:29 PM gharvey UKLN.CSCCO UKLN.CSCCO UKLN.CSCCO unknown 0 01-Jan-1970 12:00:00 AM 1 ALL PHONE 0 1
    Hope this helps.
    Thanks in advance,
    Arindam

  • Fact and dimension table partition

    My team is implementing new data-warehouse. I would like to know that when  should we plan to do partition of fact and dimension table, before data comes in or after?

    Hi,
    It is recommended to partition Fact table (Where we will have huge data). Automate the partition so that each day it will create a new partition to hold latest data (Split the previous partition into 2). Best practice is to create partition on transaction
    timestamps so load the incremental data into a empty table called (Table_IN) and then Switch that data into main table (Table). Make sure your tables (Table and Table_IN) should be on one file group.
    Refer below content for detailed info
    Designing and Administrating Partitions in SQL Server 2012
    A popular method of better managing large and active tables and indexes is the use of partitioning. Partitioning is a feature for segregating I/O workload within
    SQL Server database so that I/O can be better balanced against available I/O subsystems while providing better user response time, lower I/O latency, and faster backups and recovery. By partitioning tables and indexes across multiple filegroups, data retrieval
    and management is much quicker because only subsets of the data are used, meanwhile ensuring that the integrity of the database as a whole remains intact.
    Tip
    Partitioning is typically used for administrative or certain I/O performance scenarios. However, partitioning can also speed up some queries by enabling
    lock escalation to a single partition, rather than to an entire table. You must allow lock escalation to move up to the partition level by setting it with either the Lock Escalation option of Database Options page in SSMS or by using the LOCK_ESCALATION option
    of the ALTER TABLE statement.
    After a table or index is partitioned, data is stored horizontally across multiple filegroups, so groups of data are mapped to individual partitions. Typical
    scenarios for partitioning include large tables that become very difficult to manage, tables that are suffering performance degradation because of excessive I/O or blocking locks, table-centric maintenance processes that exceed the available time for maintenance,
    and moving historical data from the active portion of a table to a partition with less activity.
    Partitioning tables and indexes warrants a bit of planning before putting them into production. The usual approach to partitioning a table or index follows these
    steps:
    1. Create
    the filegroup(s) and file(s) used to hold the partitions defined by the partitioning scheme.
    2. Create
    a partition function to map the rows of the table or index to specific partitions based on the values in a specified column. A very common partitioning function is based on the creation date of the record.
    3. Create
    a partitioning scheme to map the partitions of the partitioned table to the specified filegroup(s) and, thereby, to specific locations on the Windows file system.
    4. Create
    the table or index (or ALTER an existing table or index) by specifying the partition scheme as the storage location for the partitioned object.
    Although Transact-SQL commands are available to perform every step described earlier, the Create Partition Wizard makes the entire process quick and easy through
    an intuitive point-and-click interface. The next section provides an overview of using the Create Partition Wizard in SQL Server 2012, and an example later in this section shows the Transact-SQL commands.
    Leveraging the Create Partition Wizard to Create Table and Index Partitions
    The Create Partition Wizard can be used to divide data in large tables across multiple filegroups to increase performance and can be invoked by right-clicking
    any table or index, selecting Storage, and then selecting Create Partition. The first step is to identify which columns to partition by reviewing all the columns available in the Available Partitioning Columns section located on the Select a Partitioning Column
    dialog box, as displayed in Figure 3.13. This screen also includes additional options such as the following:
    Figure 3.13. Selecting a partitioning column.
    The next screen is called Select a Partition Function. This page is used for specifying the partition function where the data will be partitioned. The options
    include using an existing partition or creating a new partition. The subsequent page is called New Partition Scheme. Here a DBA will conduct a mapping of the rows selected of tables being partitioned to a desired filegroup. Either a new partition scheme should
    be used or a new one needs to be created. The final screen is used for doing the actual mapping. On the Map Partitions page, specify the partitions to be used for each partition and then enter a range for the values of the partitions. The
    ranges and settings on the grid include the following:
    Note
    By opening the Set Boundary Values dialog box, a DBA can set boundary values based on dates (for example, partition everything in a column after a specific
    date). The data types are based on dates.
    Designing table and index partitions is a DBA task that typically requires a joint effort with the database development team. The DBA must have a strong understanding
    of the database, tables, and columns to make the correct choices for partitioning. For more information on partitioning, review Books Online.
    Enhancements to Partitioning in SQL Server 2012
    SQL Server 2012 now supports as many as 15,000 partitions. When using more than 1,000 partitions, Microsoft recommends that the instance of SQL Server have at
    least 16Gb of available memory. This recommendation particularly applies to partitioned indexes, especially those that are not aligned with the base table or with the clustered index of the table. Other Data Manipulation Language statements (DML) and Data
    Definition Language statements (DDL) may also run short of memory when processing on a large number of partitions.
    Certain DBCC commands may take longer to execute when processing a large number of partitions. On the other hand, a few DBCC commands can be scoped to the partition
    level and, if so, can be used to perform their function on a subset of data in the partitioned table.
    Queries may also benefit from a new query engine enhancement called partition elimination. SQL Server uses partition enhancement automatically if it is available.
    Here’s how it works. Assume a table has four partitions, with all the data for customers whose names begin with R, S, or T in the third partition. If a query’s WHERE clause
    filters on customer name looking for ‘System%’, the query engine knows that it needs only to partition three to answer
    the request. Thus, it might greatly reduce I/O for that query. On the other hand, some queries might take longer if there are more than 1,000 partitions and the query is not able to perform partition elimination.
    Finally, SQL Server 2012 introduces some changes and improvements to the algorithms used to calculate partitioned index statistics. Primarily, SQL Server 2012
    samples rows in a partitioned index when it is created or rebuilt, rather than scanning all available rows. This may sometimes result in somewhat different query behavior compared to the same queries running on SQL Server 2012.
    Administrating Data Using Partition Switching
    Partitioning is useful to access and manage a subset of data while losing none of the integrity of the entire data set. There is one limitation, though. When
    a partition is created on an existing table, new data is added to a specific partition or to the default partition if none is specified. That means the default partition might grow unwieldy if it is left unmanaged. (This concept is similar to how a clustered
    index needs to be rebuilt from time to time to reestablish its fill factor setting.)
    Switching partitions is a fast operation because no physical movement of data takes place. Instead, only the metadata pointers to the physical data are altered.
    You can alter partitions using SQL Server Management Studio or with the ALTER TABLE...SWITCH
    Transact-SQL statement. Both options enable you to ensure partitions are
    well maintained. For example, you can transfer subsets of data between partitions, move tables between partitions, or combine partitions together. Because the ALTER TABLE...SWITCH statement
    does not actually move the data, a few prerequisites must be in place:
    • Partitions must use the same column when switching between two partitions.
    • The source and target table must exist prior to the switch and must be on the same filegroup, along with their corresponding indexes,
    index partitions, and indexed view partitions.
    • The target partition must exist prior to the switch, and it must be empty, whether adding a table to an existing partitioned table
    or moving a partition from one table to another. The same holds true when moving a partitioned table to a nonpartitioned table structure.
    • The source and target tables must have the same columns in identical order with the same names, data types, and data type attributes
    (length, precision, scale, and nullability). Computed columns must have identical syntax, as well as primary key constraints. The tables must also have the same settings for ANSI_NULLS and QUOTED_IDENTIFIER properties.
    Clustered and nonclustered indexes must be identical. ROWGUID properties
    and XML schemas must match. Finally, settings for in-row data storage must also be the same.
    • The source and target tables must have matching nullability on the partitioning column. Although both NULL and NOT
    NULL are supported, NOT
    NULL is strongly recommended.
    Likewise, the ALTER TABLE...SWITCH statement
    will not work under certain circumstances:
    • Full-text indexes, XML indexes, and old-fashioned SQL Server rules are not allowed (though CHECK constraints
    are allowed).
    • Tables in a merge replication scheme are not allowed. Tables in a transactional replication scheme are allowed with special caveats.
    Triggers are allowed on tables but must not fire during the switch.
    • Indexes on the source and target table must reside on the same partition as the tables themselves.
    • Indexed views make partition switching difficult and have a lot of extra rules about how and when they can be switched. Refer to
    the SQL Server Books Online if you want to perform partition switching on tables containing indexed views.
    • Referential integrity can impact the use of partition switching. First, foreign keys on other tables cannot reference the source
    table. If the source table holds the primary key, it cannot have a primary or foreign key relationship with the target table. If the target table holds the foreign key, it cannot have a primary or foreign key relationship with the source table.
    In summary, simple tables can easily accommodate partition switching. The more complexity a source or target table exhibits, the more likely that careful planning
    and extra work will be required to even make partition switching possible, let alone efficient.
    Here’s an example where we create a partitioned table using a previously created partition scheme, called Date_Range_PartScheme1.
    We then create a new, nonpartitioned table identical to the partitioned table residing on the same filegroup. We finish up switching the data from the partitioned table into the nonpartitioned table:
    CREATE TABLE TransactionHistory_Partn1 (Xn_Hst_ID int, Xn_Type char(10)) ON Date_Range_PartScheme1 (Xn_Hst_ID) ; GO CREATE TABLE TransactionHistory_No_Partn (Xn_Hst_ID int, Xn_Type
    char(10)) ON main_filegroup ; GO ALTER TABLE TransactionHistory_Partn1 SWITCH partition1 TO TransactionHistory_No_Partn; GO
    The next section shows how to use a more sophisticated, but very popular, approach to partition switching called a sliding
    window partition.
    Example and Best Practices for Managing Sliding Window Partitions
    Assume that our AdventureWorks business is booming. The sales staff, and by extension the AdventureWorks2012 database, is very busy. We noticed over time that
    the TransactionHistory table is very active as sales transactions are first entered and are still very active over their first month in the database. But the older the transactions are, the less activity they see. Consequently, we’d like to automatically group
    transactions into four partitions per year, basically containing one quarter of the year’s data each, in a rolling partitioning. Any transaction older than one year will be purged or archived.
    The answer to a scenario like the preceding one is called a sliding window partition because
    we are constantly loading new data in and sliding old data over, eventually to be purged or archived. Before you begin, you must choose either a LEFT partition function window or a RIGHT partition function window:
    1. How
    data is handled varies according to the choice of LEFT or RIGHT partition function window:
    • With a LEFT strategy, partition1 holds the oldest data (Q4 data), partition2 holds data that is 6- to 9-months old (Q3), partition3
    holds data that is 3- to 6-months old (Q2), and partition4 holds recent data less than 3-months old.
    • With a RIGHT strategy, partition4 holds the holds data (Q4), partition3 holds Q3 data, partition2 holds Q2 data, and partition1
    holds recent data.
    • Following the best practice, make sure there are empty partitions on both the leading edge (partition0) and trailing edge (partition5)
    of the partition.
    • RIGHT range functions usually make more sense to most people because it is natural for most people to to start ranges at their lowest
    value and work upward from there.
    2. Assuming
    that a RIGHT partition function windows is used, we first use the SPLIT subclause of the ALTER PARTITION FUNCTIONstatement
    to split empty partition5 into two empty partitions, 5 and 6.
    3. We
    use the SWITCH subclause
    of ALTER TABLE to
    switch out partition4 to a staging table for archiving or simply to drop and purge the data. Partition4 is now empty.
    4. We
    can then use MERGE to
    combine the empty partitions 4 and 5, so that we’re back to the same number of partitions as when we started. This way, partition3 becomes the new partition4, partition2 becomes the new partition3, and partition1 becomes the new partition2.
    5. We
    can use SWITCH to
    push the new quarter’s data into the spot of partition1.
    Tip
    Use the $PARTITION system
    function to determine where a partition function places values within a range of partitions.
    Some best practices to consider for using a slide window partition include the following:
    • Load newest data into a heap, and then add indexes after the load is finished. Delete oldest data or, when working with very large
    data sets, drop the partition with the oldest data.
    • Keep an empty staging partition at the leftmost and rightmost ends of the partition range to ensure that the partitions split when
    loading in new data, and merge, after unloading old data, do not cause data movement.
    • Do not split or merge a partition already populated with data because this can cause severe locking and explosive log growth.
    • Create the load staging table in the same filegroup as the partition you are loading.
    • Create the unload staging table in the same filegroup as the partition you are deleting.
    • Don’t load a partition until its range boundary is met. For example, don’t create and load a partition meant to hold data that is
    one to two months older before the current data has aged one month. Instead, continue to allow the latest partition to accumulate data until the data is ready for a new, full partition.
    • Unload one partition at a time.
    • The ALTER TABLE...SWITCH statement
    issues a schema lock on the entire table. Keep this in mind if regular transactional activity is still going on while a table is being partitioned.
    Thanks Shiven:) If Answer is Helpful, Please Vote

  • Table partitioning and global indexing

    hello all,
    the requirement is to do table partitioning with global indexing! & also thr r almost 60 crores of rows are there! so can you tell me the way which can be done better and also please provide me the procedure with documents?
    thanks in advance!

    Hi,
    have a look at online redefinition of a table, see Oracle Manual (10.2): http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tables.htm#ADMIN01514
    The steps are described in the manual.
    Herald ten Dam
    Superconsult.nl

  • Benefits of table partitioning on ASM controlled storage?

    Hi everyone,
    I understand that, as the documentation describes, table partitioning for the purpose of striping is a very good strategy for high performing OLTP databases. So you can explicitly assign partitions to different database-files, residing on different disks. A pretty clear benefit.
    What about ASM controlled storage? Does it help partitioning your tables here, for the purpose of striping? Or is it even better to abandon the ASM option for the sake of reliable striping benefit?
    Thanks in advance for any helpful thought or real life report...

    My situation is the following:
    I am a database developer/architect. In my organisation we have a DBA team, which has no knowledge of the application.
    So, I am not in a position to test. I am supposed to order/require this or that from our DBA, in this case ASM or NO ASM. Partitioning of tables is my job.
    That's why I am asking if anybody else has experience with this.
    To our app: our challenge - when we go into production - will not be the mass of data, but the concurrent use of it from up-to 10.000 users. This is why I am considering a partitioning solution, suitable to the usage profile.
    So does anybody have experience from similar scenarios? Is it possible to trace, what ASM actually does, e.g. does it stripe the tables across the drives optimally?

  • Can we addnew partition and sub partition in the existing table in one shor

    can we addnew partition and sub partition in the existing table in one short

    nav wrote:
    can we addnew partition and sub partition in the existing table in one shortYes,
    You can and below is the example for Range-List partition
    ALTER TABLE <table_name>
       ADD PARTITION <partition_name> VALUES LESS THAN (<value>
          STORAGE (INITIAL 20K NEXT 20K) TABLESPACE <TS name> NOLOGGING
              SUBPARTITION Clause
              SUBPARTITION Clause
              SUBPARTITION Clause
              SUBPARTITION Clause
               );

  • Getting error while importing a table partition

    Hi,
    I am trying to import a table partition from OEM and occurred with following error:
    Job IMPORT000042 has been reopened at Friday, 13 June, 2008 14:44
    Restarting "SYSMAN"."IMPORT000042":
    Processing object type TABLE_EXPORT/TABLE/TBL_TABLE_DATA/TABLE/TABLE_DATA
    ORA-31693: Table data object "SCOTT"."CONTAINER":"PARTITION_5" failed to load/unload and is being skipped due to error:
    ORA-06502: PL/SQL: numeric or value error
    LPX-00210: expected '<' instead of 'n'
    Job "SYSMAN"."IMPORT000042" completed with 1 error(s) at 14:44
    Job state: COMPLETED
    Thanks

    What's the source and target database Oracle version?
    What's the character set of both databases?

  • Long running table partitioning job

    Dear HANA grus,
    I've just finished table partitioning jobs for CDPOS(change document item) with 4 partitions by hash with 3 columns.
    Total data volumn is around 340GB and the table size was 32GB !!!!!
    (migration job was done without disabling CD, so currently deleting data on the table with RSCDOK99)
    Before partitioning, the data volumn of the table was around 32GB.
    After partitioning, the size has changed to 25GB.
    It took around One and half hour with exclusive lock as mentioned in the HANA adminitration guide.
    (It is QA DB, so less complaints)
    I thought that I might not can do this in the production DB.
    Does anyone hava any idea for accelerating this task?? (This is the fastest DBMS HANA!!!!)
    Or Do you have any plan for online table partitioning functionality??(To HANA Development team)
    Any comments would be appreciate.
    Cheers,
    - Jason

    Jason,
    looks like we're cross talking here...
    What was your rationale to partition the table in the first place?
           => To reduce deleting time of CDPOS            (As I mentioned it was almost 10% quantity of whole Data volume, So I would like to save deleting time of the table from any pros of partitioning table like partitioning pruning)
    Ok, I see where you're coming from, but did you ever try out if your idea would actually work?
    As deletion of data is heavily related with locating the records to be deleted, creating an index would have probably be the better choice.
    Thinking about it... you want to get rid of 10% of your data and in order to speed the overall process up, you decide to move 100% of the data into sets of 25% of the data - equally holding their 25% share of the 10% records to be deleted.
    The deletion then should run along these 4 sets of 25% of data.
    It's surely me, but where is the speedup potential here?
    How many unloads happened during the re-partitioning?
           => It was fully uploaded in the memory before partitioning the table by myself.(from HANA studio)
    I was actually asking about unloads _during_ the re-partitioning process. Check M_CS_UNLOADS for the time frame in question.
    How do the now longer running SQL statements look like?
           => As i mentioned selecting/deleting increased almost twice.
    That's not what I asked.
    Post the SQL statement text that was taking longer.
    What are the three columns you picked for partitioning?
           => mandant, objectclas, tabname(QA has 2 clients and each of them have nearly same rows of the table)
    Why those? Because these are the primary key?
    I wouldn't be surprised if the SQL statements only refer to e.g. MANDT and TABNAME in the WHERE clause.
    In that case the partition pruning cannot work and all partitions have to be searched.
    How did you come up with 4 partitions? Why not 13, 72 or 213?
           => I thought each partitions' size would be 8GB(32GB/4) if they are divided into same size(just simple thought), and 8GB size is almost same size like other largest top20 tables in the HANA DB.
    Alright, so basically that was arbitrary.
    For the last comment of your reply, most people would do partition for their existing large tables to get any benefit of partitioning(just like me). I think your comment can be applied for the newly inserting data.
    Well, not sure what "most people" would do.
    HASH partitioning a large existing table certainly is not an activity that is just triggered off in a production system. Adding partitions to a range partitions table however happens all the time.
    - Lars

  • Automatic table partitioning in Oracle 11g

    Hi All,
    I need to implement automatic table partitioning in Oracle 11g version, but partitioning interval should be on daily basis(For every day).
    I was able to perform this for Monthly and Yearly but not on daily basis.
    create table part
    (a date)PARTITION BY RANGE (a)
    INTERVAL (NUMTOYMINTERVAL(1,'*MONTH*'))
    (partition p1 values less than (TO_DATE('01-NOV-2007','DD-MON-YYYY'))
    Table created
    create table part
    (a date)PARTITION BY RANGE (a)
    INTERVAL (NUMTOYMINTERVAL(1,'*YEAR*'))
    (partition p1 values less than (TO_DATE('01-NOV-2007','DD-MON-YYYY'))
    Table createdBut if i use DD or DAY instead of YEAR or MONTH it fails......Please suggest me how to perform this on daily basis.
    SQL>
      1  create table part
      2  (a date)PARTITION BY RANGE (a)
      3  INTERVAL (NUMTOYMINTERVAL(1,'*DAY*'))
      4  (partition p1 values less than (TO_DATE('01-NOV-2007','DD-MON-YYYY'))
      5* )
    SQL> /
    INTERVAL (NUMTOYMINTERVAL(1,'DAY'))
    ERROR at line 3:
    ORA-14752: Interval expression is not a constant of the correct type
    SQL> create table part
    (a date)PARTITION BY RANGE (a)
    INTERVAL (NUMTOYMINTERVAL(1,'*DD*'))
    (partition p1 values less than (TO_DATE('01-NOV-2007','DD-MON-YYYY'))
    );  2    3    4    5
    INTERVAL (NUMTOYMINTERVAL(1,'DD'))
    ERROR at line 3:
    ORA-14752: Interval expression is not a constant of the correct typePlease suggest me to resolve this ORA-14752 error for using DAY or DD or HH24
    -Yasser

    Yes, for differenct partitions for different months.
    interval (numtoyminterval(1,'MONTH'))
    store in (TS1,TS2,TS3)
    This code will store data in partitions in tablespaces TS1, TS2, and TS3 in a round robin manner.
    for Day wise day yes you can store
    INTERVAL (NUMTODSINTERVAL(1,'day')) or
    INTERVAL (NUMTODSINTERVAL(2,'day')) or
    INTERVAL (NUMTODSINTERVAL(3,'day')) or
    INTERVAL (NUMTODSINTERVAL(4,'day')) or
    INTERVAL (NUMTODSINTERVAL(5,'day')) or
    INTERVAL (NUMTODSINTERVAL(n,'day'))

Maybe you are looking for