Index >
ORACLE Server Parameters >
dml_locks
dml_locks
Oracle 10.0.1:
Paramter Name: | dml_locks
| Description: | dml locks - one for each table modified in a transaction
| Type: | NUMBER
| Obsoleted: | FALSE
| Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Oracle 9.2.0:
Paramter Name: | dml_locks
| Description: | dml locks - one for each table modified in a transaction
| Type: | NUMBER
| Obsoleted: | FALSE
| Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Oracle 8.1.7:
Paramter Name: | dml_locks
| Description: | dml locks - one for each table modified in a transaction
| Type: | NUMBER
| Obsoleted: | FALSE
| Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Oracle 8.0.6:
Paramter Name: | dml_locks
| Description: | dml locks - one for each table modified in a transaction
| Type: | NUMBER
| Obsoleted: | FALSE
| Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Oracle 7.3.4:
Paramter Name: | dml_locks
| Description: | dml locks - one for each table modified in a transaction
| Type: | NUMBER
| Obsoleted: | FALSE
| Can ALTER SESSION: | FALSE
| Can ALTER SYSTEM: | FALSE
|
Related Error Messages:
ORA-00055: maximum number of DML locks exceeded
ORA-00061: another instance has a different DML_LOCKS setting Cause: The shared instance being started is using DML locks, and the
running instances are not, or vice-versa.
Action: Ensure that all instances' INIT.ORA files specify
the DML_LOCKS parameter as 0 or all as non-zero.
ORA-00062: DML full-table lock cannot be acquired; DML_LOCKS is 0 Cause: The instance was started with DML_LOCKS = 0, and the statement
being executed needs a full-table lock (S, X, or SSX).
Action: Restart the instance with DML_LOCKS not equal to zero, and
reexecute the statement.
This parameter is documented in the
Oracle Server Reference Guide.
Search for more info about
[ dml_locks ]
on the Oracle FAQ.
|