Cause: It was not possible to create the control file. Action: Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again.

Cause: The syntax for the DISPATCHERS parameter is incorrect. Action: Refer to the manual for correct syntax.

Cause: A command was issued that tried to lock the table indicated in the message. Examples of commands that can lock tables are: LOCK TABLE, ALTER TABLE … ADD (…), and so on. Action: Use the ALTER TABLE … ENABLE TABLE LOCK command, and retry the command.

Cause: The value for the initialization parameter is invalid. Action: Choose a value as indicated by the message.

Cause: The specified SID contained an illegal character or the SID specified was too long, which cannot occur in an SPFILE setting. Illegal characters include ,#’=() and whitespace. Action: Use a SID that does not contain a special character or whitespace. Check platform specific documentation for the maximum length of SID.

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.