processes

Oracle 11.1.0:

Oracle 10.2.0:

Oracle 10.1.0:

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-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-10005: trace latch operations for debugging

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-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.

ORA-12852: PARALLEL_MIN_SERVERS must be less than PROCESSES, %s

Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PROCESSES.

Action: Set PARALLEL_MIN_SERVERS to a value less than PROCESSES value specified in the accompanying message and retry.

ORA-16010: disable stale RFS process extermination

Cause: Disables the termination of RFS processes waiting for tcp_keepalive_interval to expire.

Action: No action is required.

ORA-16081: insufficient number of processes for APPLY

Cause: Logical standby apply engine was started with fewer processes available than needed.

Action: Increase the values of the initialization parameters PROCESSES and and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_LOGSTDBY_PARAMETERS view.

ORA-16155: enable arch procs to not exceed log_archive_max_processes

Cause: disallow arch processes to exceed log_archive_max_processes in releases prior to 9i. Note that in 9i and subsequent releases this event is not required. We reserve this event for 9i and subsequent releases to allow us to backport the new log_arch_max_processes behavior for earlier releases.

Action: No action is required.

ORA-16212: number processes specified for APPLY is too great

Cause: Logical standby apply engine was started with more processes requested than are available.

Action: Adjust the values of the initialization parameters PROCESSES and and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_LOGSTDBY_PARAMETERS view.

ORA-16403: shutdown in progress - remote connection is not permitted

Cause: The SHUTDOWN command was used to shut down a running remote primary or standby ORACLE instance, so the LGWR or ARCH processes cannot connect to ORACLE.

Action: Wait for the remote instance to be restarted, or contact your DBA.

ORA-17619: max number of processes using I/O slaves in a instance reached

Cause: An attempt was made to start large number of processes requiring I/O slaves.

Action: There can be a maximum of 35 processes that can have I/O slaves at any given time in a instance.

ORA-23386: replication parallel push cannot create slave processes

Cause: An attempt was made to start large number of processes requiring I/O slaves.

Action: There can be a maximum of 35 processes that can have I/O slaves at any given time in a instance.

ORA-24319: unable to allocate memory

Cause: Process was unable to allocate memory to store diagnostics.

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

ORA-26671: maximum number of STREAMS processes exceeded

Cause: Cannot create additional STREAMS processes since the maximum number of STREAMS processes has been reached.

Action: Remove existing STREAMS processes and retry the operation.

ORA-26685: cannot apply transactions from multiple sources

Cause: Transactions from multiple sources were sent to the same apply process.

Action: Create multiple apply processes and create appropriate rules so that transactions from only one source reach an apply process.

ORA-27092: size of file exceeds file size limit of the process

Cause: an attempt was made to open a file that exceeds the process's file size limit (ulimit), additional information shows the current limit (logical blocks) and the size of the file (logical blocks)

Action: increase the processes file size limit (ulimit) and retry

ORA-27142: could not create new process

Cause: OS system call

Action: check errno and if possible increase the number of processes

ORA-28751: memory allocation failure

Cause: The allocation of memory failed due to exhaustion of system memory.

Action: Terminate other processes to free up memory or add memory to the system.

ORA-28756: callback failure to allocate memory

Cause: A function supplied by the caller failed to allocate memory. This error could have been caused by system memory exhaustion.

Action: Terminate other processes to free up memory or add memory to the system.

ORA-28757: system attempt to allocate 0 bytes of memory

Cause: The system attempted to allocate 0 bypes of memory because there was no available memory left to allocate. This error could have been caused by system memory exhaustion.

Action: Terminate other processes to free up memory or add memory to the system.

ORA-28776: Output buffer supplied is too small.

Cause: The creation of a binding for use in the parsing of a parameter value failed. This error can be caused by the parameter value being in an incorrect format, e.g. a right parenthesis was not supplied where expected, or the exhaustion of system memory.

Action: Make sure that the parameter is specified in the correct format. If the format is correct, free up system memory by terminating processes or adding more memory.

ORA-28854: Memory allocation failure

Cause: The allocation of memory failed due to exhaustion of system memory.

Action: Terminate other processes to free up memory or add memory to the system.

ORA-28859: SSL negotiation failure

Cause: An error occurred during the negotiation between two processes as part of the SSL protocol. This error will occur if the two sides to the connection do not support a common cipher suite.

Action: Configure each process so they support a common cipher suite. Then attempt the connection again. If error occurs again enable Oracle Net tracing and attempt the connection again. Then contact Oracle customer support with the trace output.

ORA-30437: all job queue processes have stopped running

Cause: All of the job queue processes used by refresh have stopped for some reason. At least one job queue process must be running in order to refresh summaries.//

Action: This is an internal error. Notify ORACLE technical support

ORA-31420: unable to submit the purge job

Cause: When creating the first change table, a purge job is submitted to the job queue. Submission of this purge job failed.

Action: Make sure that job queue processes are enabled and are currently running. If this does not solve the problem, contact Oracle.//

ORA-31635: unable to establish job resource synchronization

Cause: A lock used in synchronizing Data Pump resources during job creation and deletion could not be obtained during job creation. This indicates that a process for some other Data Pump job has not released the lock due to an internal error.

Action: Eliminate the processes for any failed Data Pump job and try to create the new job again. If the error continues to occur, contact Oracle Customer Support and report the error.

ORA-31676: illegal value for number of workers, %s

Cause: Called create worker processes with an illegal number of workers specified.

Action: Make sure that the number of workers value is greater than 0 and less than the maximum value for the platform (normally 32767). If this error occurs from a Data Pump client (e.g. expdp or impdp) and you specified the parallel parameter, try the operation again with a smaller value for the parallel parameter. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31686: error creating worker processes

Cause: Setup to create worker processes failed.

Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31689: illegal value for base worker id, %s

Cause: Called create worker processes with an illegal base worker id value specified.

Action: Make sure that the base worker id value is greater than 0 and less than the maximum value for the platform (normally 32767). If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-32517: cannot issue ORADEBUG command (waited %d ms for process %s); total wait time exceeds %d ms

Cause: The process targeted to execute the ORADEBUG command was busy executing another ORADEBUG command. But, because the total wait time for all targeted processes exceeded the maximum wait time, the ORADEBUG command was not issued to the target process.

Action: Increase the timeout value.

ORA-32518: cannot wait for ORADEBUG command completion (waited %d ms for process %s); total wait time exceeds %d ms

Cause: The total wait time for all targeted processes exceeded the maximum wait time, therefore the wait for the targeted process to finish executing the ORADEBUG command was aborted.

Action: Increase the timeout value.//////////////////////////LITERAL REPLACEMENT////////////////////////////

ORA-39003: unable to get count of total workers alive

Cause: Attempt to get count of total worker processes alive failed.

Action: Check the additional error messages to see what caused the failure. Correct the error, if possible, and try the operation again. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39014: One or more workers have prematurely exited.

Cause: One or more of the worker processes exited before the job was completed. With no workers, the master process will terminate the job.

Action: Rerun the job. If problem persists, contact Oracle Customer Support.

ORA-39077: unable to subscribe agent %s to queue \"%s\"

Cause: The Data Pump's communication layer was unable to attach one of its processes to the control or status queue. Subsequent messages will detail the problem.

Action: Fix the problem if possible, or contact Oracle Customer Support.

ORA-39107: Master process %s violated startup protocol. Master error:

Cause: An attempt to delete the worker processes failed.

Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39118: . . imported %s %s out of %s rows

Cause: The master process that created this worker process called delete worker processes to abort the current operation.

Action: No action is necessary. This is an informational error message.

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