Oracle 12c R2 Error Codes and Solution Suggestions from ORA-02800 to ORA-02900
- 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.
Cause: Some asynchronous operations timed out in kernel mode.
Action: Internal error – contact ORACLE support.
Cause: Internal error.
Action: Contact ORACLE support.
Cause: Internal error.
Action: Contact ORACLE support.
Cause: The client was unable to allocated a buffer for the name of the log file.
Action: Contact your System Administrator.
Cause: Internal error.
Action: Contact ORACLE support.
Cause: Internal error.
Action: Contact ORACLE support.
Cause: The client was unable to allocate memory for the array of I/O vectors that the servers are to use.
Action: Contact your System Administrator.
Cause: The client was unable to allocate memory for an array of flags that the servers are to use.
Action: Contact your System Administrator.
Cause: Internal error.
Action: Contact ORACLE support.
- ORA-02810: Unable to make temporary file name for memory mapped file
- ORA-02811: Unable to attach shared memory segment
- ORA-02812: Bad attach address
- ORA-02813: Unable to make temporary file name in order to get key
Cause: Internal error.
Action: Contact ORACLE support.
Cause: Shmget(2) failed.
Action: Check the UNIX number. If you are unsure about what it means, contact ORACLE customer support.
Cause: Shmat(2) failed.
Action: Check the UNIX number. If you are unsure about what it means, contact ORACLE customer support.
Cause: A server did not die after being sent a kill signal.
Action: The process may be a runaway – contact ORACLE customer support.
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.
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.
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.
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.
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.
Cause: A server was unable to seek to the designated block.
Action: Check the UNIX error number.
Cause: The buffer on which an I/O is being done is not on the correct boundary.
Action: Check the calling program.
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.
Cause: Internal error.
Action: Contact ORACLE support.
Cause: A negative number was given for the I/O block size to be used by the asynchronous I/O package.
Action: This is a programming error – use either a positive number or zero to get the default value.
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.
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.
Cause: No segment of the proper size is ready for use by the caller.
Action: Free some segments and try again.
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.
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.
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.
Cause: A server was unable to close a file being used for asynchronous I/O.
Action: See the UNIX error number for more information.
Cause: The server was unable to open a file for use with asynchronous I/O.
Action: Check the UNIX error number for more information.
Cause: Internal error.
Action: Contact ORACLE support.
Cause: Internal error.
Action: Contact ORACLE support.
Cause: Internal error.
Action: Contact ORACLE support.
Cause: The arming of a signal handler for the alarmsignal failed.
Action: Internal error – contact ORACLE support.
Cause: The server was unable to flush its writes out to disk.
Action: Check the UNIX error number.
Cause: The client process was unable to open its log file.
Action: Check the UNIX error number for more information.
Cause: A server exited during its initialization process.
Action: Check the servers’ logs for more information.
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.
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.
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.
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.
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.
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.
Cause: An operation using the asynchronous I/O package was attempted without first initializing the package using sfainit().
Action: Call sfainit() before using the package.
Cause: A server could not read the requested amount of data from disk.
Action: Check the UNIX error number.
Cause: A file upon which an asynchronous I/O operation is to be performed has already been closed by the package.
Action: This is a programming error.
Cause: This is an internal problem.
Action: Contact ORACLE support.
Cause: The time given was not a positive number.
Action: Use a positive number.
Cause: The time given was not a positive number.
Action: Use a positive number.
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.
Cause: The value given for ‘db_slave_buffers’ in the initialization parameter file was 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.
Cause: Stated in errno.
Action: Resolve the problem.
Cause: Stated in errno.
Action: Resolve the problem.
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.
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.
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.
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.
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.
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.