Preamble
Oracle condition REGEXP_LIKE allows to execute regular expressions in WHERE proposal in SELECT, INSERT, UPDATE or DELETE queries.
Syntax for REGEXP_LIKE in Oracle/PLSQL
REGEXP_LIKE ( expression, pattern [, match_parameter ] )
Parameters and arguments of the condition
- expression – a symbolic expression such as a column or a field. These can be the following types of data: VARCHAR2, CHAR, NVARCHAR2, NCHAR, CLOB or NCLOB.
- pattern – Template. Regular expression for comparison. This can be a combination of the following values:
| Meaning | Description |
| ^ |
Corresponds to the beginning of a line. When using match_parameter with ‘m’, it corresponds to the beginning of the string anywhere within the expression.
|
| $ |
Corresponds to the end of the line. When using match_parameter with ‘m’, it corresponds to the end of a line anywhere within the expression.
|
| * | Corresponds to zero or more occurrences. |
| + | Corresponds to one or more occurrences. |
| ? | Corresponds to zero or one entry. |
| . | Corresponds to any character except NULL. |
| | | Used as “OR” to specify more than one alternative. |
| [ ] |
It is used to specify a list of matches where you try to match any of the characters in the list.
|
| [^ ] |
It is used to specify a nonmatching list where you try to match any character except for those on the list.
|
| ( ) | Used for group expressions as subexpressions. |
| {m} | Corresponds m times. |
| {m,} | Matching at least m times. |
| {m,n} | Matching at least m times, but not more than n times. |
| \n | n is a number from 1 to 9. It corresponds to the n subexpression located in ( ) before \n. |
| [..] | Corresponds to a single element mapping, which can be more than one character. |
| [::] | Corresponds to the class of symbols. |
| [==] | Corresponds to the class of equivalence. |
| \d | Corresponds to the digital symbol. |
| \D | Corresponds to a non-digital symbol. |
| \w | Corresponds to the text symbol. |
| \W | Corresponds to a non-text character. |
| \s | Corresponds to the space character. |
| \S | Does not match the space character. |
| \A |
Corresponds to the beginning of a line or corresponds to the end of a line before a new line character.
|
| \Z | Corresponds to the end of the line. |
| *? | Corresponds to the previous pattern of zero or more occurrences. |
| +? | One or more occurrences correspond to the previous pattern. |
| ?? | Corresponds to the previous zero or one entry pattern. |
| {n}? | Corresponds to the previous template n times. |
| {n,}? | Corresponds to the previous template at least n times. |
| {n,m}? | Corresponds to the previous template at least n times, but not more than m times. |
- match_parameter – Optional. This allows to change the compliance behavior for the REGEXP_LIKE condition. This can be a combination of the following values:
| Meaning | Description |
| ‘c’ | Performs case-sensitive matching. |
| ‘i’ | Performs case insensitive matching. |
| ‘n’ |
Allows a character period (.) to match the character of a new string. By default, a metasymic period.
|
| ‘m’ |
The expression assumes that there are several lines where ^ is the beginning of a line and $ is the end of a line, regardless of the position of these characters in the expression. By default, the expression is assumed to be on the same line.
|
| ‘x’ |
Ignored are the symbols of spaces. By default, the space characters are the same as any other character.
|
Note:
The REGEXP_LIKE condition uses an input character set for string evaluation.
If you specify match_parameter as conflict, the REGEXP_LIKE condition will use the last value to break the conflict.
If match_parameter is omitted, the condition REGEXP_LIKE will use case sensitivity as defined by parameter NLS_SORT.
Example of a comparison with more than one alternative
The first Oracle example of the REGEXP_LIKE condition, which we will consider, assumes using the | template.
Let us explain how | template works in Oracle condition REGEXP_LIKE. For example:
SELECT last_name
FROM contacts
WHERE REGEXP_LIKE (last_name, 'Anders(o|e|a)n');
This example REGEXP_LIKE returns all contacts whose last_name is either ‘Anderson’, ‘Andersen’ or ‘Andersan’. The | template indicates that the search should be done with an “o”, “e” or “a”.
Example of matching the beginning
Next, use the condition REGEXP_LIKE to match the beginning of the string. For example:
SELECT last_name
FROM contacts
WHERE REGEXP_LIKE (last_name, '^A(*)');
This example REGEXP_LIKE returns all contacts whose last_name starts with ‘A’.
Example of an end match
Next, use the condition REGEXP_ LIKE to match the end of the line. For example:
SELECT last_name
FROM contacts
WHERE REGEXP_LIKE (last_name, '(*)n$');
This example REGEXP_LIKE will return all contacts whose last_name ends in ‘n’.
Oracle regular expression: regexp like
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
From Network Traffic to Cost Transparency: Enteros Approach to Amortized Cost Management in Telecom
- 12 February 2026
- Database Performance Management
Introduction Telecom operators today are no longer just connectivity providers. They are digital service platforms supporting 5G networks, IoT ecosystems, streaming services, cloud-native core systems, enterprise connectivity, and real-time analytics. Every call, message, streaming session, IoT signal, and digital interaction generates massive volumes of transactional and analytical data. That data is processed, stored, and monetized … Continue reading “From Network Traffic to Cost Transparency: Enteros Approach to Amortized Cost Management in Telecom”
From Transactions to Transparency: Enteros’ AI SQL Platform for Financial Database Performance and Cost Intelligence
Introduction In the financial sector, performance is not optional—it is existential. Banks, insurance providers, capital markets firms, fintech platforms, and payment processors operate in environments where milliseconds matter, compliance is mandatory, and financial transparency is critical. Every transaction—whether it’s a trade execution, loan approval, insurance claim, or digital payment—flows through complex database infrastructures. Yet as … Continue reading “From Transactions to Transparency: Enteros’ AI SQL Platform for Financial Database Performance and Cost Intelligence”
Driving Healthcare RevOps Efficiency with AI SQL–Powered Database Performance Management Software
- 11 February 2026
- Database Performance Management
Introduction Healthcare organizations today operate at the intersection of clinical excellence, regulatory compliance, and financial sustainability. Hospitals, health systems, payer organizations, and healthtech SaaS providers depend on digital platforms to manage electronic health records (EHRs), billing systems, revenue cycle management (RCM), patient portals, telehealth platforms, claims processing engines, and analytics tools. At the core of … Continue reading “Driving Healthcare RevOps Efficiency with AI SQL–Powered Database Performance Management Software”
Retail Revenue Meets Cloud Economics: Enteros AIOps-Driven Approach to Database Cost Attribution
Introduction Retail has become a real-time, data-driven industry. From omnichannel commerce and dynamic pricing engines to inventory optimization, loyalty platforms, recommendation systems, and last-mile logistics, modern retail runs on software—and software runs on databases. As retailers scale their digital presence, they increasingly rely on SaaS platforms, microservices architectures, hybrid cloud infrastructure, and distributed database environments. … Continue reading “Retail Revenue Meets Cloud Economics: Enteros AIOps-Driven Approach to Database Cost Attribution”