Preamble
In this post you will learn how to create, delete, disable, and enable unique constraints in Oracle with syntax and examples.
A unique constraint is a single field or a combination of fields that uniquely define a record. Some of the fields may contain zero values if the combination of values is unique.
- In Oracle, the unique restriction may not contain more than 32 columns.
- The unique restriction can be defined either in the CREATE TABLE operator or in the ALTER TABLE operator.
The difference between a unique constraint and a primary key
Primary key
The fields that are part of the primary key cannot contain a zero value.
Unique limitation
Fields that are part of a unique constraint may contain zero values if the combination of values is unique.
Oracle does not allow you to create both a primary key and a unique constraint with identical columns.
Create a unique constraint using the CREATE TABLE operator
Syntax:
CREATE TABLE table_name
(
column1 datatype [ NULL | NOT NULL ],
column2 datatype [ NULL | NOT NULL ],
…
CONSTRAINT constraint_name UNIQUE (uc_col1, uc_col2, ... uc_col_n)
);
- table_name is the name of the table you want to create.
- column1, column2 – the columns you want to create in the table.
- constraint_name – the name of a unique constraint.
- uc_col1, uc_col2, … uc_col_n – columns that make up the unique constraint.
Let’s consider an example of creating a unique limitation in Oracle using the CREATE TABLE operator.
CREATE TABLE supplier
( supplier_id numeric(10) NOT NULL,
supplier_name varchar2(50) NOT NULL,
contact_name varchar2(50),
CONSTRAINT supplier_unique UNIQUE (supplier_id)
);
In this example, we created a unique supplier_unique restriction for the supplier table. It consists of only one field – the supplier_id field.
We could also create a unique limit with several fields, as in the example below:
CREATE TABLE supplier
( supplier_id numeric(10) NOT NULL,
supplier_name varchar2(50) NOT NULL,
contact_name varchar2(50),
CONSTRAINT supplier_unique UNIQUE (supplier_id, supplier_name)
);
Creation of a unique restriction using the ALTER TABLE operator
Syntax for creating a unique constraint using the ALTER TABLE operator in Oracle:
ALTER TABLE table_name
ADD CONSTRAINT constraint_name UNIQUE (column1, column2, ... column_n);
- table_name is the name of the table to change. This is the table to which you want to add a unique constraint.
- constraint_name is the name of the unique constraint.
- column1, column2, … column_n are the columns that make up the unique constraint.
Let’s consider an example of how to add a unique limitation to an existing table in Oracle using the ALTER TABLE operator.
ALTER TABLE supplier
ADD CONSTRAINT supplier_unique UNIQUE (supplier_id);
In this example, we created a unique limitation for an existing supplier table called supplier_unique. It consists of a field named supplier_id.
We could also create a unique constraint with multiple fields, as in the example below:
ALTER TABLE supplier
ADD CONSTRAINT supplier_name_unique UNIQUE (supplier_id, supplier_name);
Remove unique restriction
Syntax to remove a unique restriction in Oracle:
ALTER TABLE table_name
DROP CONSTRAINT constraint_name;
- table_name is the name of the table to change. This is the table from which you want to remove the unique constraint.
- constraint_name is the name of the unique constraint to be removed.
Let’s consider an example of how to remove a unique limitation from a table in Oracle.
ALTER TABLE supplier
DROP CONSTRAINT supplier_unique;
In this example, we removed the unique supplier_unique restriction for the supplier table.
Disabling the unique constraint
Syntax for disabling a unique restriction in Oracle:
ALTER TABLE table_name
DISABLE CONSTRAINT constraint_name;
- table_name is the name of the table to change. This is the table whose unique constraint you want to disable.
- constraint_name is the name of the unique constraint to disable.
Let’s consider an example of how to disable a unique limitation in Oracle.
ALTER TABLE supplier
DISABLE CONSTRAINT supplier_unique;
In this example, we disabled the unique supplier_unique restriction for the supplier table.
Enabling unique constraint
Syntax to enable a unique limitation in Oracle:
ALTER TABLE table_name
ENABLE CONSTRAINT constraint_name;
- table_name is the name of the table to change. This is the table whose unique constraint you want to enable.
- constraint_name is the name of the unique constraint to enable.
Let’s consider an example of how to enable a unique limitation in Oracle.
ALTER TABLE supplier
ENABLE CONSTRAINT supplier_unique;
In this example, we enable a unique supplier_unique restriction for the supplier table.
WHAT IS UNIQUE KEY CONSTRAINT IN ORACLE SQL?
About Enteros
Enteros offers a patented database performance management SaaS platform. It proactively identifies root causes of complex business-impacting database scalability and performance issues across a growing number of clouds, RDBMS, NoSQL, and machine learning database platforms.
The views expressed on this blog are those of the author and do not necessarily reflect the opinions of Enteros Inc. This blog may contain links to the content of third-party sites. By providing such links, Enteros Inc. does not adopt, guarantee, approve, or endorse the information, views, or products available on such sites.
Are you interested in writing for Enteros’ Blog? Please send us a pitch!
RELATED POSTS
Open Banking APIs: Where Performance = Trust
- 30 October 2025
- Software Engineering
Introduction Open banking promised to be a paradigm shift — enabling consumers to share financial data securely and allowing banks, fintechs, and third parties to build innovative services on that foundation. But as the ecosystem evolves, one truth stands out: it’s not just about access — it’s about performance. An open banking API that’s slow, … Continue reading “Open Banking APIs: Where Performance = Trust”
Enteros for the Travel Industry: Enhancing Cost Estimation Accuracy Through AIOps, Observability, and Cloud FinOps
Introduction In the fast-moving world of travel and hospitality, accurate cost estimation isn’t just a finance issue—it’s a performance challenge. From dynamic booking systems and real-time analytics to backend inventory databases and AI-driven recommendation engines, every operational layer relies on complex data interactions. The travel industry has always faced volatile demand, fluctuating operating costs, and … Continue reading “Enteros for the Travel Industry: Enhancing Cost Estimation Accuracy Through AIOps, Observability, and Cloud FinOps”
Transforming Data Lake Efficiency in the Technology Sector: How Enteros’ AI Performance Platform Redefines Database Optimization
Introduction In today’s data-driven technology landscape, the backbone of innovation lies in how efficiently enterprises manage and utilize their data. With the rise of big data, cloud ecosystems, and AI workloads, data lakes have become the central hub of data intelligence—storing massive volumes of structured, semi-structured, and unstructured data. However, as organizations scale their digital … Continue reading “Transforming Data Lake Efficiency in the Technology Sector: How Enteros’ AI Performance Platform Redefines Database Optimization”
Redefining Healthcare Efficiency: AI-Driven Backlog Prioritization and Capital Expenditure Optimization with Enteros
- 29 October 2025
- Database Performance Management
Introduction The healthcare industry is under constant pressure to balance two competing priorities — improving patient outcomes and managing operational efficiency within constrained budgets. With digital transformation accelerating across hospitals, clinics, and research institutions, vast amounts of data are being generated from electronic health records (EHRs), diagnostic imaging, clinical workflows, and administrative systems. This influx … Continue reading “Redefining Healthcare Efficiency: AI-Driven Backlog Prioritization and Capital Expenditure Optimization with Enteros”