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.

相关推荐
oioihoii1 天前
从“功能实现”到“深度优化”:金仓数据库连接条件下推技术的演进之路
数据库·oracle
一个处女座的程序猿O(∩_∩)O1 天前
性能调优实战:金仓数据库连接条件下推原理与案例拆解
数据库·oracle
oioihoii1 天前
数据库查询优化中的谓词下推策略与成本感知优化实践
服务器·数据库·oracle
正在走向自律1 天前
Oracle 替换工程实践深度解析 —— 从技术落地到生产级平稳迁移
数据库·oracle·国产化替代·金仓kingbasees
xcLeigh1 天前
从 Oracle RAC 到金仓高可用集群:平滑切换的架构对比与落地指南
数据库·oracle·架构·集群·数据清洗·kingbasees
zxrhhm1 天前
Oracle一般而言standby redo日志文件组数要比primary数据库的online redo日志文件组数至少多一个,为什么?
数据库·oracle
颜颜yan_1 天前
告别“子查询性能陷阱“:金仓数据库智能下推优化器的设计与实测
数据库·oracle
A10169330712 天前
QT数据库(三):QSqlQuery使用
数据库·qt·oracle
执笔画情ora2 天前
Postgresql数据库管理-pg_xact
数据库·postgresql·oracle
XDHCOM2 天前
ORA-32152报错咋整啊,数据库操作遇到null number问题远程帮忙修复
服务器·数据库·oracle