Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
This section lists the messages generated by the Oracle Server.
If you are using Trusted Oracle, see the Trusted Oracle documentation for information about error messages in that environment.
Cause: An operation has completed normally, having met no exceptions.
Action: No action required.
Cause: An update or insert statement attempted to insert a duplicate key.
Action: Either remove the unique restriction or do not insert the key.
Cause: The current session was requested to set a trace event by another session.
Action: This is used internally; no action required.
Cause: An operation requested a resource that was unavailable. The maximum number of sessions is specified by the initialization parameter SESSIONS. When this maximum is reached, no more requests are processed.
Action: Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the SESSIONS parameter in the initialization parameter file, and restart Oracle.
Cause: All licenses are in use.
Action: Call customer support before increasing the number of session licenses.
Cause: An operation requested a resource that was unavailable. The maximum number of processes is specified by the initialization parameter PROCESSES. When this maximum is reached, no more requests are processed.
Action: Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the PROCESSES parameter in the initialization parameter file, and restart Oracle.
Cause: The user session is currently being used by someone else.
Action: Do not execute calls in a user session concurrently.
Cause: Either the session specified does not exist, or the caller does not have the privilege to access it.
Action: Specify a valid session ID. This requires ownership of the session id or the CHANGE_USER privilege.
Cause: An attempt was made to detach the current session, which contains references to the process' private memory.
Action: A session may contain references to process memory (PGA) if it has an open network connection, a very large context area, or operating system privileges. To allow the detach, it may be necessary to close the session's database link or cursors. Detaching a session with operating system privileges is always disallowed.
Cause: An attempt was made to log in more than once from different processes after Oracle had been started in single-process mode.
Action: When Oracle is running in single-process mode, out of the previous process before trying to log in from another one.
Cause: An allocation failed because Oracle ran out of memory.
Action: Restart Oracle with a larger SGA heap.
Cause: The session ID string specified in the ALTER SYSTEM KILL SESSION command was invalid, or no string was specified.
Action: Retry the command with a valid session ID.
Cause: An attempt was made to kill the current session with the ALTER SYSTEM KILL SESSION command.
Action: If it is necessary to kill the current session, do so from another session.
Cause: A privileged user killed the session and it is no longer logged in to the database.
Action: Contact the database administrator. The administrator may be attempting to perform an operation that requires users to be logged out. When the database administrator announces that the database is available, log in and resume work.
Cause: The session ID specified in an ALTER SYSTEM KILL SESSION command was not a user session. For example, the session may be recursively started.
Action: Retry the command with a valid session ID.
Cause: The user session ID no longer exists, probably because the session was logged out.
Action: Use a valid session ID.
Cause: The session specified in the ALTER SYSTEM KILL SESSION command cannot be killed immediately because the session is involved in a non-interruptible operation. For example, rolling back a transaction or being blocked by a network operation. The session has been marked to be killed as soon as possible after the current operation is done.
Action: No action required. The session will be killed when the operation is completed. Further executions of the ALTER SYSTEM KILL SESSION command may cause the session to be killed sooner.
Cause: The session migration password specified in a session creation call was invalid (probably too long).
Action: Retry with a valid password, less than 30 characters.
Cause: An attempt was made to detach or clone the current session, and it has an empty migration password. This is not allowed.
Action: Create the session with a non-empty migration password.
Cause: An attempt was made to ROLLBACK from a PL/SQL object (procedure, function, package) in a session where COMMIT and ROLLBACK are disabled by an ALTER SESSION DISABLE COMMIT IN PROCEDURE statement.
Action: Enable COMMITs from PL/SQL in this session or do not attempt a COMMIT or ROLLBACK when disabled.
Cause: Specified value for LICENSE_MAX_USERS is less than current number of users.
Action: Check the license limit and drop extra users or purchase more licenses.
Cause: An attempt was made to go more than the specified number of recursive SQL levels was made.
Action: Remove the recursive SQL, possibly a recursive trigger.
Cause: Could not obtain the operating system resources necessary for an Oracle enqueue. This most often occurs when the user resource quota on the operating system is too low.
Action: Look up the operating system error in the operating system-specific Oracle documentation and perform the needed action.
Cause: This message is usually caused by an instance that has terminated abnormally.
Action: Restart any non-recovered instances.
Cause: An operation requested a resource that was unavailable. The maximum number of enqueue resources is specified by the initialization parameter ENQUEUE_RESOURCES. When this maximum is reached, no more requests are processed.
Action: Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the ENQUEUE_RESOURCES parameter in the initialization parameter file, and restart Oracle.
Cause: An operation requested a resource that was unavailable and the enqueue list for the resource had reached its maximum length. If a request is made for a resource that is unavailable, the request is enqueued to wait for the resource. The number of requests that may be queued for a given resource is specified by the initialization parameter ENQUEUE_RESOURCES. When this maximum is reached, no more requests may be added to the enqueue list.
Action: Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the ENQUEUE_RESOURCES parameter in the initialization parameter file, and restart Oracle.
Cause: The NOWAIT keyword forced a return to the command prompt because a resource was unavailable for a LOCK TABLE or SELECT FOR UPDATE command.
Action: Try the command after a few minutes or enter the command without the NOWAIT keyword.
Cause: An operation requested a resource that was unavailable. The maximum number of DML locks is specified by the DML_LOCKS parameter in the initialization parameter file. When this maximum is reached, no more requests are processed.
Action: Try the operation again in a few minutes. If this message occurs often, shut down Oracle, increase the DML_LOCKS parameter in the initialization parameter file, and restart Oracle.
Cause: The attempted lock is incompatible with the DDL lock already held on the object. This usually occurs when attempting to drop a table that has parse locks.
Action: Before attempting to drop a table, check that it has no parse locks. Wait a few minutes before retrying the operation.
Cause: The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts.
Action: Increase the TEMPORARY_TABLE_LOCKS parameter and restart Oracle.
Cause: The DB_BLOCK_SIZE parameter value in the initialization parameter file used to start a database does not match the value used when that database was created. Potential reasons for this mismatch are
Action: For one of the above causes, either
Cause: An unavailable resource was requested. The maximum number of datafiles is specified by the DB_FILES parameter in the initialization parameter file. When this maximum is reached, no more requests are processed.
Action: Try again when the resource is freed. If this message occurs often, Oracle must be shut down and restarted after increasing the DB_FILES parameter in the initialization parameter file. If the DB_FILES parameter cannot be changed because it is already set to the MAXDATAFILES parameter value, set at database creation, you must create a new control file.
Cause: Your session and another session are waiting for a resource locked by the other. This condition is known as a deadlock. To resolve the deadlock, one or more statements were rolled back for the other session to continue work.
Action: Either
Cause: The shared instance being started is using DML locks and the running instances are not, or vice versa.
Action: Either
Cause: The instance was started with the initialization parameter DML_LOCKS set to zero, but the statement being executed needs a full-table lock (S, X, or SRX).
Action: Set DML_LOCKS to a non-zero value, restart the instance, and re-enter the statement.
Cause: The value of the LOG_FILES initialization parameter was exceeded.
Action: Increase the value of LOG_FILES and warm start Oracle. The value needs to be as large as the highest number log that currently exists rather than just the count of the logs that exist. If this parameter cannot be increased because it would exceed the MAXLOGFILES set at database creation, you must create a new control file first.
Cause: The initialization parameter DB_BLOCK_SIZE is set to a value that calls for more contiguous space than can be allocated on the operating system being used.
Action: Reduce the value of DB_BLOCK_SIZE so that the requested contiguous space is within the capacity of the operating system.
Cause: An attempt was made to enter a fixed date string that was not in the proper format.
Action: Enter the date string using the format YYYY-MM-DD:HH24:MI:SS.
Cause: The maximum number of redo 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: Check that the LOG_FILES initialization parameter is the same for all instances.
Cause: The value for the initialization parameter is invalid.
Action: Choose a value as indicated by the message. Change the value of the LOG_FILES parameter to be compatible.
Cause: The value for the initialization parameter is invalid.
Action: Choose a value as indicated by the message. Change the value of the LOG_FILES parameter to be compatible.
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: An invalid debugger command was specified.
Action: Type HELP to see the list of available commands.
Cause: An invalid process number was specified.
Action: Specify a valid process number.
Cause: An invalid process was specified.
Action: Specify a valid process.
Cause: An incorrect number of arguments was specified.
Action: Specify the correct number of arguments. Type HELP to see the list of commands and their syntax.
Cause: No debug process has been specified.
Action: Specify a valid process.
Cause: The specified process was not logged on to the current instance.
Action: Specify a valid process.
Cause: An attempt was made to invoke a dump which doesn't exist.
Action: Type DUMPLIST to see the list of available dumps.
Cause: An attempt was made to invoke an invalid dump.
Action: Try another dump.
Cause: An attempt was made to dump a variable by name on a system which does not support this feature.
Action: Try the PEEK command.
Cause: An attempt was made to dump a variable which doesn't exist.
Action: Use a valid variable name.
Cause: An attempt was made to dump an invalid global area.
Action: Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Use extra + level to dump global area as well as extra bytes for every pointer; extra must be a multiple of 4.
Cause: An attempt was made to read/write an invalid memory address range.
Action: Try another address or length.
Cause: An invalid length was specified for the POKE command.
Action: Use a valid length (either 1, 2, 4, or possibly 8).
Cause: Even though there may be SGA corruptions, the SGA was mapped.
Action: Use the DUMPSGA command to dump the SGA.
Cause: An attempt was made to dump an invalid global area.
Action: Specify either PGA, SGA, or UGA.
Cause: An invalid attempt was made to dump the current call heap.
Action: Wait until the process starts a call.
Cause: An invalid attempt was made to dump the user call heap.
Action: Wait until the process starts a call.
Cause: You tried to use an Oracle SQL feature that is not compliant with the SQL92 standard.
Action: Do not use the feature or use the ALTER SESSION SET FLAGGER command to set the appropriate level of SQL92 compliance.
Cause: The resource needed by the transaction was busy. The PDML transaction could not acquire the resource within the specified amount of time. This indicates potential deadlock involving this PDML transaction and other transactions currently running in the system.
Action: Increase the value of the PARALLEL_TRANSACTION_RESOURCE_TIMEOUT parameter, then retry the operation.
Cause: An application made reference to unknown or inaccessible data.
Action: Handle this condition within the application or make appropriate modifications to the application code. Note: If the application uses Oracle-mode SQL instead of ANSI-mode SQL, ORA-01403 will be generated instead of ORA-00100.
