Exchange Table Subpartition With Data And Its All LOCAL Partition Indexes 子分区

You have a table called TAB1 which is AUTO PARTITION ON A DATE COLUMN and then SUB-PARTITOIN further.

Now you are trying to move data and its sub-partition LOCAL INDEXES from TAB1 to TAB3 using exchange partition.

You have a staging table as TAB2. All three tables TAB1 (main table) , TAB2 (staging table) and TAB3 (history table) have same table structure.

Now the question is Do you have to have same indexes structure with diff name on TAB2 and TAB3 as TAB1? If not then how do to exchange the partition?

SOLUTION

NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

You need to have an index on the exchange table that indexes the same columns as the local index on the partitioned table.

Text: index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION

Cause:

Ensure that the indexes for the two tables have indexes which follow this rule For every non partitioned index for the non partitioned table, there has to be an identical LOCAL index on the partitioned table and vice versa

Here's a testcase you can review

  • drop any objects already created

drop table test_part cascade constraints;

drop table test_exch cascade constraints;

-- create range/list composite partitioned table

CREATE TABLE test_part (

customer_id NUMBER(6),

cust_first_name VARCHAR2(20),

cust_last_name VARCHAR2(20),

nls_territory VARCHAR2(30),

credit_limit NUMBER(9,2))

PARTITION BY RANGE (credit_limit)

SUBPARTITION BY LIST (nls_territory)

SUBPARTITION TEMPLATE

(SUBPARTITION east VALUES ('CHINA', 'JAPAN', 'INDIA', 'THAILAND'),

SUBPARTITION west VALUES ('AMERICA', 'GERMANY', 'ITALY', 'SWITZERLAND'),

SUBPARTITION other VALUES (DEFAULT))

(PARTITION p1 VALUES LESS THAN (1000),

PARTITION p2 VALUES LESS THAN (2500),

PARTITION p3 VALUES LESS THAN (MAXVALUE));

-- create local index on partitions

CREATE INDEX test_part_idx ON test_part(credit_limit, nls_territory)

STORAGE (INITIAL 1M MAXEXTENTS UNLIMITED)

LOCAL

(PARTITION p1,

PARTITION p2,

PARTITION p3

(SUBPARTITION east, SUBPARTITION west, SUBPARTITION other));

-- create the exchange table and index

CREATE TABLE test_exch2 (

customer_id NUMBER(6),

cust_first_name VARCHAR2(20),

cust_last_name VARCHAR2(20),

nls_territory VARCHAR2(30),

credit_limit NUMBER(9,2))

partition by list(nls_territory)

(partition east VALUES ('CHINA', 'JAPAN', 'INDIA', 'THAILAND'),

partition west VALUES ('AMERICA', 'GERMANY', 'ITALY', 'SWITZERLAND'),

partition other VALUES (DEFAULT));

CREATE INDEX test_exch2_idx ON test_exch2 (credit_limit, nls_territory);

alter table test_part exchange partition p1 with table test_exch2;

If you want to exchange out just a single subpartition of a partition (i.e. not the entire partition and all its subpartitions), then do this

-- create exchange table to hold the subpartition

CREATE TABLE test_exch (

customer_id NUMBER(6),

cust_first_name VARCHAR2(20),

cust_last_name VARCHAR2(20),

nls_territory VARCHAR2(30),

credit_limit NUMBER(9,2))

/

CREATE INDEX test_exch_idx ON test_exch (credit_limit, nls_territory);

alter table test_part exchange subpartition P2_OTHER with table test_exch;

Make sure to use without validation, or it will try to validate each row in the exchange table should go into the partition you are trying to put it into , and that takes a long time

Now the question is Do I have to have same indexes structure with diff name on TAB2 and TAB3 as TAB1? If not then how do I exchange the partition?

In your testcase, the index name does have to be different on the exchange table

If you want your local index partitions to be usable after the exchange, you have to use including indexes clause, and you have one index on the exchange table for every local index on tab1 and yes, the index names have to be different.

相关推荐
欢呼的太阳1 小时前
数据库设计Step by Step (10)——范式化
服务器·数据库·oracle
多巴胺梦想家9 小时前
数据库恢复技术:当灾难来临
网络·数据库·oracle
oradh14 小时前
Oracle DG主备架构的基本维护操作总结
数据库·oracle·架构·dg主备架构的基本维护操作总结
Albert Tan14 小时前
Oracle EBS 12.2 Create RFQ
oracle
迷枫71216 小时前
简单sql与dm功能实验记录
数据库·sql·oracle
蚁库16 小时前
Oracle 19c 文件系统安装实战教程:从规划到日常管理完整流程
数据库·oracle
IvorySQL1 天前
IvorySQL Agent 探索与实践
数据库·人工智能·postgresql·oracle·ivorysql
ShiXZ2132 天前
指令集-SQL 常用指令速查手册
数据库·sql·mysql·oracle
许彰午2 天前
从Oracle看MySQL聚簇索引的架构性缺陷与缓解之道
mysql·oracle·架构
AllData公司负责人2 天前
数据集成管理|AIIData数据中台实现MySQL、Hive、Oracle一键接入Doris
大数据·数据库·人工智能·hive·mysql·oracle·数据分析