Issues in using exchange partition

Hi,
I have some issues. Please give me a solution friends!!!!
I have two tables. One table (name as 'A') is partitioned another one(like table name 'B') is not partitioned but have unique index. I am going to exchange the data from B to A. That time B tables's index is moved to unusable state. Can u please help to resolve this. Is ther any option except using Alter index rebuild option.
Thanks in advance..

Wrong forum, this is for Oracle REST Data Services.

Similar Messages

How to use Exchange partition

Hi All,
I have a requirement like .. i have to insert the data from partition table to unpartition table like temp table. by googling i came to know about Exchange partition. by using Exchange partition we can dump temp table to partition table but i don't know how to copy the data from partition table to temp table. following script am using.
ALTER TABLE abc_partition
EXCHANGE PARTITION P_2011_1115 WITH TABLE abc_tmp
INCLUDING INDEXES
WITHOUT VALIDATION;
And again i have created a partition table and i ran below query
ALTER TABLE abc_tmp
EXCHANGE PARTITION P_2011_1115 WITH TABLE abc_partition
INCLUDING INDEXES
WITHOUT VALIDATION;
but i was getting an error like partition ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered table
Thanks
Sree
Edited by: 874823 on Apr 30, 2012 2:01 AM

In that case, you need to follow these basic steps.
1. Use a CTAS (Create Table as Select) to create the staging table. This table's structure needs to match that of the partition table - be that a hash or index organised structure. The columns need to be in the same order, and of the same data type. Not null constraints need to be applied to the applicable columns. If you have manually set storage clauses (e.g. PCTFREE for example) for the partition table, the same needs to be applied to the staging table.
A CTAS would look something as follows:
create table staging_table(
col1 not null,
col2 null,
col3 null
) nologging as
select
some_col,
some_other_column,
third_column
from some_other_data2. The next step is to add the required indexes to the staging table - as that table needs to match the structure of the partitioned table. So the staging table needs to have the same index structures as local partition indexes of the partition table.
3. The actual partition exchange can now happen. The data is not actually exchanged. Ownership of the data changes. The data blocks (for data and indexes) owned by the staging table, is now owned by that partition in the partition table. Likewise the staging table now owns the data and indexes of the partition.
4. The last step is cleaning up - dropping and purging the staging table (assuming that you no longer have a need for it).
The above steps can be fully automated (for any partition table) by developing a generic PL/SQL interface library that performs these steps. Additional features such as parallel processing and tablespaces to use for the staging table and indexes can also considered for such a PL/SQL interface.

ORA-02266: unique/primary keys - error while using Exchange Partition

Hi All,
While using EXCHANGE PARTITION statement as given below,
ALTER TABLE SOURCE_TABLE EXCHANGE PARTITION PRT_EXCG_PRTN WITH TABLE TARGET_TABLE
we are getting this error,
ORA-02266: unique/primary keys in table referenced by enabled foreign keys
However, there are no tables have foreign keys referring this TARGET_TABLE, we checked this by referring
USER_CONSTRAINTS table, it has only primary key and NOT NULL constraints.
SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME like 'TARGET_TABLE';
We are using the following version,
Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
PL/SQL Release 9.2.0.6.0 - Production
CORE 9.2.0.6.0 Production
TNS for IBM/AIX RISC System/6000: Version 9.2.0.6.0 - Production
NLSRTL Version 9.2.0.6.0 - Production
Is it due to any error in our end or it could be a bug in Oracle and should we go for any patch updation ?
Please guide us to resolve this error as soon as possible, thank you.
Regards,
Deva

*** Duplicate Post ***
Please Ignore.

How to use "exchange partition" as performance trick?

Hi,
having a partitioned table in Oracle 10g release 2, I am searching for a performant to reload partitions completely.
I heard about the possibility to load the new data (== complete partition which shall replace existing partition data) completely into a temporary partition and then just to exchange the partitions (throw away the old one and replace it with the new one). This (I was told - and it sounds good to me) is a most performant way of updating the complete data of one partition.
Yet it is unclear to me how to load the new data (which automatically would be inserted in the partition which it shall replace).
So is this possibility existing at all?
Any link to an example?
Best regards from sunny Black Forrest,
Mattin

Hi Martin,
the procedere would be something like
create table tmp_berichtswerte as select * from berichtswerte where 1=0;
Populate the temp table
alter table berichtswerte exchange partition brw_p200109 with table tmp_berichtswerte;
Rebuild the indexes on that partition (and the global indexes on the table)P.S. Sunny? Right now? your are kidding!

Oracle Exchange partition feature not working as expected?

I used the Exchange Partition feature to swap segments between 2 tables- one Partitioned, and one Non-Partitioned. The exchange went well. However, all the data in the partitioned table has gone to the partition which stores the maxbound values.
Any ideas if this is the default behavior or have i missed out something?
/** actual table names changed due to client confidentiality issues */
-- Drop the 2 intermediate tables if they already exist
drop table ordered_inv_bkp cascade constraints ;
drop table ordered_inv_t cascade constraints ;
1st create a Non-Partitioned Table from ORDERED_INV and then add the primary key and unique index(s):
create table ordered_inv_bkp as select * from ordered_inv ;
alter table ordered_inv_bkp add constraint ordinvb_pk primary key (ordinv_id) ;
create unique index ordinv_scinv_uix on ordered_inv_bkp(
SCP_ID ASC,
INV_ID ASC,
ANATLOC_ID ASC,
SOI_ID ASC,
CANCEL_TS ASC );
-- Next, we have to create a partitioned table ORDERED_INV_T with a similar
-- structure as ORDERED_INV.
-- This is a bit tricky, and involves a pl/sql code
declare
l_dt_start DATE;
l_ptn VARCHAR2(50);
cnt PLS_INTEGER;
l_cnt_initial PLS_INTEGER;
ts_name VARCHAR2(50);
l_sql VARCHAR2(10000);
ts_indx VARCHAR2(100);
l_num_errors NUMBER ;
l_num_errors_ok NUMBER ;
l_user_name VARCHAR2(50) ;
l_sysdate VARCHAR2(50);
l_cnt_script PLS_INTEGER ;
BEGIN
SELECT COUNT(*) INTO cnt FROM user_TABLES
WHERE TABLE_NAME='ORDERED_INV_T';
IF cnt=0 THEN
l_sql:= 'CREATE TABLE ORDERED_INV_T
PARTITION BY RANGE (ORDINV_TIME)
( PARTITION TP_ORDINV_MAX VALUES LESS THAN (MAXVALUE)
TABLESPACE TEST_TPT_DATA
ENABLE ROW MOVEMENT
AS SELECT * FROM ORDERED_INV WHERE 1=0 ';
EXECUTE IMMEDIATE l_sql;
-- Add section to set default values for the intermediate table OL_ORDERED_INV_T
FOR crec_cols IN (
SELECT u.column_name ,u.nullable, u.data_default,u.table_name
FROM USER_TAB_COLUMNS u WHERE
u.table_name ='ORDERED_INV' AND
u.data_default IS NOT NULL )
LOOP
l_sql:= 'ALTER TABLE ORDERED_INV_T MODIFY '||crec_cols.column_name||' DEFAULT '||crec_cols.data_default;
-- dbms_output.put_line('chk data default => ' || l_sql) ;
EXECUTE IMMEDIATE l_sql;
END LOOP;
END IF;
-- Split partition to create more partitions
select TO_CHAR(SYSDATE,'YYYY-MM-DD HH24:MI:SS') into l_sysdate from dual;
DBMS_OUTPUT.PUT_LINE ('Finding oldest value at ' || l_sysdate) ;
EXECUTE IMMEDIATE 'SELECT NVL(TRUNC(MIN(OL_ORDINV_TIME),''MONTH''),TRUNC(SYSDATE,''MONTH''))
FROM ORDERED_INV' INTO l_dt_start;
select TO_CHAR(SYSDATE,'YYYY-MM-DD HH24:MI:SS') into l_sysdate from dual;
DBMS_OUTPUT.PUT_LINE ('Started creating partitions at ' || l_sysdate) ;
LOOP
EXIT WHEN l_dt_start > ADD_MONTHS(TRUNC(SYSDATE,'MONTH'),1);
l_ptn:='tp_ordinv_'|| TO_CHAR(l_dt_start,'YYYYMM');
l_sql:= 'ALTER TABLE ORDERED_INV_T
split partition TP_ORDINV_MAX at (TO_DATE('''|| TO_CHAR(ADD_MONTHS(l_dt_start,12),'YYYYMM') ||''',''YYYYMM''))
into ( partition '||l_ptn||' , partition TP_ORDINV_MAX)';
execute immediate l_sql;
l_dt_start:=add_months(l_dt_start,12);
END LOOP;
END;
-- Also, add indexes to this table
alter table ORDERED_INV_T add constraint ordinvt_pk primary key (ordinv_id) ;
create unique index ordinvt_uix on ordered_inv_t(
SCP_ID ASC,
INV_ID ASC,
ANATLOC_ID ASC,
SOI_ID ASC,
CANCEL_TS ASC );
-- Next, use exchange partition for actual swipe
-- Between ordered_inv_t and ordered_inv_bkp
-- Analyze both tables : ordered_inv_t and ordered_inv_bkp
BEGIN
DBMS_STATS.GATHER_TABLE_STATS(OWNNAME => 'HENRY220', TABNAME => 'ORDERED_INV_T');
DBMS_STATS.GATHER_TABLE_STATS(OWNNAME => 'HENRY220', TABNAME =>'ORDERED_INV_BKP');
END;
SET TIMING ON;
ALTER TABLE ordered_inv_t
EXCHANGE PARTITION TP_ORDINV_MAX
WITH TABLE ordered_inv_bkp
WITHOUT VALIDATION
UPDATE GLOBAL INDEXES;
-- Check query :
select partition_name, num_rows, high_value from user_tab_partitions where table_name = 'ORDERED_INV_T' ;
These are the results:
TP_ORDINV_199801 0 TO_DATE(' 1999-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_199901 0 TO_DATE(' 2000-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_200001 0 TO_DATE(' 2001-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_200101 0 TO_DATE(' 2002-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_200201 0 TO_DATE(' 2003-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_200301 0 TO_DATE(' 2004-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_200401 0 TO_DATE(' 2005-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_200501 0 TO_DATE(' 2006-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_200601 0 TO_DATE(' 2007-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_200701 0 TO_DATE(' 2008-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_200801 0 TO_DATE(' 2009-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_200901 0 TO_DATE(' 2010-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_201001 0 TO_DATE(' 2011-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_201101 0 TO_DATE(' 2012-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_201201 0 TO_DATE(' 2013-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')
TP_ORDINV_MAX 24976 MAXVALUE
Pay attention to the last record

>
used the Exchange Partition feature to swap segments between 2 tables- one Partitioned, and one Non-Partitioned. The exchange went well. However, all the data in the partitioned table has gone to the partition which stores the maxbound values.
>
That isn't possible. The data in the partition before the exchange could only have gone to the non-partitioned table.
Please edit you post and add \ tags on the lines before and after your code to preserve formatting. See the FAQ for details.

Re: exchange partition on weekly partition

We have divided month in 4 week partitions Week 1 start from date 2 to 8, Week2 start from 9 to 15, Week3 start from 16 to 22 and Week4 start from 23 to 1st of coming month.
Tables has huge data (some tables size in TB). Can exchange partition will work on it or I have to change it to daily partition (with huge data)?
Yes - exchange partition will work on it. As I said above:
EXCHANGE PARTITION just exchanges two 'like' partitions so doesn't care what time period the partitions represent (daily, weekly, monthly, etc).
That allows you to EXCHANGE one 'weekly' partition with a temp table.
But you said you are loading data daily:
We are loading data in our dataware house on daily basis from temp to stage and fact tables through insert command
So you don't have a weeks worth of data to exchange; you have a 'days' worth of data. That can only be EXCHANGED with a partition that is intended to hold a days worth of data.
If you are manually adding partitions to your current table then just begin manually add DAILY partitions instead of adding weekly ones. Then you can do a simple daily EXCHANGE to load the data.
Or you could REDEFINE your existing table to use daily partitions by just defining partitions that correspond to your existing weekly ones to hold your current data and then daily partitions for your new data.
CREATE TABLE SCOTT.PARTITION_DAILY_TEST
ID NUMBER(10),
MY_DATE DATE
PARTITION BY RANGE (MY_DATE)
INTERVAL( NUMTODSINTERVAL(1,'DAY'))
PARTITION P_201204_WEEK1 VALUES LESS THAN (TO_DATE(' 2012-04-08 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')),
PARTITION P_201204_WEEK2 VALUES LESS THAN (TO_DATE(' 2012-04-16 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')),
PARTITION P_201204_WEEK3 VALUES LESS THAN (TO_DATE(' 2012-04-23 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')),
PARTITION P_201204_WEEK4 VALUES LESS THAN (TO_DATE(' 2012-05-02 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')),
PARTITION P_201205_WEEK1 VALUES LESS THAN (TO_DATE(' 2012-05-08 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
That table definition above defines specific partitions for existing data but tells Oracle to CREATE and USE daily partitions for new data.
Then you can use EXCHANGE PARTITION (via a work tablel) to move data from your current table partitions to the new table partitions.

If you are manually adding partitions to your current table then just begin manually add DAILY partitions instead of adding weekly ones. Then you can do a simple daily EXCHANGE to load the data.
Or you could REDEFINE your existing table to use daily partitions by just defining partitions that correspond to your existing weekly ones to hold your current data and then daily partitions for your new data.
rp0428,
Just for confirmation can we add daily partition instead of weekly in our existing table for future data and current data will remain in weekly partition.

Exchange Partition Usage

Hi,
We store data from the main table by referring other lookup tables and store them temporarily in a Swap table and then
in the end, we move data from here to the Main table using Exchange Partition.
EXECUTE IMMEDIATE('ALTER TABLE TMP_SWAP EXCHANGE PARTITION PRT_TMP_SWAP WITH TABLE MAIN_TABLE');
It is equivalent to Truncating data in the main table and insert data into it by reading from the swap table.
Please tell me, how internally oracle handles "EXCHANGE PARTITION" implementation and how we get better performance
instead of using TRUNCATE and INSERT, thank you.
Regards,
Deva

Hi,
It simply detaches extents/data blocks from the source table and attaches it to the destination table.
This is the reason performance is better than INSERT statement.
Regards
Message was edited by:
Citrus
corrected a typo

Trying to convert Interval Partitioned Table to Range..Exchange Partition..

Requirement:
Replace Interval 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 Interval Partitioned Table to a Range Partitioned Table. Can I do it using EXCHANGE PARTITION. As if I use the conventional way of creating another Range Partitioned table and 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 EXCHANGE requires a non-partitioned, non-clustered table
This is because both the tables are partitioned. So it does not allow me.
If I do instead :
create a non partitioned table for exchanging the data through 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);
-Problem is that all the data goes into MAX Partition.
Even after creating a lot of partitions by Splitting Partitions, still the data is in MAX Partition only.
So:
-- Is it that we can't Replace an Interval Partitioned Table by Range Partitioned Table using EXCHANGE PARTITION. i.e. We will have to do Insert into..
-- We can do it but I am missing something over here.
-- If all the data is in MAX Partition because of "WITHOUT VALIDATION" , can we make it be redistributed in the right kind of range partitions.

You will need to pre-create the partitions in a_range, then exchange them one by one from a to a tmp then then to arange. Using your sample (thanks for proviing the code by the way).
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 existing partitions form a using:
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=GREGORIAYou can then create table a_range with the apporopriate partitions. Note that you may need to create additional partitions in a_range because interval partitioning does not create partitions that it has no data for, even if that leaves "holes" in the partitioning scheme. So, based on the above:
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 plain table to use in the exchanges:
SQL> CREATE TABLE A_tmp (
2     a              NUMBER,
3     CreationDate   DATE);
Table created.and exchange all of the partitions:
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-13John

Receiving Error 550 when using Exchange via another software application.

Here's a good one (and I hope I'm able to explain this correctly)....
I work at a hospital where we have a gym facility that is open to employees and also to the public. We use a client management system called Twin Oaks. This Twin Oaks software has email functionality that uses an Exchange user account to send
group emails out to clients (this avoids the front desk staffers from having to create email distro groups in Outlook to send out mass emails).
I worked with the Twin Oaks support staff to get the email integration set up with our Exchange server (it was an easy process, entering the SMTP server name then a few other basic settings).
Emailing through the Twin Oaks software works, but only to clients who have INTERNAL hospital email addresses. The messages are failing to go out to any client that has an external email address (Error 550 states the address is unavailable).
Twin Oaks' response to this is that we have some type of firewall that is preventing the delivery of these emails to external addresses. This is not the case and I can't seem to find any reason that would prevent the mails from going out. We
can email external addresses direct from the generic account we set up for this purpose, but for some reason, the mails are not going when they are sent through Twin Oaks application.
We are using Exchange Server 2010. I can't find any transport settings or policies that would prevent emails from going to external addresses and am stumped as to why this isn't working.
Has anyone else experienced these types of issues when using Exchange through another software application to send messages?
Any responses would be greatly appreciated!

Hi,
Based on the description, you could send email to external addresses without the Twin Oaks software. However, with the Twin Oaks software, you couldn't send successfully.
For this issue, I recommend you enable message tracking and check whether you could retrieve message tracking log entires when you send emails to external addresses through the Twin Oaks software.
If you couldn't retrieve message these tracking log entires when you send emails to external addresses through the Twin Oaks software, it means that the Exchange server is OK and the crux of the problem is the Twin Oaks software.
Here is an article about message tracking log for your reference.
Get-MessageTrackingLog
http://technet.microsoft.com/en-us/library/aa997573(v=exchg.141).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Problem exchanging partitions using range partitioning

I have a range-partitioned table. Here's a cut down version....
CREATE TABLE MY_TABLE
   (     VALUE           NUMBER,
     PARTITION_KEY      NUMBER
PARTITION BY RANGE ("PARTITION_KEY")
(PARTITION "P1" VALUES LESS THAN (2),
PARTITION "P2" VALUES LESS THAN (3),
PARTITION "P3" VALUES LESS THAN (4),
PARTITION "P4" VALUES LESS THAN (5),
PARTITION "P5" VALUES LESS THAN (6),
PARTITION "P6" VALUES LESS THAN (7),
PARTITION "P7" VALUES LESS THAN (8));For the process I'm working on, I want to be able to:
- create a table as a copy of one of the partitions
- do some processing on that table
- exchange the updated table back into the partitioned table
I can achieve this as follows....
CREATE TABLE MY_TABLE_COPY_P7 AS (SELECT * FROM MY_TABLE WHERE PARTITION_KEY = 7);
... do processing ...
ALTER TABLE MY_TABLE DROP PARTITION P7;
ALTER TABLE MY_TABLE ADD PARTITION P7 VALUES LESS THAN (8);
ALTER TABLE MY_TABLE EXCHANGE PARTITION P7 WITH TABLE MY_TABLE_COPY INCLUDING INDEXES;However, this only works if the partition I'm adding back in is the highest partition.
If I try do take out one of the middle partitions, then add it back I get an error:
SQL] ALTER TABLE MY_TABLE ADD PARTITION P5 VALUES LESS THAN (6);
ALTER TABLE MY_TABLE ADD PARTITION P5 VALUES LESS THAN (6)
ERROR at line 1:
ORA-14074: partition bound must collate higher than that of the last partitionAny ideas on how I can exchange one of the middle partitions with having to first drop the higher ones?
Btw, I have to use range partitioning as we're using spatial, which only supports range partitioning.
Cheers,

Actually, you can do the exchange partition thing with 8i and over. After creating my_table from your script, I did:
SQL> INSERT INTO my_table VALUES (1,7.5);
1 row created.
SQL> INSERT INTO my_table VALUES (2, 7.2);
1 row created.
SQL> INSERT INTO my_table VALUES (3,7.7);
1 row created.
SQL> CREATE TABLE my_tab_tmp AS
2 SELECT * FROM my_table
3 WHERE 1=2;
Table created.
SQL> ALTER TABLE my_table EXCHANGE PARTITION P7 WITH TABLE my_tab_tmp;
Table altered.
SQL> SELECT * FROM my_tab_tmp;
     VALUE PARTITION_KEY
         1           7.5
         2           7.2
         3           7.7
SQL> SELECT * FROM my_table;
no rows selected
SQL> UPDATE my_tab_tmp
2 set value = value * 20;
3 rows updated.
SQL> COMMIT;
Commit complete.
SQL> ALTER TABLE my_table EXCHANGE PARTITION P7 WITH TABLE my_tab_tmp;
Table altered.
SQL> SELECT * FROM my_tab_tmp;
no rows selected
SQL> SELECT * FROM my_table;
     VALUE PARTITION_KEY
        20           7.5
        40           7.2
        60           7.7You will, of course, need to re-build any global indexes on my_table.
When you first create my_tab_tmp, you should also create indexes to match any local indexes on the partitions, then do the exchange partition using the INCLUDING INDEXES clause. You could also skip creating the indexes and then re-create them after exchanging the updated table with the partition.
Note that none of this will work if you are changing values of partition_key so thatthey fall out of the range for the partition.
HTH
John

Issue while using SUBPARTITION clause in the MERGE statement in PLSQL Code

Hello All,
I am using the below code to update specific sub-partition data using oracle merge statements.
I am getting the sub-partition name and passing this as a string to the sub-partition clause.
The Merge statement is failing stating that the specified sub-partition does not exist. But the sub-partition do exists for the table.
We are using Oracle 11gr2 database.
Below is the code which I am using to populate the data.
declare
ln_min_batchkey PLS_INTEGER;
ln_max_batchkey PLS_INTEGER;
lv_partition_name VARCHAR2 (32767);
lv_subpartition_name VARCHAR2 (32767);
begin
FOR m1 IN ( SELECT (year_val + 1) AS year_val, year_val AS orig_year_val
FROM ( SELECT DISTINCT
TO_CHAR (batch_create_dt, 'YYYY') year_val
FROM stores_comm_mob_sub_temp
ORDER BY 1)
ORDER BY year_val)
LOOP
lv_partition_name :=
scmsa_handset_mobility_data_build.fn_get_partition_name (
p_table_name => 'STORES_COMM_MOB_SUB_INFO',
p_search_string => m1.year_val);
FOR m2
IN (SELECT DISTINCT
'M' || TO_CHAR (batch_create_dt, 'MM') AS month_val
FROM stores_comm_mob_sub_temp
WHERE TO_CHAR (batch_create_dt, 'YYYY') = m1.orig_year_val)
LOOP
lv_subpartition_name :=
scmsa_handset_mobility_data_build.fn_get_subpartition_name (
p_table_name => 'STORES_COMM_MOB_SUB_INFO',
p_partition_name => lv_partition_name,
p_search_string => m2.month_val);
                    DBMS_OUTPUT.PUT_LINE('The lv_subpartition_name => '||lv_subpartition_name||' and lv_partition_name=> '||lv_partition_name);
IF lv_subpartition_name IS NULL
THEN
                         DBMS_OUTPUT.PUT_LINE('INSIDE IF => '||m2.month_val);
INSERT INTO STORES_COMM_MOB_SUB_INFO T1 (
t1.ntlogin,
t1.first_name,
t1.last_name,
t1.job_title,
t1.store_id,
t1.batch_create_dt)
SELECT t2.ntlogin,
t2.first_name,
t2.last_name,
t2.job_title,
t2.store_id,
t2.batch_create_dt
FROM stores_comm_mob_sub_temp t2
WHERE TO_CHAR (batch_create_dt, 'YYYY') = m1.orig_year_val
AND 'M' || TO_CHAR (batch_create_dt, 'MM') =
m2.month_val;
ELSIF lv_subpartition_name IS NOT NULL
THEN
                    DBMS_OUTPUT.PUT_LINE('INSIDE ELSIF => '||m2.month_val);
MERGE INTO (SELECT *
FROM stores_comm_mob_sub_info
SUBPARTITION (lv_subpartition_name)) T1 --> Issue Here
USING (SELECT *
FROM stores_comm_mob_sub_temp
WHERE TO_CHAR (batch_create_dt, 'YYYY') =
m1.orig_year_val
AND 'M' || TO_CHAR (batch_create_dt, 'MM') =
m2.month_val) T2
ON (T1.store_id = T2.store_id
AND T1.ntlogin = T2.ntlogin)
WHEN MATCHED
THEN
UPDATE SET
t1.postpaid_totalqty =
(NVL (t1.postpaid_totalqty, 0)
+ NVL (t2.postpaid_totalqty, 0)),
t1.sales_transaction_dt =
GREATEST (
NVL (t1.sales_transaction_dt,
t2.sales_transaction_dt),
NVL (t2.sales_transaction_dt,
t1.sales_transaction_dt)),
t1.batch_create_dt =
GREATEST (
NVL (t1.batch_create_dt, t2.batch_create_dt),
NVL (t2.batch_create_dt, t1.batch_create_dt))
WHEN NOT MATCHED
THEN
INSERT (t1.ntlogin,
t1.first_name,
t1.last_name,
t1.job_title,
t1.store_id,
t1.batch_create_dt)
VALUES (t2.ntlogin,
t2.first_name,
t2.last_name,
t2.job_title,
t2.store_id,
t2.batch_create_dt);
END IF;
END LOOP;
END LOOP;
COMMIT;
end;
Much appreciate your inputs here.
Thanks,
MK.
(SORRY TO POST THE SAME QUESTION TWICE).
Edited by: Maddy on May 23, 2013 10:20 PM

Duplicate question

How do I stop receiving calendar invites on iCal/iCloud and use exchange 2013 calendar instead?

I Have an exchange 2013 email account which isn't registered as part of my iCloud account.
i Use my outlook calendar (exch) for work and the same exch calendar day to day from all my iOS devices.
when a colleague or outside email away from my company sends me a calendar meeting request, it works fine. (Using my exch email as the invite recipient).
my girlfriend sends me a meeting request from her hotmail account using the same exch email address for me, but he. Invites always arrive to my iCloud/iCal calendar instead! I can't seem to change it so I often miss diary notes or reminders unless I constantly look at both calendars.
i Just want to use exchange calendar and lose iCal (or if easier sync both iCal and exchange calendars vica versa - but that may be over complicating the issue, basically I just need one calendar and would rather it be my outlook exchange cal)
any ideas?

Hello again,
False alarm..... it didnt work sorry.
I removed the iCal accounts from my mac, and also from my iphone. Then when my partner sent me a calendar invite it simply didnt arrive at all!
She has a hotmail account installed on her IOS iphone 5.
She is sending the invite to my exch 2013 email address which is not associated with any icloud account.
My exch 2013 email is installed in both my Outlook for mac 2011 and IOS device Iphone 5s.
When I switch the iCloud Calendar back on in my iphone 5s, the invite comes through but ONLY optional to the icloud calendar. I cannot seem to get it receiving on my default calendar which is set to Exchange 2013 account.
Its very strange as its only her invites that do this. Anyone else's come through on my exchange calendar because its the same email address receeving it my end.

Google apps doesn't connect using exchange option in mail while on 3G

Hello,
I have been using google apps for over two years and it has been working perfectly on my iPhone. I set up my email using the exchange option and its been running without incident. I also have my gmail setup using exchange and it too has been working fine for years. About 2 months ago I had my iPhone 5 replaced by apple under warranty and on the new device I was no longer able to setup my gmail using exchange. I then read that google stopped supporting exchange for new iOS devices. However, my google apps account continued to work perfectly until a few days ago. It suddenly stopped connecting to my account. I did a few experiments and noticed that it works perfectly when connected via wifi or on Edge but not on 3G. It's strange that it just doesn't connect on 3G. To troubleshoot I deleted the account and added it again but that didn't solve the problem. I also restored the phone but that didn't help either. Finally I changed my SIM card and that didn't help too.
Does anyone have any idea why this is and how I can solve this issue?
Regards,
Saeed

buyousuf wrote:
Thanks for the reply. This explains why my gmail account doesn't work using exchange. However, google apps is a paid service and hence should work using exchange.
What did google say when you contacted them? It's their service.
Also, I am able to connect using Edge and wifi but not while on 3G.
Connect to what? Are you saying Google Apps works on Edge, but not 3G? Or are you saying you can't connect to the Internet at all over 3G?

Exchange Partition

Hi,
What happens when :
1. A query is running on a partition table has millions of records.
2. Alter table exchange partition ... issued
Does it completes step (1) first and than it takes (2)step or how it handles? Or will it show wrong result in the query? Please help.

I have a case for the need to exchange partitions between two range partitioned tables. For example table SALES_HIST contains millions of sales records from the last 5 years range partitioned by fiscal year and month.
The need arises to add new columns to the table for the current year and going forward. The new columns are meaningless to prior years so the decision is made to move data older than the prior year to separate tables which should retain the fiscal year/month partitioning for performance.
If we had the ability to exchange partitions between partitioned tables, this would be a simple matter of a series of DDL statements to create the new table(s) and index(es) and then exchange partitions from the current table to the new table. Instead, we are forced to create the table, insert into NEW_TAB /*+ append */ select * from SALES_HIST, alter table sales_hist drop partition, create indexes on new_tab; repeat ad nauseum. And, since the volume of data is huge, we are forced to insert piecemeal else we blow out temp space and drag the system to a crawl.

Materialized view on a Partitioned Table (Data through Exchange Partition)

Hello,
We have a scenario to create a MV on a Partitioned Table which get data through Exchange Partition strategy. Obviously, with exchange partition snap shot logs are not updated and FAST refreshes are not possible. Also, this partitioned table being a 450 million rows, COMPLETE refresh is not an option for us.
I would like to know the alternatives for this approach,
Any suggestions would be appreciated,
thank you

From your post it seems that you are trying to create a fast refresh view (as you are creating MV log). There are limitations on fast refresh which is documented in the oracle documentation.
http://docs.oracle.com/cd/B28359_01/server.111/b28313/basicmv.htm#i1007028
If you are not planning to do a fast refresh then as already mentioned by Solomon it is a valid approach used in multiple scenarios.
Thanks,
Jayadeep

Issues in using exchange partition

Similar Messages

Maybe you are looking for