Truncating old partitions in the table.

Hi,
Can you pls helpme out in writing a job/script(procedure) to truncate 6 older partitons with date range partition 'YYYY-MM' in the table!!!
Thanks,

I have a 20 partitioned tables with more than year old data with range partitioning.
I am trying to develop a package/job either to drop or truncate 6 months older partitions.
I will truncate partitions periodically on each schema - not all at once.
if you someone can send me the scripts/procudure - that really helps my task.
Thanks,

Similar Messages

Problem in truncate/drop partitions in a table having nested table columns.

Hi,
I have a table that has 2 columns of type nested table. Now in the purge process, when I try to truncate or drop a partition from this table, I get error that I can't do this (because table has nested tables). Can anybody help me telling how I will be able to truncate/drop partition from this table? IF I change column types from nested table to varray type, will it help?
Also, is there any short method of moving existing data from a nested table column to a varray column (having same fields as nested table)?
Thanks in advance.

>
I have a table that has 2 columns of type nested table. Now in the purge process, when I try to truncate or drop a partition from this table, I get error that I can't do this (because table has nested tables). Can anybody help me telling how I will be able to truncate/drop partition from this table?
>
Unfortunately you can't do those operations when a table has a nested table column. No truncate, no drop, no exchange partition at the partition level.
A nested table column is stored as a separate table and acts like a 'child' table with foreign keys to the 'parent' table. It is these 'foreign keys' that prevent the truncation (just like normal foreign keys prevent truncating partions and must be disabled first) but there is no mechanism to 'disable' them.
Just one excellent example (there are many others) of why you should NOT use object columns at all.
>
IF I change column types from nested table to varray type, will it help?
>
Yes but I STRONGLY suggest you take this opportunity to change your data model to a standard relational one and put the 'child' (nested table) data into its own table with a foreign key to the parent. You can create a view on the two tables that can make data appear as if you have a nested table type if you want.
Assuming that you are going to ignore the above advice just create a new VARRAY type and a table with that type as a column. Remember VARRAYs are defined with a maximum size. So the number of nested table records needs to be within the capacity of the VARRAY type for the data to fit.
>
Also, is there any short method of moving existing data from a nested table column to a varray column (having same fields as nested table)?
>
Sure - just CAST the nested table to the VARRAY type. Here is code for a VARRAY type and a new table that shows how to do it.
-- new array type
CREATE OR REPLACE TYPE ARRAY_T AS VARRAY(10) OF VARCHAR2(64)
-- new table using new array type - NOTE there is no nested table storage clause - arrays stored inline
CREATE TABLE partitioned_table_array
     ( ID_ INT,
      arra_col ARRAY_T )
     PARTITION BY RANGE (ID_)
     ( PARTITION p1 VALUES LESS THAN (40)
     , PARTITION p2 VALUES LESS THAN(80)
     , PARTITION p3 VALUES LESS THAN(100)
-- insert the data from the original table converting the nested table data to the varray type
INSERT INTO PARTITIONED_TABLE_ARRAY
SELECT ID_, CAST(NESTED_COL AS ARRAY_T) FROM PARTITIONED_TABLENaturally since there is no more nested table storage you can truncate or drop partitions in the above table
alter table partitioned_table_array truncate partition p1
alter table partitioned_table_array drop partition p1

Truncating first partition created for table partitioned by INTERVAL

Hi,
I have a table created with interval partitions.
When I truncate the partitions, I am unable to truncate the very first partition created on the table. How can I do this?
Thanks.

>
When I truncate the partitions, I am unable to truncate the very first partition created on the table
>
I'm going to assume you mean DROP and not TRUNCATE and are getting thel following error when you try to DROP the very first partition
>
ORA-14758: Last partition in the range section cannot be dropped
>
Interval partitioned tables have one or more RANGE partitions and zero or more INTERVAL partitions. The boundary between the LAST range partition and the FIRST interval partition is known as the transition point.
As the error message states you cannot drop the sole remaining RANGE partition that is below the transition point.
You have to move the transition point by merging the last remaining RANGE partition and the first INTERVAL partition. Since dropping a partiton means you no longer want the data you would normally truncate the range partition prior to the merge to minimize the amount of undo and redo that will be generated by the merge.
See this article for an example of how to 'move' the transition point to effectively drop the last remaining RANGE partition.
http://prutser.wordpress.com/2010/01/11/dropping-interval-partitions/

Create index partition in the table partition tablespace

Hello,
I am running a custom job that
* Creates a tablespace daily
* Creates the daily table partition in the tablespace created
* Drops the tablepartition X days old
* Drops the tablespace for that partition on X+1 day.
The above job runs perfectly, but 'm having issues with managing the indexes for these partitioned tables. In the old database (10g - Single Node), all the partitions/indexes existed in one BIG tablespace and when I imported the table creation script into the new database, I modified all the table partitions & indexes to go into their respective tablespace.
Eg:
Table_name........Partition_name.....................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 runs, it creates the index into the default tablespace TBS_DATA.
Table_name........Partition_name.....................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 indexes to its default tablespace, but how can I ensure that the index gets created in its designated tablespace?
NOTE - the partition/tablespace management job that I run only creates the table partition and not the index.
The new env is a 2-Node 11gR2 RAC cluster on Linux x86_64.
Thanks in advance,
aBBy.

Excerpt from the job -
This creates the partition into the new tablespace.
v_sql_new_part := 'alter table '||tab_owner||'.'||tab_name||' add partition '||v_new_part_nm||'
values less than (to_date('''||v_new_part_dt_formatted||''',''DD-MON-YYYY'')) tablespace '||part_tbs;
execute immediate v_sql_new_part;New tablespace for new partition - because this is a 10T database and having multiple tablespaces helps with backup/recovery.
Thanks,
aBBy.

Old value in the table SETLEAF

Dear All,
Normally we take back up on every weekend. Due to some wrong transport request in production in last weekend, all the value in the table - SETLEAF has been overwriten. Is there any way in which we can read the value entry in the table -SETLEAF from the back up system befor the last week end ?
Please help immideate basis.
Regards,
sp sahu

Hello,
I think you will have to build another database to read the value from specific table.
Restore system to another server and check the table valaues.
Good Luck,
Atil

Deleting data from a partition in a table

There is a requirement to delete data from a particular partition in our PROD Env.
Please let me know the syntax for the same.
Also is it possible to truncate a partition?
The DB version is 10.2.0.4 and OS is Solaris 10
Regards,
Narayan
Edited by: user7202581 on Apr 14, 2013 12:11 AM

Hi, You can use the following Syntex.
-- For Truncate
ALTER TABLE <table_name> TRUNCATE PARTITION <Partition_name>;
-- For Delete
DELETE FROM <table_name> PARTITION <partition_name>;

How to truncate a partition in owb

I wonder how can i achieve truncating a partition before loading into this target table. I found this pre-mapping prcess where we have this option of truncating a table, but how can i just truncate a partition within a table in a mapping? please advice.
~Prabha

As per Detlef's suggestion, here's the basics that you can embedd in a function/procedure. Accepts 3 parameters in_table_name, in_subpartition_name and in_partition_name. You can also enhance ALTER statements to REUSE/DROP STORAGE if required.
v_sql VARCHAR2(250) DEFAULT NULL;
BEGIN
IF in_subpartition_name IS NOT NULL THEN
v_sql := 'ALTER TABLE '||in_table_name||' TRUNCATE SUBPARTITION '||in_subpartition_name;
ELSIF in_partition_name IS NOT NULL THEN
v_sql := 'ALTER TABLE '||in_table_name||' TRUNCATE PARTITION '||in_partition_name;
ELSE
RAISE no_data_found;
END IF;
EXECUTE IMMEDIATE v_sql;

Possible to swap multiple partitions into a table?

Hi,
We are using partition exchnage to swap individual partitions into table which then backed up.
This being done one partition at a time.
Is it possible to swap several partitions of a tabel in one go.
using Oracle 11.2.0.3
partioned by date, one partition of reach day.
Is it possible say to move the last 7 days partitions into the other table for backup using partition exchange?
Thanks

>
We are using partition exchnage to swap individual partitions into table which then backed up.
This being done one partition at a time.
Is it possible to swap several partitions of a tabel in one go.
>
No.
If the goal is to back up the data why not just use expdp to export the data for all seven partitions at once? Then drop the partitions.
If you only use one regular table for the exchange you would have to start with an empty table, swap one partition, backup the table, truncate the table, swap the next partition and so on.
Or you could create a table with seven empty partitions and swap the 7 partitions one at a time and then backup the new partitioned table.
Or you could create seven tables and swap each one with a partition and then backup all seven tables.
Too many choices.

Partitioning a fact table

I am curious to hear techniques for partitioning a fact table with OWB. I know HOW to setup the partitioning for the table, but what I am curious about is what type of partitioning everyone is suggesting. Take the following example...Lets say we have a sales transaction fact table. It has dimensions of Date, Product, and Store. An immediate partitioning idea is to partition the table by month. But my curiosity arises in the method used to partition the fact table. There is no longer a true date field in the fact table to do range partitioning on. And hash partitioning will not distribute the records by month.
One example I found was to "code" the surrogate key in the date dimension so that it was created in the following manner "YYYYMMDD". Then you could use the range partitioning based on values of the key in the fact table less than 20040200 for Jan. 2004, less than 20040300 for Feb. 2004, and so on.
Is this a good idea?

Jason,
In general, obviously, query performance and scaleability benefit from partitioning. Rather than hitting the entire table upon retrieving data, you would only hit a part of the table. There are two main strategies to identify what partitioning strategy to choose:
1) Users always query specific parts of the data (e.g. data from a particular month) in which case it makes sense for the part to be the size of the partition. If your end users often query by month or compare data on a month-by-month basis, then partitioning by month may well be the right strategy.
2) Improve data loading speed by creating partitions. The database supports partion exchange loading, supported by Warehouse Builder as well, which enables you to swap out a temporary table and a partition at once. In general, your load frequency then decides your partitioning strategy: if you load on a daily basis, perhaps you want daily partions. Beware that for Warehouse Builder to use the partition exchange loading feature you will have to have a date field in the fact table, so you would change the time dimension.
In general, your suggestion for the generated surrogate key would work.
Thanks,
Mark.

Diagnostic pack, Tuning pack are not in OEM 10g, Add partition to a table

Hi All,
I have 2 questions:
Q.1: In Oracle 9i Oracle Enterprise Manager java console, we had "Diagnostic Pack" and "Tuning Pack" which helped us seeing performance tuning info (session's statistics such as cpu time, pga memory, physical disk reads, etc.) and privded help for sql tuning and performance improvements. But in 10g, the same product (Oracle Enterprise Manager java console) does not include these 2 packs, due to which we are unable to monitor and control performance tuning information/statistics. Now my question is, do we need to install these 2 packs separately in 10g? if yes, where can we get them? (I am sure in 9i, these packages came with OEM console and we didnt need to get them separately)
Q.2: I have a partitioned table having 5 partitions based on range partitioning. Now our requirements have changed and we need to insert values beyong the 5th partition, so we need a 6th partition. Can someone tell me the command to add a new partition to the table? I tried "Alter table xxx add partition yyy ....", but it didn't work. If any one can me the correct syntax, it will be great.
Thanks in advance.

OP is talking about java-based EM, not web-based DBConsole. In fact he/she has to change to DBConsole, because 10g java EM doesn't longer support these tuning features.
Alter table ... partition syntax depends on the kind of partitioning, see the documentation:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_3001.htm#i2131048
Werner

Partitioning on the base of date

hi,
im having a PROBLEM IN CREATING A TABLE containing a date column having range partitioning on it. my table an accompanying error is :
CREATE TABLE A123 (A NUMBER, B DATE)
PARTITION BY RANGE (B)
(PARTITION B1 VALUES LESS THAN (TO_DATE((SYSDATE - INTERVAL '30' DAY),'DD-MON-YYYY')))
(PARTITION B1 VALUES LESS THAN (TO_DATE((SYSDATE - INTERVAL '30' DAY),'DD-MON-YYYY')))
ERROR at line 3:
ORA-14019: partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE
i'v also tried it as:
CREATE TABLE A123 (A NUMBER, B DATE)
PARTITION BY RANGE (B)
(PARTITION B1 VALUES LESS THAN (TO_DATE(SYSDATE - INTERVAL '30' DAY,'DD-MON-YYYY')))
(PARTITION B1 VALUES LESS THAN (TO_DATE(SYSDATE - INTERVAL '30' DAY,'DD-MON-YYYY')))
ERROR at line 3:
ORA-14019: partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE
as shown above,,i want to create partitions of the table A123 column b which is of date datatype,,i want to have a partition which stores data of SYSDATE - 30,.
Any suggestions/recommendations would be appreciated.
thanx
Regards

hi,
sorry im calling u again for support,,
the way u told for creating a table based on date column partitions creates a table with fixed date as a HIGH/UPPER BOUND,,for example if i create a table A123 as :
begin
execute immediate 'CREATE TABLE A123 (A NUMBER, B DATE)
PARTITION BY RANGE (B)
(PARTITION B4 VALUES LESS THAN (TO_DATE(('''||to_char(SYSDATE - INTERVAL '90' DAY,'DD-MON-YYYY')||'''),''DD-MON-YYYY''))
,PARTITION B3 VALUES LESS THAN (TO_DATE(('''||to_char(SYSDATE - INTERVAL '60' DAY,'DD-MON-YYYY')||'''),''DD-MON-YYYY''))
,PARTITION B2 VALUES LESS THAN (TO_DATE(('''||to_char(SYSDATE - INTERVAL '30' DAY,'DD-MON-YYYY')||'''),''DD-MON-YYYY''))
,PARTITION B1 VALUES LESS THAN (MAXVALUE))';
end;
ALTER TABLE A123 ENABLE ROW MOVEMENT
now the HIGH VALUE for partition B2 is January 03,2005...
while i want it to be dynamic.
means after 2 months the high value for B2 partition should be (Jan 03,2005 + 2 months)..
can we do this in oracle??
Regards.

No option to specify interval partition when creating table

I am trying to create a table in APPS which has Range partition with interval 1 (interval partition). When I go through the options to create the table, I see only Range, List and Hash partitions. How do I create interval partitions?

Thanks Chris for the update. Where can I find the correct syntax to use. Below is the current content for partition in the .table file.
<entry>
<key>OracleTablePartitions</key>
<value class="oracle.javatools.db.ora.OracleTablePartitions">
<ID class="oracle.javatools.db.IdentifierBasedID">
<name><![CDATA[PARTITION]|http://forums.oracle.com/forums/]></name>
<identifier class="java.lang.String"><![CDATA[8dd284eb-9b8a-4eb9-9f35-2f05b1911094]|http://forums.oracle.com/forums/]></identifier>
<parent class="oracle.javatools.db.TemporaryObjectID">
</parent>
<schemaName><![CDATA[FUSION]|http://forums.oracle.com/forums/]></schemaName>
<type><![CDATA[PARTITION MODEL]|http://forums.oracle.com/forums/]></type>
</ID>
<objectType>PARTITION</objectType>
<partitionColumns>
<partitionColumn class="oracle.javatools.db.IdentifierBasedID">
<name><![CDATA[ATTR_GROUP_ID]|http://forums.oracle.com/forums/]></name>
<identifier class="java.lang.String"><![CDATA[979467ab-e769-42f9-a631-735b24b01670]|http://forums.oracle.com/forums/]></identifier>
<parent class="oracle.javatools.db.IdentifierBasedID">
<name><![CDATA[EGO_ITEM_EFF_B]|http://forums.oracle.com/forums/]></name>
<identifier class="java.lang.String"><![CDATA[3b9592e8-c9d7-4e83-a2b6-9bebec1ea955]|http://forums.oracle.com/forums/]></identifier>
<schemaName><![CDATA[FUSION]|http://forums.oracle.com/forums/]></schemaName>
<type><![CDATA[TABLE]|http://forums.oracle.com/forums/]></type>
</parent>
<schemaName><![CDATA[FUSION]|http://forums.oracle.com/forums/]></schemaName>
<type><![CDATA[COLUMN]|http://forums.oracle.com/forums/]></type>
</partitionColumn>
</partitionColumns>
*<partitionType>RANGE</partitionType>*
<partitions>
<partition>
<ID class="oracle.javatools.db.IdentifierBasedID">
<name><![CDATA[AG_ZERO]|http://forums.oracle.com/forums/]></name>
<identifier class="java.lang.String"><![CDATA[3a8e802d-41eb-4fc5-bac6-853fb54c0864]|http://forums.oracle.com/forums/]></identifier>
<parent class="oracle.javatools.db.IdentifierBasedID">
<name><![CDATA[PARTITION]|http://forums.oracle.com/forums/]></name>
<identifier class="java.lang.String"><![CDATA[8dd284eb-9b8a-4eb9-9f35-2f05b1911094]|http://forums.oracle.com/forums/]></identifier>
<parent class="oracle.javatools.db.TemporaryObjectID">
</parent>
<schemaName><![CDATA[FUSION]|http://forums.oracle.com/forums/]></schemaName>
<type><![CDATA[PARTITION MODEL]|http://forums.oracle.com/forums/]></type>
</parent>
<schemaName><![CDATA[FUSION]|http://forums.oracle.com/forums/]></schemaName>
<type><![CDATA[PARTITION]|http://forums.oracle.com/forums/]></type>
</ID>
<name><![CDATA[AG_ZERO]|http://forums.oracle.com/forums/]></name>
<compression><![CDATA[NOCOMPRESS]|http://forums.oracle.com/forums/]></compression>
<objectType>PARTITION</objectType>
<partitionType>RANGE</partitionType>
<values>
<value class="java.lang.String"><![CDATA[1]|http://forums.oracle.com/forums/]></value>
</values>
</partition>
</partitions>

Partitioning the table ...

I have procedure which inserts the data based on sysdate (everyday). I have partitioned the table using partition by list i have created 31 partitions on this table.
say for example if tis 8th of sep then the partition will be xyz_08 and tommorow will be xyz_09 similarly i have 31 partitions.
I was trying to insert manually by changing sys dates for example like sysdate -1, sysdate -2, sysdate -3 and so on. And it worked absolutely fine
My requirement :- is once its reaches to 31st partition then it has to drop the 1st partition and so on it continues by droping old partitions everyday once its inserted with the latest partition.
my questions
- how do incorporate a logic of adding partitions everyday ?
- how to drop the oldest partition(1st partition ) when it reaches the 31 partition ?
- do i need to use cursors and for loop to archive this both above tasks ?
Any logic with example would be great. Sample code will be wonderful ??
Thank you so much i appreciate it. !!!

user642297 wrote:
let me share my code how i am implementing the partition by list ...Please use the *\* tag before and after a sample code block (or database output) that you post. This formats the code properly (as predefined text output) and is a lot easier on the eye to read. (yes - copy the tag exactly as you see it here and paste it into your posting).
In my previous posting i mentioned about the droping the partition. But thats not the right way i guess. Because if i drop the partition then the data will not be loaded in the same partition next time since that partition will be dropped.
The best way would be truncating the partition i guess. so next time we can load the data in the same partition ....
Correct. You can simply truncate the partition to empty it and ready if for a new data set. However, as already mentioned, a range partition and not a list partition may be more suitable.
One of the great features of partitioning is called +partition pruning+. This means Oracle, at run-time, figures out what partitions to use, and what partitions to ignore, for a specific SQL query. As the data is date based. it makes more sense to use a date range partition - this allows pruning to happen when you look for data for a specific date or date range. With a list partition, you need to use the list column as is as a predicate... and it will be unusual to construct queries that only look at the day number and not as the date as a whole.
few more questions
- if i drop the table, will partitions will also be dropped automatically ? or do i need to explicitly drop the partitions before dropping the table ?
Yes. Partitions is part of the table (these are physical storage containers for the data). Drop the table. Partitions gone.
- how would i drop all the partitions at once ???
By dropping the table. You cannot drop all partitions either - at least one partition must remain behind as a table needs a "+storage container+". It cannot be a table without a means of storing the data inserted into the table somewhere.
i know i can use ALTER TABLE TABLE_NAME DROP PARTITION PARTITION_NAME. This only drops the particular partition but not all the partitions right????
Correct.

Find the partition for the fact table

Oracle version : Oracle 10.2
I have one fact table with daily partitions.
I am inserting some test data in this table for old date 20100101.
I am able to insert this record in this table as below
insert into fact_table values (20100101,123,456);
However I observed that the partition for this date does not exist in the table (all_tab_partitions) morever I am not able to select the data using
select * from facT_table partition(d_20100101)
but I am able to extract the data using
select * from facT_table where date_id=20100101
could some one please let me know the way to find the partition in which this data might be inserted
and if the partition for date 20100101 is not present then why insert for that date is working ?

user507531 wrote:
However I observed that the partition for this date does not exist in the table (all_tab_partitions) morever I am not able to select the data using
select * from facT_table partition(d_20100101)Wrong approach.
but I am able to extract the data using
select * from facT_table where date_id=20100101Correct approach.
could some one please let me know the way to find the partition in which this data might be inserted
and if the partition for date 20100101 is not present then why insert for that date is working ?Who says that the date is invalid..? This is a range partition - which means that each partition covers a range. And if you bothered to read up in the SQL Reference Guide on how a range partition is defined, you will notice that each partition is defined with the end value of the range it covers. There is no start value - as the previous partition's end value is the "+border+" between this and the prior partition.
I suggest that before you use a database feature you first familiarise yourself with it. Else incorrectly using it, and making the wrong assumptions about it, more than likely results.

I have partitioned my tables, do I need to rebuild the indexes of the table

Hello,
I have partition very huge tables, by using rage partition method. After that few queries taking more time than before. Does the old indexes needs to rebuild?
Thanks

929941 wrote:
Hello,
I have partition very huge tables, by using rage partition method. After that few queries taking more time than before. Does the old indexes needs to rebuild?
ThanksWhat do you think?
By the way, how did you partition existing tables? Did you use dbms_redefinition, or did you use CTAS, or some other method?
I love RAGE partitions. You should always always partition your rage.

Truncating old partitions in the table.

Similar Messages

Maybe you are looking for