【转自】http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_7004.htm#i2153503

CREATE TRIGGER

Purpose

Use the CREATE TRIGGER statement to create and enable a database trigger, which is:

• A stored PL/SQL block associated with a table, a schema, or the database or

• An anonymous PL/SQL block or a call to a procedure implemented in PL/SQL or Java

Oracle Database automatically executes a trigger when specified conditions occur.

When you create a trigger, the database enables it automatically. You can subsequently disable and enable a trigger with the DISABLE and ENABLE clause of the ALTER TRIGGER or ALTER TABLE statement.

Prerequisites

Before a trigger can be created, the user SYS must run a SQL script commonly called DBMSSTDX.SQL. The exact name and location of this script depend on your operating system.

• To create a trigger in your own schema on a table in your own schema or on your own schema (SCHEMA), you must have the CREATE TRIGGER system privilege.

• To create a trigger in any schema on a table in any schema, or on another user's schema (schema.SCHEMA), you must have the CREATE ANY TRIGGER system privilege.

• In addition to the preceding privileges, to create a trigger on DATABASE, you must have the ADMINISTER DATABASE TRIGGER system privilege.

If the trigger issues SQL statements or calls procedures or functions, then the owner of the trigger must have the privileges necessary to perform these operations. These privileges must be granted directly to the owner rather than acquired through roles.

Syntax

create_trigger::=

DML_event_clause ::=

referencing_clause::=

Semantics

OR REPLACE

Specify OR REPLACE to re-create the trigger if it already exists. Use this clause to change the definition of an existing trigger without first dropping it.

schema

Specify the schema to contain the trigger. If you omit schema, then Oracle Database creates the trigger in your own schema.

trigger

Specify the name of the trigger to be created.

If a trigger produces compilation errors, then it is still created, but it fails on execution. This means it effectively blocks all triggering DML statements until it is disabled, replaced by a version without compilation errors, or dropped. You can see the associated compiler error messages with the SQL*Plus command SHOW ERRORS.

BEFORE

Specify BEFORE to cause the database to fire the trigger before executing the triggering event. For row triggers, the trigger is fired before each affected row is changed.

Restrictions on BEFORE TriggersBEFORE triggers are subject to the following restrictions:

• You cannot specify a BEFORE trigger on a view or an object view.

• You can write to the :NEW value but not to the :OLD value.

AFTER

Specify AFTER to cause the database to fire the trigger after executing the triggering event. For row triggers, the trigger is fired after each affected row is changed.

Restrictions on AFTER TriggersAFTER triggers are subject to the following restrictions:

• You cannot specify an AFTER trigger on a view or an object view.

• You cannot write either the :OLD or the :NEW value.

INSTEAD OF

Specify INSTEAD OF to cause Oracle Database to fire the trigger instead of executing the triggering event. INSTEAD OF triggers are valid for DML events on views. They are not valid for DDL or database events.

If a view is inherently updatable and has INSTEAD OF triggers, then the triggers take preference. In other words, the database fires the triggers instead of performing DML on the view.

If the view belongs to a hierarchy, then the trigger is not inherited by subviews.

INSTEAD OF Triggers

• INSTEAD OF triggers are valid only for views. You cannot specify an INSTEAD OF trigger on a table.

• You can read both the :OLD and the :NEW value, but you cannot write either the :OLD or the :NEW value.

DML_event_clause

The DML_event_clause lets you specify one of three DML statements that can cause the trigger to fire. Oracle Database fires the trigger in the existing user transaction.

You cannot specify the MERGE keyword in the DML_event_clause. If you want a trigger to fire in relation to a MERGE operation, you must create triggers on the INSERT and UPDATE operations to which the MERGE operation decomposes.

DELETE

Specify DELETE if you want the database to fire the trigger whenever a DELETE statement removes a row from the table or removes an element from a nested table.

INSERT

Specify INSERT if you want the database to fire the trigger whenever an INSERT statement adds a row to a table or adds an element to a nested table.

UPDATE

Specify UPDATE if you want the database to fire the trigger whenever an UPDATE statement changes a value in one of the columns specified after OF. If you omit OF, then the database fires the trigger whenever an UPDATEstatement changes a value in any column of the table or nested table.

For an UPDATE trigger, you can specify object type, varray, and REF columns after OF to indicate that the trigger should be fired whenever an UPDATE statement changes a value in one of the columns. However, you cannot change the values of these columns in the body of the trigger itself.

Restrictions on Triggers on UPDATE OperationsThe UPDATE clause is subject to the following restrictions:

• You cannot specify UPDATE OF for an INSTEAD OF trigger. Oracle Database fires INSTEAD OF triggers whenever an UPDATE changes a value in any column of the view.

• You cannot specify a nested table or LOB column in the UPDATE OF clause.

Performing DML operations directly on nested table columns does not cause Oracle Database to fire triggers defined on the table containing the nested table column.

ddl_event

Specify one or more types of DDL statements that can cause the trigger to fire. You can create triggers for these events on DATABASE or SCHEMA unless otherwise noted. You can create BEFORE and AFTER triggers for these events. Oracle Database fires the trigger in the existing user transaction.

Restriction on Triggers on DDL EventsYou cannot specify as a triggering event any DDL operation performed through a PL/SQL procedure.

The following ddl_event values are valid:

ALTERSpecify ALTER to fire the trigger whenever an ALTER statement modifies a database object in the data dictionary.

Restriction on Triggers on ALTER OperationsThe trigger will not be fired by an ALTER DATABASE statement.

ANALYZESpecify ANALYZE to fire the trigger whenever the database collects or deletes statistics or validates the structure of a database object.

ASSOCIATE STATISTICSSpecify ASSOCIATE STATISTICS to fire the trigger whenever the database associates a statistics type with a database object.

AUDITSpecify AUDIT to fire the trigger whenever the database tracks the occurrence of a SQL statement or tracks operations on a schema object.

COMMENTSpecify COMMENT to fire the trigger whenever a comment on a database object is added to the data dictionary.

CREATESpecify CREATE to fire the trigger whenever a CREATE statement adds a new database object to the data dictionary.

Restriction on Triggers on CREATE OperationsThe trigger will not be fired by a CREATE DATABASE or CREATE CONTROLFILE statement.

DISASSOCIATE STATISTICSSpecify DISASSOCIATE STATISTICS to fire the trigger whenever the database disassociates a statistics type from a database object.

DROPSpecify DROP to fire the trigger whenever a DROP statement removes a database object from the data dictionary.

GRANTSpecify GRANT to fire the trigger whenever a user grants system privileges or roles or object privileges to another user or to a role.

NOAUDITSpecify NOAUDIT to fire the trigger whenever a NOAUDIT statement instructs the database to stop tracking a SQL statement or operations on a schema object.

RENAMESpecify RENAME to fire the trigger whenever a RENAME statement changes the name of a database object.

REVOKESpecify REVOKE to fire the trigger whenever a REVOKE statement removes system privileges or roles or object privileges from a user or role.

TRUNCATESpecify TRUNCATE to fire the trigger whenever a TRUNCATE statement removes the rows from a table or cluster and resets its storage characteristics.

DDLSpecify DDL to fire the trigger whenever any of the preceding DDL statements is issued.

database_event

Specify one or more particular states of the database that can cause the trigger to fire. You can create triggers for these events on DATABASE or SCHEMA unless otherwise noted. For each of these triggering events, Oracle Database opens an autonomous transaction scope, fires the trigger, and commits any separate transaction (regardless of any existing user transaction).

SERVERERROR Specify SERVERERROR to fire the trigger whenever a server error message is logged.

The following errors do not cause a SERVERERROR trigger to fire:

• ORA-01403: no data found

• ORA-01422: exact fetch returns more than requested number of rows

• ORA-01423: error encountered while checking for extra rows in exact fetch

• ORA-01034: ORACLE not available

• ORA-04030: out of process memory when trying to allocate string bytes (string, string)

LOGONSpecify LOGON to fire the trigger whenever a client application logs onto the database.

LOGOFF Specify LOGOFF to fire the trigger whenever a client application logs off the database.

STARTUPSpecify STARTUP to fire the trigger whenever the database is opened.

SHUTDOWNSpecify SHUTDOWN to fire the trigger whenever an instance of the database is shut down.

SUSPENDSpecify SUSPEND to fire the trigger whenever a server error causes a transaction to be suspended.

DB_ROLE_CHANGEIn a Data Guard configuration, specify DB_ROLE_CHANGE to fire the trigger whenever a role change occurs from standby to primary or from primary to standby.

ON table | view

The ON clause lets you determine the database object on which the trigger is to be created. Specify the schema and table or view name of one of the following on which the trigger is to be created:

• Table or view

• Object table or object view

• A column of nested-table type

If you omit schema, then Oracle Database assumes the table is in your own schema. You can create triggers on index-organized tables.

Restriction on SchemaYou cannot create a trigger on a table in the schema SYS.

NESTED TABLE Clause

Specify the nested_table_column of a view upon which the trigger is being defined. Such a trigger will fire only if the DML operates on the elements of the nested table.

Restriction on Triggers on Nested TablesYou can specify NESTED TABLE only for INSTEAD OF triggers.

DATABASE

Specify DATABASE to define the trigger on the entire database. The trigger fires whenever any database user initiates the triggering event.

SCHEMA

Specify SCHEMA to define the trigger on the current schema. The trigger fires whenever any user connected as schema initiates the triggering event.

referencing_clause

The referencing_clause lets you specify correlation names. You can use correlation names in the PL/SQL block and WHEN condition of a row trigger to refer specifically to old and new values of the current row. The default correlation names are OLD and NEW. If your row trigger is associated with a table named OLD or NEW, use this clause to specify different correlation names to avoid confusion between the table name and the correlation name.

• If the trigger is defined on a nested table, then OLD and NEW refer to the row of the nested table, and PARENT refers to the current row of the parent table.

• If the trigger is defined on an object table or view, then OLD and NEW refer to object instances.

Restriction on the referencing_clauseThe referencing_clause is not valid with INSTEAD OF triggers on CREATE DDL events.

FOR EACH ROW

Specify FOR EACH ROW to designate the trigger as a row trigger. Oracle Database fires a row trigger once for each row that is affected by the triggering statement and meets the optional trigger constraint defined in theWHEN condition.

Except for INSTEAD OF triggers, if you omit this clause, then the trigger is a statement trigger. Oracle Database fires a statement trigger only once when the triggering statement is issued if the optional trigger constraint is met.

INSTEAD OF trigger statements are implicitly activated for each row.

Restriction on Row TriggersThis clause is valid only for DML event triggers, not for DDL or database event triggers.

WHEN Clause

Specify the trigger condition, which is a SQL condition that must be satisfied for the database to fire the trigger. See the syntax description of condition in Chapter 7, "Conditions". This condition must contain correlation names and cannot contain a query.

The NEW and OLD keywords, when specified in the WHEN clause, are not considered bind variables, so are not preceded by a colon (:). However, you must precede NEW and OLD with a colon in all references other than theWHEN clause.

Restrictions on Trigger ConditionsTrigger conditions are subject to the following restrictions:

• If you specify this clause for a DML event trigger, then you must also specify FOR EACH ROW. Oracle Database evaluates this condition for each row affected by the triggering statement.

• You cannot specify trigger conditions for INSTEAD OF trigger statements.

• You can reference object columns or their attributes, or varray, nested table, or LOB columns. You cannot invoke PL/SQL functions or methods in the trigger condition.

pl/sql_block

Specify the PL/SQL block that Oracle Database executes to fire the trigger.

The PL/SQL block of a database trigger can contain one of a series of built-in functions in the SYS schema designed solely to extract system event attributes. These functions can be used only in the PL/SQL block of a database trigger.

Restrictions on Trigger ImplementationThe implementation of a trigger is subject to the following restrictions:

• The PL/SQL block of a trigger cannot contain transaction control SQL statements (COMMIT, ROLLBACK, SAVEPOINT, and SET CONSTRAINT) if the block is executed within the same transaction.

• You can reference and use LOB columns in the trigger action inside the PL/SQL block. You can modify the :NEW values but not the :OLD values of LOB columns within the trigger action.

call_procedure_statement

The call_procedure_statement lets you call a stored procedure rather than specifying the trigger code inline as a PL/SQL block. The syntax of this statement is the same as that for CALL, with the following exceptions:

• You cannot specify the INTO clause of CALL, because it applies only to functions.

• You cannot specify bind variables in expr.

• To reference columns of tables on which the trigger is being defined, you must specify :NEW and :OLD.

Examples

Creating a DML Trigger: ExamplesThis example shows the basic syntax for a BEFORE statement trigger. You would write such a trigger to place restrictions on DML statements issued on a table, for example, when such statements could be issued.

CREATE TRIGGER schema.trigger_name
BEFORE
DELETE OR INSERT OR UPDATE
ON schema.table_name
pl/sql_block

Oracle Database fires such a trigger whenever a DML statement affects the table. This trigger is a BEFORE statement trigger, so the database fires it once before executing the triggering statement.

The next example shows a partial BEFORE row trigger. The PL/SQL block might specify, for example, that an employee's salary must fall within the established salary range for the employee's job:

CREATE TRIGGER hr.salary_check
BEFORE INSERT OR UPDATE OF salary, job_id ON hr.employees
FOR EACH ROW
WHEN (new.job_id <> 'AD_VP')
pl/sql_block

Oracle Database fires this trigger whenever one of the following statements is issued:

• An INSERT statement that adds rows to the employees table

• An UPDATE statement that changes values of the salary or job_id columns of the employees table

salary_check is a BEFORE row trigger, so the database fires it before changing each row that is updated by the UPDATE statement or before adding each row that is inserted by the INSERT statement.

salary_check has a trigger condition that prevents it from checking the salary of the administrative vice president (AD_VP).

Creating a DDL Trigger: ExampleThis example creates an AFTER statement trigger on any DDL statement CREATE. Such a trigger can be used to audit the creation of new data dictionary objects in your schema.

CREATE TRIGGER audit_db_object AFTER CREATE
ON SCHEMA
pl/sql_block

Calling a Procedure in a Trigger Body: ExampleYou could create the salary_check trigger described in the preceding example by calling a procedure instead of providing the trigger body in a PL/SQL block. Assume you have defined a procedure check_sal in the hrschema, which verifies that an employee's salary is in an appropriate range. Then you could create the trigger salary_check as follows:

CREATE TRIGGER salary_check
BEFORE INSERT OR UPDATE OF salary, job_id ON employees
FOR EACH ROW
WHEN (new.job_id <> 'AD_VP')
CALL check_sal(:new.job_id, :new.salary, :new.last_name)

The procedure check_sal could be implemented in PL/SQL, C, or Java. Also, you can specify :OLD values in the CALL clause instead of :NEW values.

Creating a Database Event Trigger: ExampleThis example shows the basic syntax for a trigger to log all errors. The hypothetical PL/SQL block does some special processing for a particular error (invalid logon, error number 1017). This trigger is an AFTERstatement trigger, so it is fired after an unsuccessful statement execution, such as unsuccessful logon.

CREATE TRIGGER log_errors AFTER SERVERERROR ON DATABASE
BEGIN
IF (IS_SERVERERROR (1017)) THEN
<special processing of logon error>
ELSE
<log error number>
END IF;
END;

Creating an INSTEAD OF Trigger: ExampleIn this example, an oe.order_info view is created to display information about customers and their orders:

CREATE VIEW order_info AS
SELECT c.customer_id, c.cust_last_name, c.cust_first_name,
o.order_id, o.order_date, o.order_status
FROM customers c, orders o
WHERE c.customer_id = o.customer_id;

Normally this view would not be updatable, because the primary key of the orders table (order_id) is not unique in the result set of the join view. To make this view updatable, create an INSTEAD OF trigger on the view to process INSERT statements directed to the view. The PL/SQL trigger implementation is shown in italics.

CREATE OR REPLACE TRIGGER order_info_insert
INSTEAD OF INSERT ON order_info
DECLARE
duplicate_info EXCEPTION;
PRAGMA EXCEPTION_INIT (duplicate_info, -00001);
BEGIN
INSERT INTO customers
(customer_id, cust_last_name, cust_first_name)
VALUES (
:new.customer_id,
:new.cust_last_name,
:new.cust_first_name);
INSERT INTO orders (order_id, order_date, customer_id)
VALUES (
:new.order_id,
:new.order_date,
:new.customer_id);
EXCEPTION
WHEN duplicate_info THEN
RAISE_APPLICATION_ERROR (
num=> -20107,
msg=> 'Duplicate customer or order ID');
END order_info_insert;
/

You can now insert into both base tables through the view (as long as all NOT NULL columns receive values):

INSERT INTO order_info VALUES
(999, 'Smith', 'John', 2500, '13-MAR-2001', 0);

Creating a SCHEMA Trigger: ExampleThe following example creates a BEFORE statement trigger on the sample schema hr. When a user connected as hr attempts to drop a database object, the database fires the trigger before dropping the object:

CREATE OR REPLACE TRIGGER drop_trigger
BEFORE DROP ON hr.SCHEMA
BEGIN
RAISE_APPLICATION_ERROR (
num => -20000,
msg => 'Cannot drop object');
END;
/

##############################################

##############################################

####################另  一  篇####################

##############################################

##############################################

【转自】http://heisetoufa.javaeye.com/blog/367314

##############################################

##############################################

###################自己写了个例子###################

##############################################

drop trigger c_object;
drop trigger d_object;

CREATE OR REPLACE TRIGGER d_object BEFORE DROP ON SCHEMA
DECLARE
BEGIN
delete from dict_columns where table_name = lower(Sys.Dictionary_obj_name);
END;
/

CREATE OR REPLACE TRIGGER c_object AFTER CREATE ON SCHEMA
DECLARE
aa      VARCHAR2(64);
sql_str VARCHAR2(768);
BEGIN
FOR curs IN (SELECT table_name, column_name, data_type, data_length, data_default FROM user_tab_columns where table_name not like '%$%' ORDER BY table_name, column_id) LOOP
IF curs.data_default IS NULL THEN
curs.data_default := ' ';
END IF;
sql_str := 'INSERT INTO dict_columns (table_name,column_name,data_type,data_length,data_default) VALUES(:1,:2,:3,:4,:6)';
EXECUTE IMMEDIATE sql_str USING curs.table_name,curs.column_name,curs.data_type,curs.data_length,curs.data_default;
END LOOP;
END;
/

##############################################

oracle触发器高级教程相关推荐

1. Oracle（11g）数据库教程之十五：Oracle触发器实例

   Oracle(11g)数据库教程之十五:Oracle触发器实例 准备工作: 先启动Oracle,连接数据库 建立两个表:Goods(商品表).Orders(订单表) Goods(商品表) create ...

2. oracle R11g高级安装详细教程

   最详细的Oracle安装步骤如下: 1.在官网去下载oracle安装包,选择对应的安装包(如下图) Oracle下载界面地址: http://www.oracle.com/technetwork/da ...

3. 安装oracle高级安装,oracle R11g高级安装详细教程

   最详细的Oracle安装步骤如下: 1.在官网去下载oracle安装包,选择对应的安装包(如下图) Oracle下载界面地址: http://www.oracle.com/technetwork/da ...

4. oracle 触发器的实例(转)

   触发器使用教程和命名规范 目  录 目录 触发器使用教程和命名规范 1 1,触发器简介 1 2,触发器示例 2 3,触发器语法和功能 3 4,例一:行级触发器之一 4 5,例二:行级触发器之二 4 6 ...

5. Oracle 触发器使用实例

   触发器使用教程和命名规范 目 录 触发器使用教程和命名规范 1 1,触发器简介 1 2,触发器示例 2 3,触发器语法和功能 3 4,例一:行级触发器之一 4 5,例二:行级触发器之二 4 6,例三: ...

6. oracle行级的触发器,Oracle触发器Trigger2行级

   create table trigger_t2( id int, name varchar(30), age int ); /* --创建一个before update的触发器-控制每一行,行级 -- ...

7. 触发器使用教程和命名规范

   触发器使用教程和命名规范 目  录 触发器使用教程和命名规范 1 1,触发器简介 1 2,触发器示例 2 3,触发器语法和功能 3 4,例一:行级触发器之一 4 5,例二:行级触发器之二 4 6,例三 ...

8. Oracle数据库基础教程

   查看书籍详细信息: Oracle数据库基础教程 编辑推荐 体现作者多年的数据库管理与开发经验,结合大量实用技巧,重点突出,便于灵活掌握,提供典型应用实例与上机实验,分析详细,实用性强. 本书是作者结合 ...

9. MYSQL语句大全(SQL 高级教程)【上】

   SQL 高级教程 Top            TOP 子句用于规定要返回的记录的数目.                    对于拥有数千条记录的大型表来说,TOP 子句是非常有用的         ...

最新文章

1. 微信小程序左滑删除效果的实现完整源码附效果图
2. SAP MM41 收到报错：Retail materials cannot be maintained.
3. ZigBee 裸机 uart 配置
4. windows服务守护进程bat脚本、windows窗体守护进程bat脚本
5. 成功解决调用密钥报错4001 加密方式错误
6. 【时间序列】时序预测竞赛之异常检测算法综述
7. 识别手指pos 20个
8. 《CCNA路由和交换(200-120)学习指南》——2.4节认证提要
9. BZOJ4998 星球联盟（LCT+双连通分量+并查集）
10. GT9xxxxx系列------如何加入电源管理模块
11. idea社区版创建springboot_idea社区版+spring boot
12. spring html导出excel文件,Spring 导出 Excel-Fun言
13. 带小数十进制转二进制C语言,c语言十进制小数转为二进制
14. 如何快速的自建 DoH ( DNS over HTTPS) 服务
15. (一) Marlin-2.1.x 源码解析：G-Code指令的接收、解析与执行
16. 用AkShare获取实盘沪深可转债数据
17. LeetCode 6194. 最小 XOR
18. 中国大学MOOC北京大学唐大仕老师《Java程序设计》源码分享
19. 阿里云李克：阿里云边缘云计算的技术和实践
20. Tensorflow MNIST for Android

热门文章

1. OpenCV 简单的人脸识别
2. Python遍历字典的方法
3. DataNumen DWG Recovery中文版
4. A*算法的认识与求第K短路模板
5. Hyperledger Fabric安装问题备忘（二）
6. 2017-10-29—英语发音的一些技巧总结
7. Linux 访问权限
8. VS2010中整理代码快捷键
9. JSON数据与JavaScript对象转换
10. php数组全排列,元素所有组合