processes

Oracle 10.0.1:

Oracle 9.2.0:

Oracle 8.1.7:

Oracle 8.0.6:

Oracle 7.3.4:

Related Error Messages:

Cause: All process state objects are in use.

Action: Increase the value of the PROCESSES initialization parameter.

ORA-00024: logins from more than one process not allowed in single-process mode

Cause: Trying to login more than once from different processes for ORACLE started in single-process mode.

Action: Logoff from the other process.

ORA-00447: fatal error in background process

Cause: One of the background processes died unexpectedly.

Action: Warm start the system.

ORA-00448: normal completion of background process

Cause: One of the background processes completed normally (i.e. exited). The background process thinks that somebody asked it to exit.

Action: Warm start the system.

ORA-00483: During shutdown a process abnormally terminated

Cause: One of the background processes did not exit normally at or near the time of shutdown.

Action: Use shutdown abort.

ORA-00601: cleanup lock conflict

Cause: PMON process runs into lock conflict trying to recovery processes

Action: This is trapped internally, no action necessary

ORA-01019: unable to allocate memory in the user side

Cause: The user side memory allocator returned error.

Action: Increase the processes heap size or switch to the old set of calls.

ORA-01328: only one build operation may occur at one time

Cause: Another processes is simultaneously attempting to run build();

Action: Wait until the other processes completes.

ORA-01372: Insufficient processes for specified LogMiner operation

Cause: The number of processes requested by the caller can not be allocated

Action: Increase number of parallel servers allocated to the instance

ORA-02481: Too many processes specified for events (max %s)

Cause: Too many processes specified than allowed per event.

Action: Enter fewer processes by using ranges or wildcards if possible.

ORA-02720: osnfop: shmat failed

Cause: When the fast driver was invoked, processes failed to attach to the shared memory buffer. You probably supplied an illegal shared memory attach address, or the system ran out of data space to accomodate the buffer.

Action: Try invoking the Fast driver later, or use the default attach address.

ORA-02758: Allocation of internal array failed

Cause: The package was unable to allocate memory for an array because the system ran out of memory.

Action: Either reclaim memory by killing other processes or reboot the machine with more memory.

ORA-02780: Name given for the core dump directory is invalid

Cause: The name given for the directory in which the server processes are to dump core in the event of an exception does not correspond to a directory.

Action: Use a different name.

ORA-02800: Requests timed out

Cause: Some of the requests for asynchronous input or output were not serviced in the required amount of time.

Action: If the load on the system is high, it is possible that the timeout limit is too low. Reset it with sfainit(). If the server processes are dying due to unexpected signals, this is an internal error, and ORACLE support should be contacted.

ORA-02842: Client unable to fork a server

Cause: The client could not spawn a server. A possible reason is that the operating system has reached its limit on the number of processes that it can spawn.

Action: Either reduce the number of servers that are to be used, or reconfigure the operating system so that it can handle more processes.

ORA-04930: open sequence number failed or initial state is valid

Cause: Either Shared Sequence Number OS component was not installed properly, or an MC hardware failure may have occurred or a previous instance was not shut down properly.

Action: Verify that there are no background or foreground Oracle processes from a previous instance on this node using the OS command ps -ef|grep . Verify that there are no shared memory segments belonging to the user which owns the Oracle installation by isuing the ipcs -b OS command. If there are shared memory segments or processes still on the system, use svrmgrl to shutdown the instance with the abort option. If the instance is not up, verify that the cluster software and/or the hardware is installed and working. Log in as superuser and issue the cnxshow command. Are all of the nodes in the cluster listed? Are they members of the cluster? Is the communications between nodes okay? If the answer to any of these questions is false, contact Digital's customer support organization.

ORA-06250: NETNTT: cannot allocate send and receive buffers

Cause: Two-task driver could not allocate data buffers.

Action: There is insufficient memory to run your program. Kill off other processes to free up memory.

ORA-06258: NETNTT: cannot allocate context area

Cause: Two-task driver could not allocate data buffers.

Action: There is insufficient memory to run your program. Kill off other processes to free up memory.

ORA-06263: NETNTT: out of memory in pi_connect

Cause: Two-task driver could not allocate data buffers.

Action: There is insufficient memory to run your program. Kill off other processes to free up memory.

ORA-06793: TLI Driver: server cannot create new process

Cause: The remote TLI server was unable to start an ORACLE process on behalf of the client.

Action: Note the operating system error message or number and contact your system adminstrator. The remote host may be unable to create any new processes due to a full process table.

ORA-07258: spdcr: fork error, unable to create process.

Cause: An error occurred when creating a new process.

Action: Check errno. Perhaps a system limit on the number of processes has been exceeded.

ORA-07412: sfaslv: Error getting entry in asynchronous write array.

Cause: One of the database writer processes could not locate its entry in the SGA.

Action: Contact customer support.

ORA-07417: sfareq: One or more database writers not active.

Cause: One or more of the database writer processes is no longer running.

Action: Check the trace files for the database writers. Shut down the database and try to warm start.

ORA-08313: sllfop: could not allocate buffers

Cause: Memory for the load buffers could not be allocated.

Action: Reduce the maximum record size. Eliminate any unnecessary processes on your current node before running SQL*Loader again.

ORA-09701: scnfy: maximum number of processes exceeded

Cause: PROCESSES INIT.ORA parameter exceeded.

Action: Decrease the PROCESSES parameter and restart.

ORA-09922: Can't spawn process - background log directory not created properly

Cause: ORACLE was unable to spawn a background process because the directory that will hold trace files of the background processes was not created properly.

Action: Examine the directory pointed to by the initialization parameter "background_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-09923: Can't spawn process - user log directory not created properly

Cause: ORACLE was unable to spawn a background process because the directory that holds the trace files of the dedicated server processes was not created properly.

Action: Examine the directory pointed to by the initialization parameter "user_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-09924: Can't spawn process - core dump directory not created properly

Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.

ORA-09978: skxfqhdel: Error Disconnecting from another endpoint.

Cause: The process was unable to disconnect cleanly from another endpoint.

Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.

ORA-09979: skxfqhsnd: Error Sending a message to another endpoint

Cause: The process was unable to send a message to an existing endpoint.

Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.

ORA-09980: skxfqdrcv: Error Receiving a message from another endpoint

Cause: The process encountered an error while trying to receive a message.

Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.

ORA-09983: skxfidsht: Error shutting down SDI channel

Cause: The process was unable shut down the SDI channel

Action: Check the SDI persistent resources using SDI tools. Verify that all processes exited cleanly and the instance is safely shut down. Delete any remaining SDI channel IDs associated with the current instance.

ORA-10690: Set shadow process core file dump type (Unix only)

Cause: Control core file size for shadow processes

Action: Level 1: Detach SGA before dumping core Level 2: Do not produce any core

ORA-10691: Set background process core file type (Unix only)

Cause: Control core file size file for background processes

Action: Level 1: Detach SGA before dumping core

ORA-12634: Memory allocation failed

Cause: Process was unable to allocate memory.

Action: Terminate other processes in order to reclaim needed memory.

ORA-12643: Client received internal error from server

Cause: The client process received an error from the server that indicated that an internal Oracle Net native services error had occurred.

Action: Enable tracing on both processes and attempt to recreate the problem. If successful in recreating the problem, contact Oracle Customer Support.

ORA-12676: Server received internal error from client

Cause: The server process received an error from the client which indicated that an internal Oracle Net native services error had occurred.

Action: Enable tracing on both processes and attempt to recreate the problem. If the problem recurs, contact Oracle Customer Support.

This parameter is documented in the Oracle Server Reference Guide. Search for more info about [ processes ] on the Oracle FAQ.