We can create the index before creating the primary key.

最新推荐文章于 2025-12-12 11:13:55 发布

最新推荐文章于 2025-12-12 11:13:55 发布 · 77 阅读

文章标签：

本文探讨了Oracle数据库中主键与其关联索引之间的关系。通过实例演示了如何创建表并设置主键，解释了为何无法直接删除与主键关联的索引。此外，还介绍了在保留索引的情况下移除主键约束的方法。

Our system encourter a big index contention then we found the index is created by the primary key.

then we think about if we can remove the index instead of keeping the primary key if the index is not used by any query.

but we find it is impossiable.

We can create the index before creating the primary key.
As we Know the index will be created at same time when we create the primary key.
But we can create the index maually before creating the primary key.
This is helpful when the index is big.
We can compress ,parallel option etc.

See the example as below.

$ sqlplus / as sysdba

SQL*Plus: Release 10.2.0.3.0 - Production on Tue Nov 30 02:20:26 2010

Connected to:

Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production

With the Partitioning, Real Application Clusters, Oracle Label Security, OLAP and Data Mining options

SQL> create table t as select * from all_objects;

Table created.

SQL> alter table t add constraint pk_t primary key (OBJECT_ID);

Table altered.

The index is created at same time and also named as pk_t.

SQL> set autotrace trace exp

SQL> select count(*) from t;

Execution Plan

----------------------------------------------------------

-----------------------------------------------------------

-----------------------------------------------------------

| 0 | SELECT STATEMENT | | 1 | 38 (8)|

| 1 | SORT AGGREGATE | | 1 | |

| 2 | INDEX FAST FULL SCAN| PK_T | 36063 | 38 (8)|

-----------------------------------------------------------

SQL> set autotrace off;

SQL> select CONSTRAINT_NAME,INDEX_NAME from dba_constraints where TABLE_NAME='T';

CONSTRAINT_NAME INDEX_NAME
------------------------------ ------------------------------
PK_T PK_T

SQL> drop index PK_T;

drop index PK_T

ERROR at line 1:

ORA-02429: cannot drop index used for enforcement of unique/primary key

The index and constraint are coupled. You can not drop the index but have the constraint.

But you can drop the constraint while have the index with the following command.

SQL> alter table t drop constraint PK_T keep index;

Table altered.

SQL> set autotrace trace exp

SQL> select count(*) from t;

Execution Plan

----------------------------------------------------------

-----------------------------------------------------------

-----------------------------------------------------------

| 0 | SELECT STATEMENT | | 1 | 38 (8)|

| 1 | SORT AGGREGATE | | 1 | |

| 2 | INDEX FAST FULL SCAN| PK_T | 36063 | 38 (8)|

-----------------------------------------------------------

SQL> alter table t add constraint pk_t2 primary key (OBJECT_ID);

Table altered.

SQL> select count(*) from t;

Execution Plan

----------------------------------------------------------

-----------------------------------------------------------

-----------------------------------------------------------

| 0 | SELECT STATEMENT | | 1 | 38 (8)|

| 1 | SORT AGGREGATE | | 1 | |

| 2 | INDEX FAST FULL SCAN| PK_T | 36063 | 38 (8)|

SQL> set autotrace off;

SQL> select CONSTRAINT_NAME,INDEX_NAME from dba_constraints where TABLE_NAME='T';

CONSTRAINT_NAME INDEX_NAME
------------------------------ ------------------------------
PK_T2 PK_T

SQL> drop index PK_T;

drop index PK_T

ERROR at line 1:

ORA-02429: cannot drop index used for enforcement of unique/primary key

SQL> alter table t drop constraint PK_T;

alter table t drop constraint PK_T

ERROR at line 1:

ORA-02443: Cannot drop constraint - nonexistent constraint

SQL> alter table t drop constraint PK_T2;

Table altered.

If we used this command then the index PK_T was dropped with the constrain PK_T2.

That was to say the constraint PK_T2 associated with index PK_T automitically.