ORA-02879: sou2o: Could not gain access to protected memory

ORA-02879: sou2o: Could not gain access to protected memory

Cause: This is an internal error, note error code in errno.

Action: Report to your customer support representative. Restarting your application or your computer may cure the problem.

ORA-02878: sou2o: Variable smpdidini overwritten

ORA-02878: sou2o: Variable smpdidini overwritten

Cause: The variable smpdidini was overwritten, probably by client code.

Action: Verify client code, e.g. Pro*C, for illegal memory access. If the problem occurs outside Single Task operation, contact your customer support representative.

ORA-02877: smpini: Unable to initialize memory protection

ORA-02877: smpini: Unable to initialize memory protection

Cause: The adspcinit program has not been executed.

Action: Execute the adscpinit program as shown in your Installation and Users Guide. If the problem persists, try rebooting your computer.

ORA-02876: smpini: Unable to attach to shared memory for PGA

ORA-02876: smpini: Unable to attach to shared memory for PGA

Cause: Stated in errno.

Action: Resolve the problem.

ORA-02875: smpini: Unable to get shared memory for PGA

ORA-02875: smpini: Unable to get shared memory for PGA

Cause: Stated in errno.

Action: Resolve the problem.

ORA-02855: Number of requests is less than the number of slaves

ORA-02855: Number of requests is less than the number of slaves

Cause: The value given for db_slave_buffers in your INIT.ORA file is less than the number specified for the number of slaves, db_slaves.

Action: Specify a number that is greater than that given for db_slaves Alternatively, specify 0. The kernel will supply the appropriate number.

ORA-02854: Invalid number of request buffers

ORA-02854: Invalid number of request buffers

Cause: The value given for db_slave_buffers in your INIT.ORA file is less than 0.

Action: Use a number that is greater than or equal to 0.

ORA-02853: Invalid server list latch time out value

ORA-02853: Invalid server list latch time out value

Cause: The time given was not a positive number.

Action: Use a positive number.

ORA-02852: Invalid critical-section time out value

ORA-02852: Invalid critical-section time out value

Cause: The time given was not a positive number.

Action: Use a positive number.

ORA-02851: Request list is empty when it should not be

ORA-02851: Request list is empty when it should not be

Cause: This is an internal problem.

Action: Contact ORACLE support.

ORA-02850: File is closed

ORA-02850: File is closed

Cause: A file upon which an asynchronous I or O operation is to be performed has already been closed by the package.

Action: This is a programming error.

ORA-02849: Read failed because of an error

ORA-02849: Read failed because of an error

Cause: A server could not read the requested amount of data from disk.

Action: Check the UNIX error number.

ORA-02848: Asynchronous I or O package is not running

ORA-02848: Asynchronous I or O package is not running

Cause: An operation using the asynchronous I or O package was attempted without first initializing the package using sfainit().

Action: Call sfainit() before using the package.

ORA-02847: Server did not terminate when posted

ORA-02847: Server did not terminate when posted

Cause: A server did not respond to a posted request to shutdown. The first number is the number of the server. The second is its UNIX process number. This is an internal problem.

Action: Contact ORACLE support.

ORA-02846: Unkillable server

ORA-02846: Unkillable server

Cause: A server would not respond to the termination signal. The first number is the number of the server. The second is its UNIX process number. This is an internal problem.

Action: This is an operating system problem.

ORA-02845: Invalid value for the timing wanted flag

ORA-02845: Invalid value for the timing wanted flag

Cause: A value was given for the flag that indicates that operations are to be timed out. Only TRUE and FALSE are supported.

Action: This is a programming error - check the calling routine.

ORA-02844: Invalid value for the leave open flag

ORA-02844: Invalid value for the leave open flag

Cause: A value was given for the flag that determines whether a file is to be left open after the client checks it to see if the servers can use it. Only TRUE and FALSE are supported.

Action: This is a programming error - check the calling routine.

ORA-02843: Invalid value for kernel flag

ORA-02843: Invalid value for kernel flag

Cause: An illegal value was given for the kernel flag in the information structure. Only TRUE and FALSE are permitted.

Action: This is a programming error - check the calling routine.

ORA-02842: Client unable to fork a server

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-02841: Server died on start up

ORA-02841: Server died on start up

Cause: A server exited during its initialization process.

Action: Check the servers logs for more information.

ORA-02840: Open of log file by client failed

ORA-02840: Open of log file by client failed

Cause: The client process was unable to open its log file.

Action: Check the UNIX error number for more information.

ORA-02839: Sync of blocks to disk failed.

ORA-02839: Sync of blocks to disk failed.

Cause: The server was unable to flush its writes out to disk.

Action: Check the UNIX error number.

ORA-02838: Unable to arm signal handler for the alarm signal

ORA-02838: Unable to arm signal handler for the alarm signal

Cause: The arming of a signal handler for the alarmsignal failed.

Action: Internal error - contact ORACLE support.

ORA-02837: Unable to unlink temporary file

ORA-02837: Unable to unlink temporary file

Cause: Internal error.

Action: Contact ORACLE support.

ORA-02836: Unable to create temporary key file

ORA-02836: Unable to create temporary key file

Cause: Internal error.

Action: Contact ORACLE support.

ORA-02835: Server unable to send signal to client

ORA-02835: Server unable to send signal to client

Cause: Internal error.

Action: Contact ORACLE support.

ORA-02834: Server unable to open file

ORA-02834: Server unable to open file

Cause: The server was unable to open a file for use with asynchronous I or O.

Action: Check the UNIX error number for more information.

ORA-02833: Server was unable to close file

ORA-02833: Server was unable to close file

Cause: A server was unable to close a file being used for asynchronous I or O.

Action: See the UNIX error number for more information.

ORA-02832: Segment deallocation failed - segment not on list

ORA-02832: Segment deallocation failed - segment not on list

Cause: The caller attempted to deallocate a segment that was not on the in use list. This is a programming error.

Action: Check the calling program.

ORA-02831: Segment deallocation failed - empty segment list

ORA-02831: Segment deallocation failed - empty segment list

Cause: The caller attempted to deallocate a segment but the in use list was empty. This is a programming error.

Action: Check the calling program.

ORA-02830: Segment could not be split - no free segments available

ORA-02830: Segment could not be split - no free segments available

Cause: A segment that is larger than that desired could not be split because no free segment was available.

Action: Free some segments and try again.

ORA-02829: No segment of the proper size is available

ORA-02829: No segment of the proper size is available

Cause: No segment of the proper size is ready for use by the caller.

Action: Free some segments and try again.

ORA-02828: Segment free list is empty

ORA-02828: Segment free list is empty

Cause: No segments are available to allocated.

Action: Free some segments or shut down the package and re-initialize it with a higher number of segments.

ORA-02827: Invalid file number

ORA-02827: Invalid file number

Cause: The file number upon which an operation is to done is either less than zero or greater than the maximum number of files than can be open.

Action: This is a programming error. Since the calling program should not touch this number, this is a programming error.

ORA-02826: Illegal block size

ORA-02826: Illegal block size

Cause: A negative number was given for the I or O block size to be used by the asynchronous I or O package.

Action: This is a programming error - use either a positive number or zero to get the default value.

ORA-02825: Request on free list was not free

ORA-02825: Request on free list was not free

Cause: Internal error.

Action: Contact ORACLE support.

ORA-02824: Request free list is empty

ORA-02824: Request free list is empty

Cause: The list from which the package allocates request descriptors is empty because all of the descriptors is in use.

Action: Wait until some become free, or initialize the package with a higher number of request descriptors.

ORA-02823: Buffer is not aligned.

ORA-02823: Buffer is not aligned.

Cause: The buffer on which an I or O is being done is not on the correct boundary.

Action: Check the calling program.

ORA-02822: Invalid block offset

ORA-02822: Invalid block offset

Cause: A server was unable to seek to the designated block.

Action: Check the UNIX error number.

ORA-02821: Unable to read the requested number of blocks.

ORA-02821: Unable to read the requested number of blocks.

Cause: A server could not read the number of blocks that was requested. The end of the file may have been read.

Action: Check the file on disk.

ORA-02820: Unable to write the requested number of blocks

ORA-02820: Unable to write the requested number of blocks

Cause: A server could not write the requested amount of data out to disk. The disk may have run out of space.

Action: Check the UNIX error number.

ORA-02819: Write failed

ORA-02819: Write failed

Cause: A server was unable to perform a write. The number in the additional information field is the starting block number of the data segment being written out. The first number in the additional information field is the block number being written out. The second is the actual number of bytes that was written out. The disk may have filled up.

Action: Check the UNIX error number.

ORA-02818: Less than the number of blocks requested was read in

ORA-02818: Less than the number of blocks requested was read in

Cause: A server could not read in the request amount of data. The first number in the additional information field is the block number being read in. The second is the actual number of bytes that was read in.

Action: This is a programming error.

ORA-02817: Read failed

ORA-02817: Read failed

Cause: A server could not read a requested amount of data.

Action: Check the call to sfard(). An incorrect file descriptor may have been sent to sfard(). The number in the additional information field is the starting block number of the data segment being read in.

ORA-02816: Unable to kill a process

ORA-02816: Unable to kill a process

Cause: A server did not die after being sent a kill signal.

Action: The process may be a runaway - contact ORACLE customer support.

ORA-02815: Unable to attach shared memory

ORA-02815: Unable to attach shared memory

Cause: Shmat(2) failed.

Action: Check the UNIX number. If you are unsure about what it means, contact ORACLE customer support.

ORA-02814: Unable to get shared memory

ORA-02814: Unable to get shared memory

Cause: Shmget(2) failed.

Action: Check the UNIX number. If you are unsure about what it means, contact ORACLE customer support.

ORA-02813: Unable to make temporary file name in order to get key

ORA-02813: Unable to make temporary file name in order to get key

Cause: Internal error.

Action: Contact ORACLE support.

ORA-02809: Jump buffer not valid

ORA-02809: Jump buffer not valid

Cause: Internal error.

Action: Contact ORACLE support.

ORA-02808: Allocation of memory of open files array failed.

ORA-02808: Allocation of memory of open files array failed.

Cause: The client was unable to allocate memory for an array of flags that the servers are to use.

Action: Contact your System Administrator.

ORA-02807: Allocation of memory for I or O vectors failed.

ORA-02807: Allocation of memory for I or O vectors failed.

Cause: The client was unable to allocate memory for the array of I or O vectors that the servers are to use.

Action: Contact your System Administrator.

ORA-02806: Unable to set handler for SIGALRM

ORA-02806: Unable to set handler for SIGALRM

Cause: Internal error.

Action: Contact ORACLE support.

ORA-02805: Unable to set handler for SIGTPA

ORA-02805: Unable to set handler for SIGTPA

Cause: Internal error.

Action: Contact ORACLE support.

ORA-02804: Allocation of memory failed for log file name

ORA-02804: Allocation of memory failed for log file name

Cause: The client was unable to allocated a buffer for the name of the log file.

Action: Contact your System Administrator.

ORA-02803: Retrieval of current time failed

ORA-02803: Retrieval of current time failed

Cause: Internal error.

Action: Contact ORACLE support.

ORA-02802: No idle servers available in parallel mode

ORA-02802: No idle servers available in parallel mode

Cause: Internal error.

Action: Contact ORACLE support.

ORA-02801: Operations timed out

ORA-02801: Operations timed out

Cause: Some asynchronous operations timed out in kernel mode.

Action: Internal error - contact ORACLE support.

ORA-02800: Requests timed out

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-02799: Unable to arm signal handler

ORA-02799: Unable to arm signal handler

Cause: The arming of a signal handler for the done signal failed.

Action: Internal error - contact ORACLE support.

ORA-02798: Invalid number of requests

ORA-02798: Invalid number of requests

Cause: The number of operations sent to either sfard() or sfawrite() is less than zero.

Action: This is a user programming error.