Preamble
In this tutorial you will learn how to create an AFTER INSERT trigger (after inserting) in Oracle with syntax and examples.
Oracle executes (excites) the AFTER INSERT trigger after executing the INSERT operator.
Syntax of the AFTER INSERT trigger
CREATE [ OR REPLACE ] TRIGGER name_trigger
AFTER INSERT
ON table_name
[ FOR EACH ROW ]
DECLARE
- variable declaration
BEGIN
- trigger code
EXCEPTION
WHEN ...
- emergency handling
END;
Parameters or arguments
- Trigger_name – The name of the trigger to be created.
- AFTER INSERT – indicates that the trigger is triggered after the INSERT operator is executed.
- table_name – The name of the table for which the Trigger was created.
Restrictions
- You cannot create a trigger in views.
- You cannot update :NEW (new) values.
- You cannot update :OLD (old) values.
Example
Let’s take an example of how to create an AFTER INSERT trigger using the CREATE TRIGGER design.
If you have created a table of the following structure:
CREATE TABLE orders
(order_id number(5),
number(4),
cost_per_item number(6,2),
total_cost number(8,2)
);
Then we’ll create the AFTER INSERT trigger as follows:
CREATE OR REPLACE TRIGGER orders_after_insert
AFTER INSERT
ON orders
FOR EACH ROW
DECLARE
v_username varchar2(10);
BEGIN .
-- Find the person who's running INSERT on the table.
SELECT user INTO v_username
FROM dual;
-- Insert a row in the audit table
INSERT INTO orders_audit
( order_id,
Ah,
cost_per_item,
total_cost,
username )
VALUES
( :new.order_id,
:new.quantity,
:new.cost_per_item,
:new.total_cost,
v_username );
END;
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 Can Telecom Companies Prevent Database Bottlenecks During Mass Service Activations and Provisioning Events?
- 23 September 2026
- Database Performance Management
Telecom companies can avoid database bottlenecks during mass service activations by monitoring SQL performance, provisioning transactions, database waits, locking, resource utilisation, workload spikes and application dependencies. Good telecom service provisioning database performance management allows teams to identify bottlenecks earlier, tune high-impact queries, plan capacity more intelligently, and keep activation workflows humming along during periods of … Continue reading “How Can Telecom Companies Prevent Database Bottlenecks During Mass Service Activations and Provisioning Events?”
How Can Real Estate Platforms Prevent Database Slowdowns During High-Volume Property Searches and Listing Updates?
By continuously monitoring SQL performance, property-search workloads, listing updates, database waits, resource utilisation and unusual workload changes, real estate platforms can avoid database slowdowns. Effective real estate database performance monitoring enables technology teams to identify bottlenecks sooner, optimise high-impact queries, enhance database observability and sustain responsive property search and listing experiences during periods of heavy … Continue reading “How Can Real Estate Platforms Prevent Database Slowdowns During High-Volume Property Searches and Listing Updates?”
How Can Retail IT Teams Improve Database Capacity Planning for Peak Demand?
- 22 September 2026
- Database Performance Management
Retail IT teams can improve retail database capacity planning by analyzing historical workloads, monitoring SQL performance, tracking CPU, memory, storage, connections, and transaction growth, and forecasting future demand. Strong retail database performance management helps teams identify capacity risks before peak events, while Enteros supports proactive planning with observability, anomaly detection, predictive analytics, and workload intelligence. … Continue reading “How Can Retail IT Teams Improve Database Capacity Planning for Peak Demand?”
How Can Telecom Providers Improve Database Scalability for 5G and IoT Growth?
By integrating SQL optimisation, continuous observability, workload monitoring, anomaly detection, capacity planning, and effective cloud resource management, telecom operators can increase the scalability of telecom databases. Infrastructure that can manage quickly increasing device and transaction loads is necessary for robust database performance for 5G networks. Enteros assists telecom teams with capacity forecasting, bottleneck identification, and … Continue reading “How Can Telecom Providers Improve Database Scalability for 5G and IoT Growth?”