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.

相关推荐
山峰哥12 小时前
数据库工程:Explain执行计划对比实战指南‌
数据库·sql·oracle·深度优先·宽度优先
不知疲倦的仄仄12 小时前
ShardingSphere:高效管理数据库集群的终极方案
sql·mysql·oracle·database
韶博雅13 小时前
oracle密码策略检查
数据库·oracle
辰合软件14 小时前
通达OA目录结构与核心文件解析
android·数据库·oracle
忧郁的紫菜1 天前
WCF+JSON+实体对象与WebService+DataSet效率大比拼
数据库·oracle·json
标致的自行车2 天前
Entity Framework之问题收集
jvm·数据库·oracle
spider_xcxc2 天前
Redis 数据库高质量实践指南(一)
运维·数据库·redis·oracle·云计算
落叶-IT2 天前
Java异常处理深度实战教程:异常传播的失败场景分析
数据库·oracle
水木流年追梦3 天前
agent面试必备31- AI Agent 核心进阶:工具路由(Tool Routing)
数据库·人工智能·oracle·面试·职场和发展·embedding
weixin_397574093 天前
框架v5多数据源让AI查遍企业数据
数据库·人工智能·oracle