|Default value||Derived: 4 *
|Range of values||20 to unlimited; a setting of 0 disables enqueues|
|Real Application Clusters||You must set this parameter for every instance, and all instances must have positive values or all must be 0.|
A DML lock is a lock obtained on a table that is undergoing a DML operation (insert, update, delete).
DML_LOCKS specifies the maximum number of DML locks—one for each table modified in a transaction. The value should equal the grand total of locks on tables currently referenced by all users. For example, if three users are modifying data in one table, then three entries would be required. If three users are modifying data in two tables, then six entries would be required.
The default value assumes an average of four tables referenced for each transaction. For some systems, this value may not be enough.
Enqueues are shared memory structures that serialize access to database resources. If you set the value of
0, enqueues are disabled and performance is slightly increased. However, you should be aware of the following restrictions when you set you
You cannot use
CREATE INDEX statements
You cannot use explicit lock statements such as
LOCK TABLE IN EXCLUSIVE MODE
Enterprise Manager cannot run on any instances for which
DML_LOCKS is set to
Oracle holds more locks during parallel DML than during serial execution. Therefore, if your database supports a lot of parallel DML, you may need to increase the value of this parameter.
Oracle Database Concepts for a discussion of lock and enqueue resources needed for parallel DML
Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide, Oracle Database Concepts, and Oracle Database Administrator's Guide for more information on data concurrency