Error Code
ORA-00065
Description
initialization of FIXED_DATE failed
Cause
Possible cause of this error is, the FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss.
Action
To fix this error, make sure the initialization parameter is in the correct date format.
reference
Monday, January 28, 2013
ORA-00064 object is too large to allocate on this O/S (string,string)
Error Code
ORA-00064
Description
object is too large to allocate on this O/S (string,string)
Cause
Possible cause of this error is, an initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system.
Action
To fix this error, reduce the value of the initialization parameter.
reference
ORA-00064
Description
object is too large to allocate on this O/S (string,string)
Cause
Possible cause of this error is, an initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system.
Action
To fix this error, reduce the value of the initialization parameter.
reference
ORA-00063 maximum number of log files exceeded string
Error Code
ORA-00063
Description
maximum number of log files exceeded string
Cause
Possible cause of this error is, the number of log files specificied exceeded the maximum number of log files supported in this release.
Action
To fix this error, re-create the control file with the highest number of log files no greater than the maximum supported in this release.
reference
ORA-00062 DML full-table lock cannot be acquired; DML_LOCKS is 0
Error Code
ORA-00062
Description
DML full-table lock cannot be acquired; DML_LOCKS is 0
Cause
Possible cause of this error is, the instance was started with DML_LOCKS = 0, and the statement being executed needs a full-table lock (S, X, or SSX).
Action
To fix this error, restart the instance with DML_LOCKS not equal to zero, and reexecute the statement.
reference
ORA-00062
Description
DML full-table lock cannot be acquired; DML_LOCKS is 0
Cause
Possible cause of this error is, the instance was started with DML_LOCKS = 0, and the statement being executed needs a full-table lock (S, X, or SSX).
Action
To fix this error, restart the instance with DML_LOCKS not equal to zero, and reexecute the statement.
reference
ORA-00061 another instance has a different DML_LOCKS setting
Error Code
ORA-00061
Description
another instance has a different DML_LOCKS setting
Cause
Possible cause of this error is, the shared instance being started is using DML locks, and the running instances are not, or vice-versa.
Action
To fix this error, ensure that all instances' INIT.ORA files specify the DML_LOCKS parameter as 0 or all as non-zero.
reference
ORA-00061
Description
another instance has a different DML_LOCKS setting
Cause
Possible cause of this error is, the shared instance being started is using DML locks, and the running instances are not, or vice-versa.
Action
To fix this error, ensure that all instances' INIT.ORA files specify the DML_LOCKS parameter as 0 or all as non-zero.
reference
Subscribe to:
Posts (Atom)