Preamble
The Oracle NOT condition (also called NOT operator) is used to negate the condition in SELECT, INSERT, UPDATE or DELETE sentences.
Syntax of the NOT condition in Oracle/PLSQL
NOT condition
Parameters and arguments of the condition
- Condition – Condition of denial.
Note:
The Oracle NOT condition requires that the opposite conditions must be met for the entries to be included in the resulting set.
Example of a combination with the IN condition
The Oracle NOT condition can be combined with the IN condition.
For example:
SELECT *
FROM customers
WHERE customer_name NOT IN ( 'IBM', 'Hewlett Packard', 'Microsoft');
In this example, Oracle NOT will return all rows from the customer_name table where customer_name is not IBM, Hewlett Packard, or Microsoft. Sometimes, it is more efficient to list the values that you do not want, as opposed to the values that you want.
Example of a combination with the IS NULL condition
The Oracle NOT condition can be combined with the IS NULL condition.
For example:
SELECT *
FROM customers
WHERE last_name IS NOT NULL;
In this example, Oracle NOT will return all entries from the customer table where last_name does not contain a value of NULL.
Example of a combination with the LIKE condition
The Oracle NOT condition can be combined with the LIKE condition.
For example:
SELECT customer_name
FROM customers
WHERE customer_name NOT LIKE 'S%';
By placing the Oracle NOT operator before the LIKE condition, you can get all records of the customers table whose customer_name values do not start with ‘S’.
Example of combination with the BETWEEN condition
The Oracle NOT condition can also be used with the BETWEEN condition. Below is an example of how to combine the NOT operator with the BETWEEN condition.
For example:
SELECT *
FROM customers
WHERE customer_id NOT BETWEEN 4000 AND 4100;
This Oracle NOT example will return all lines where the customer_id value was not between 4000 and 4100 (inclusive). This would be equivalent to the following Oracle SELECT statement:
SELECT *
FROM customers
WHERE customer_id < 4000
OR customer_id > 4100;
Example of combination of NOT with EXISTS condition
The Oracle NOT condition can also be used with the EXISTS condition.
For example:
SELECT *
FROM suppliers
WHERE DOES NOT EXIST (SELECT *
FROM orders
WHERE suppliers.supplier_id = orders.supplier_id);
This Oracle NOT example will return all rows in the suppliers table where there are no entries in the orders table for the given supplier_id.
Oracle Tutorial: Logical Operator; AND OR NOT Operators
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
How to Achieve Real Estate Cost Transparency with Enteros: AI SQL Analytics and AIOps Platform Intelligence
- 17 February 2026
- Database Performance Management
Introduction Real estate has evolved into a technology-driven industry. From digital property marketplaces and smart building platforms to tenant apps, CRM systems, leasing automation tools, and investment analytics dashboards—modern real estate enterprises depend on complex data ecosystems. Every lease agreement, rent payment, occupancy report, maintenance request, and investor presentation is powered by databases running behind … Continue reading “How to Achieve Real Estate Cost Transparency with Enteros: AI SQL Analytics and AIOps Platform Intelligence”
How to Optimize SaaS Performance and RevOps Efficiency with Enteros: Database Management and Cloud FinOps Intelligence
Introduction The SaaS business model promises scalable growth, recurring revenue, and predictable expansion. But behind every subscription dashboard, billing workflow, in-app analytics panel, and customer success metric lies a powerful—and often overlooked—engine: The database layer. In today’s technology sector, SaaS companies compete on speed, reliability, personalization, and cost efficiency. Every millisecond of latency impacts user … Continue reading “How to Optimize SaaS Performance and RevOps Efficiency with Enteros: Database Management and Cloud FinOps Intelligence”
What Telecom CIOs Should Know About AI SQL, Cost Attribution, and Predictive Cloud FinOps with Enteros
- 16 February 2026
- Database Performance Management
Introduction The telecommunications industry operates at a scale few sectors can match. Billions of call detail records (CDRs).Real-time 5G traffic management.Subscriber billing systems.Network performance analytics.IoT connectivity platforms.Streaming, messaging, roaming, and edge computing services. Behind every one of these services lies a complex, high-volume database ecosystem. And as telecom providers modernize into cloud-native, multi-cloud, and hybrid … Continue reading “What Telecom CIOs Should Know About AI SQL, Cost Attribution, and Predictive Cloud FinOps with Enteros”
How Enteros Combines Generative AI and Database Intelligence to Drive Predictable Revenue Operations Growth
Introduction Revenue Operations (RevOps) has evolved from a coordination function into a strategic growth engine. Modern enterprises rely on tightly integrated sales, marketing, finance, customer success, and product systems to generate predictable revenue. But behind every CRM update, pricing calculation, renewal forecast, pipeline report, and customer usage metric lies a critical foundation: The database layer. … Continue reading “How Enteros Combines Generative AI and Database Intelligence to Drive Predictable Revenue Operations Growth”