ORA-00062 DML full-table lock cannot be acquired; DML_LOCKS is 0

Error Code
ORA-00062

Description
DML full-table lock cannot be acquired; DML_LOCKS is 0

Cause
Possible cause of this error is, the instance was started with DML_LOCKS = 0, and the statement being executed needs a full-table lock (S, X, or SSX).

Action
To fix this error, restart the instance with DML_LOCKS not equal to zero, and reexecute the statement.

reference

ORA-00061 another instance has a different DML_LOCKS setting

Error Code
ORA-00061

Description
another instance has a different DML_LOCKS setting

Cause
Possible cause of this error is, the shared instance being started is using DML locks, and the running instances are not, or vice-versa.

Action
To fix this error, ensure that all instances' INIT.ORA files specify the DML_LOCKS parameter as 0 or all as non-zero.

reference

ORA-00060 deadlock detected while waiting for resource

Error Code
ORA-00060

Description
deadlock detected while waiting for resource

Cause
Possible cause of this error is, when transactions deadlocked one another while waiting for resources.

Action
To fix this error, look at the trace file to see the transactions and resources involved. Retry if necessary.

reference

ORA-00059 maximum number of DB_FILES exceeded

Error Code
ORA-00059

Description
maximum number of DB_FILES exceeded

Cause
Possible cause of this error is, the value of the DB_FILES initialization parameter was exceeded.

Action
To fix this error, increase the value of the DB_FILES parameter and warm start.


reference

ORA-00058 DB_BLOCK_SIZE must be string to mount this database (not string)

Error Code

ORA-00058

Description

DB_BLOCK_SIZE must be string to mount this database (not string)

Cause

Possible cause of this error is, DB_BLOCK_SIZE initialization parameter is wrong for the database being mounted. It does not match the value used to create the database.

Action

To solve this error, fix the value of the DB_BLOCK_SIZE parameter or mount a database that matches the value.

reference