ORACLE ERROR CODE ORA-00069
ERROR
cannot acquire lock — table locks disabled for string
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

ORACLE ERROR CODE ORA-00068
ERROR
invalid value string for parameter string, must be between string and string
CAUSE
The value for the initialization parameter is invalid
ACTION
Choose a value as indicated by the message

ORACLE ERROR CODE ORA-00067
ERROR
invalid value string for parameter string; must be at least string
CAUSE
The value for the initialization parameter is invalid
ACTION
Choose a value as indicated by the message

ORACLE ERROR CODE ORA-00066
ERROR
LOG_FILES is string but needs to be string to be compatible
CAUSE
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
ACTION
Change the value of the LOG_FILES initialization parameter to be compatible

ORACLE ERROR CODE ORA-00065
ERROR
initialization of FIXED_DATE failed
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

ORACLE ERROR CODE ORA-00064
ERROR
object is too large to allocate on this O/S (string,string)
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

ORACLE ERROR CODE ORA-00063
ERROR
maximum number of log files exceeded string
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

ORACLE ERROR CODE ORA-00062
ERROR
DML full-table lock cannot be acquired; DML_LOCKS is 0
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

ORACLE ERROR CODE ORA-00061
ERROR
another instance has a different DML_LOCKS setting
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

ORACLE ERROR CODE ORA-00060
ERROR
deadlock detected while waiting for resource
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