Cause: An attempt to make a tablespace read only found that one of its files is offline. Action: Bring the file online and retry this command.

Cause: The archived log is not the correct log. An earlier log is needed. Action: Restore the correct log file.

Cause: The specified control file has a different mount ID than the other control files that are being mounted. This means that the first instance to mount the database did not use this control file. Action: Find and install the correct control file.

Cause: No control file is specified or the control file specified does not exist. Action: Specify at least one valid control file and retry the operation.

Cause: An attempt was made to use more control files than Oracle supports. Action: Shut down Oracle. Reduce the number of control files specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete unused files.

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.