Category Archives: Database

ORA-00071: process number must be between 1 and string

ORA-00071: process number must be between 1 and string

ORA-00071: process number must be between 1 and string
Cause: An invalid process number was specified.
Action: Specify a valid process number.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00070: command string is not valid

ORA-00070: command string is not valid

ORA-00070: command string is not valid
Cause: An invalid debugger command was specified.
Action: Type HELP to see the list of available commands.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00069: cannot acquire lock — table locks disabled for string

ORA-00069: cannot acquire lock — table locks disabled for string

ORA-00069: 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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00068: invalid value string for parameter string, must be between string and string

ORA-00068: invalid value string for parameter string, must be between string and string

ORA-00068: 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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00067: invalid value string for parameter string; must be at least string

ORA-00067: invalid value string for parameter string; must be at least string

ORA-00067: 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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00066: LOG_FILES is string but needs to be string to be compatible

ORA-00066: LOG_FILES is string but needs to be string to be compatible

ORA-00066: 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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00065: initialization of FIXED_DATE failed

ORA-00065: initialization of FIXED_DATE failed

ORA-00065: 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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00064: object is too large to allocate on this O/S (string,string)

ORA-00064: object is too large to allocate on this O/S (string,string)

ORA-00064: 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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00063: maximum number of log files exceeded string

ORA-00063: maximum number of log files exceeded string

ORA-00063: 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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00062: DML full-table lock cannot be acquired; DML_LOCKS is 0

ORA-00062: DML full-table lock cannot be acquired; DML_LOCKS is 0

ORA-00062: 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

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/