Cause: The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss. Action: Make sure the initialization parameter is in the correct date format.

Cause: An initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system. Action: Reduce the value of the initialization parameter.

Cause: The number of log files specificied exceeded the maximum number of log files supported in this release. Action: Re-create the control file with the highest number of log files no greater than the maximum supported in this release.

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.

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.

Cause: Transactions deadlocked one another while waiting for resources. Action: Look at the trace file to see the transactions and resources involved. Retry if necessary.

Cause: The value of the DB_FILES initialization parameter was exceeded. Action: Increase the value of the DB_FILES parameter and warm start.

Cause: DB_BLOCK_SIZE initialization parameter is wrong for the database being mounted. It does not match the value used to create the database. Action: Fix the value of the DB_BLOCK_SIZE parameter or mount a database that matches the value.

Cause: The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts. Action: Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and warm start.

Cause: An attempt was made to acquire a DDL lock that is already locked. Action: This happens if you attempt to drop a table that has parse locks on it.