Welcome to the Technical Portal: ORA-00051 to ORA-00075
| ORA Code | Code Description | Cause | Action |
| ORA-00051 | Timeout occurred while waiting for a resource | Usually due to a dead instance | Check for any dead, unrecovered instances and recover them |
| ORA-00052 | Maximum number of enqueue resources (string) exceeded | Ran out of enqueue resources | Increase the value of the ENQUEUE_RESOURCES initialization parameter |
| ORA-00053 | Maximum number of enqueues exceeded | Ran out of enqueue state objects | Increase the value of the ENQUEUES initialization parameter |
| ORA-00054 | Resource busy and acquire with NOWAIT specified | You tried to execute a LOCK TABLE or SELECT FOR UPDATE command with the NOWAIT keyword but the resource was unavailable |
Wait and try the command again after a few minutes. or Execute the command without the NOWAIT keyword. |
| ORA-00055 | Maximum number of DML locks exceeded | Ran out of DML lock state objects | Increase the value of the DML_LOCKS initialization parameter and warm start |
| ORA-00056 | DDL lock on object 'string.string' is already held in an incompatible mode | An attempt was made to acquire a DDL lock that is already locked | This happens if you attempt to drop a table that has parse locks on it |
| ORA-00057 | Maximum number of temporary table locks exceeded | The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts | Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and warm start |
| ORA-00058 | DB_BLOCK_SIZE must be string to mount this database (not string) | DB_BLOCK_SIZE initialization parameter is wrong for the database being mounted. It does not match the value used to create the database | Fix the value of the DB_BLOCK_SIZE parameter or mount a database that matches the value |
| ORA-00059 | Maximum number of DB_FILES exceeded | The value of the DB_FILES initialization parameter was exceeded | Increase the value of the DB_FILES parameter and warm start |
| ORA-00060 | Deadlock detected while waiting for resource | Transactions deadlocked one another while waiting for resources | Look at the trace file to see the transactions and resources involved. Retry if necessary |
| ORA-00061 | Another instance has a different DML_LOCKS setting | The shared instance being started is using DML locks, and the running instances are not, or vice-versa | 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 | The instance was started with DML_LOCKS = 0, and the statement being executed needs a full-table lock (S, X, or SSX) | Restart the instance with DML_LOCKS not equal to zero, and reexecute the statement |
| ORA-00063 | Maximum number of log files exceeded string | The number of log files specificied exceeded the maximum number of log files supported in this release | Re-create the control file with the highest number of log files no greater than the maximum supported in this release |
| ORA-00064 | Object is too large to allocate on this O/S (string,string) | An initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system | Reduce the value of the initialization parameter |
| ORA-00065 | Initialization of FIXED_DATE failed | The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss | Make sure the initialization parameter is in the correct date format |
| ORA-00066 | LOG_FILES is string but needs to be string to be compatible | The maximum number of log files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open | Change the value of the LOG_FILES initialization parameter to be compatible |
| ORA-00067 | Invalid value string for parameter string; must be at least string | The value for the initialization parameter is invalid | Choose a value as indicated by the message |
| ORA-00068 | Invalid value string for parameter string, must be between string and string | The value for the initialization parameter is invalid | Choose a value as indicated by the message |
| ORA-00069 | Cannot acquire lock -- table locks disabled for string | 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 | Use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry the command |
| ORA-00070 | Command string is not valid | An invalid debugger command was specified | Type HELP to see the list of available commands |
| ORA-00071 | Process number must be between 1 and string | An invalid process number was specified | Specify a valid process number |
| ORA-00072 | Process "string" is not active | An invalid process was specified | Specify a valid process |
| ORA-00073 | Command string takes between string and string argument(s) | An incorrect number of arguments was specified | Specify the correct number of arguments. Type HELP to see the list of commands and their syntax |
| ORA-00074 | No process has been specified | No debug process has been specified | Specify a valid process |
| ORA-00075 | Process "string" not found in this instance | The specified process was not logged on to the current instance | Specify a valid process |