ORA-02753: osnfsmmap: cannot close shared memory file
Cause: The Fast driver cannot close the shared memory file.
Action: Contact your customer support representative.
ORA-02754: osnfsmmap: cannot change shared memory inheritence
Cause: The Fast driver could not alter the inheritence attributes of the shared memory.
Action: Contact your customer support representative.
ORA-02755: osnfsmcre: cannot create chared memory file ?/dbs/ftt_<pid>.dbf
Cause: The Fast driver failed to create a file for shared memory.
Action: Check the permissions on the directory ?/dbs
ORA-02756: osnfsmnam: name translation failure
Cause: The Fast driver encountered an error translating the shared memory filename ?/dbs/ftt_<pid>.dbf.
Action: Contact your customer support representative.
ORA-02757: osnfop: fork_and_bind failed
Cause: The Fast driver failed to fork a process onto the desired cluster and node number.
Action: Check the desired node number in sercose[0] and cluster ID in sercose[1]. If these seem valid, contact customer support.
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-02759: Not enough request descriptors available
Cause: All of the package's request descriptors are in use performing other requests.
Action: Either wait until enough requests are done, or shut the package down and re-initialize it with more request descriptors.
ORA-02760: Client close of file failed.
Cause: The client was unable to close a file after forking the servers.
Action: This is a system problem - contact your System Administrator.
ORA-02761: File number to be canceled is negative.
Cause: The file number contained with the sfiov structure is less than zero.
Action: This may be a programming error. If it is not, contact ORACLE support.
ORA-02762: file number to be cancelled is greater than the maximum.
Cause: The file number contained with the sfiov structure is greater than the maximum.
Action: This may be a programming error. If it is not, contact ORACLE support.
ORA-02763: Unable to cancel at least one request
Cause: No requests were found that could be cancelled.
Action: This error can occur if all the requests dealing with that file number have already been filled.
ORA-02764: Invalid package mode
Cause: The mode of the package can only be parallel or duplex.
Action: See sfa.h for the correct values.
ORA-02765: Invalid maximum number of servers
Cause: The number of servers given was less than or equal to zero.
Action: Use a number greater than zero.
ORA-02766: Invalid maximum of request descriptors
Cause: The number of request descriptors was less than or equal to zero.
Action: Use a number greater than zero.
ORA-02767: Less than one request descriptor was allocated per server
Cause: The package requires that the number of request descriptors be greater than or equal to the number of servers used.
Action: Use a higher number
ORA-02768: Maximum number of files is invalid
Cause: The maximum number of files to be used by the package was less than or equal to zero.
Action: Use a positive number.
ORA-02769: Setting of handler for SIGTERM failed
Cause: The package was unable to set up handling by the server for the termination signal. This is an internal error.
Action: Contact ORACLE support.
ORA-02770: Total number of blocks is invalid
Cause: The total number of blocks to be allocated for use by the package was not greater than zero.
Action: Use a positive number.
ORA-02771: Illegal request time out value
Cause: The number was not a positive number.
Action: Use a positive number.
ORA-02772: Invalid maximum server idle time
Cause: The time given was not a positive number.
Action: Use a positive number.
ORA-02773: Invalid maximum client wait time
Cause: The time given was not a positive number.
Action: Use a positive number.
ORA-02774: Invalid request list latch time out value
Cause: The time given was not a positive number.
Action: Use a positive number.
ORA-02775: Invalid request done signal
Cause: The signal number was not a positive number.
Action: Use a positive number.
ORA-02776: Value for request done signal exceeds maximum
Cause: The value sent to the package for use as the "request done" signal exceeds the maximum allowed by the operating system.
Action: None
ORA-02777: Stat failed on log directory
Cause: The package was unable to get information about the directory in which the log files are to reside.
Action: Check the permissions on the directory or use a different directory name.
ORA-02778: Name given for the log directory is invalid
Cause: The name given for the directory in which the logs are to be kept does not correspond to a directory.
Action: Use a different name.
ORA-02779: Stat failed on core dump directory
Cause: The package was unable to get information about the directory into which the servers are to dump core in the event of an exception.
Action: Check the permissions on the directory or use a different directory name.
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-02781: Invalid value given for the timing wanted flag
Cause: The value given was not TRUE or FALSE.
Action: None
ORA-02782: Both read and write functions were not specified
Cause: To ensure that the functions act symmetrically, pointers to both the read and write functions must be given.
Action: Either specify both functions or specify neither. The package will supply its own functions.
ORA-02783: Both post and wait functions were not specified
Cause: To ensure that the functions act symmetrically, pointers to both the posting and waiting functions must be given.
Action: Either specify both functions or specify neither. The package will supply its own functions.
ORA-02784: Invalid shared memory ID specified
Cause: The ID of the segment specified for use as the shared buffer region was invalid.
Action: Use a different ID, or let the package specify its own.
ORA-02785: Invalid shared memory buffer size
Cause: The size given for the shared memory segment to be used as the shared buffer region was less than or equal to zero.
Action: Use a positive number.
ORA-02786: Size needed for shared region is greater than segment size
Cause: The size of the shared segment that was specified for the shared buffer region is less than the number of bytes required. The first field of the "additional information" field is the size needed. The second is the size of the segment.
Action: Use a larger size segment or let the package allocate its own.
ORA-02787: Unable to allocate memory for segment list
Cause: The package cannot allocate memory for an internal segment list because the system has run out of memory. The "additional information" field is the amount of memory that the package attempted to allocate.
Action: None
ORA-02788: Unable to find kernel process pointer in async process array
Cause: Internal error - Contact ORACLE support.
Action: None
ORA-02789: Maximum number of files reached
Cause: The maximum number of files that can be used for asynchronous I/O has been reached.
Action: Shut down the servers and re-initialize the package with a higher number.
ORA-02790: File name is too long
Cause: The length of the name of a file that is being opened for asynchronous I/O is longer than the maximum. The "additional information" field is the maximum length.
Action: Use a shorter name.
ORA-02791: Unable to open file for use with asynchronous I/O
Cause: The package could not open file for some reason.
Action: Check the file name.
ORA-02792: Unable to fstat() a file being used for asynchronous I/O.
Cause: The fstat(2) call on a file being used for asynchronous I/O failed.
Action: Check the file name.
ORA-02793: Close of asynchronous I/O failed.
Cause: The client was unable to close a file being used for asynchronous I/O.
Action: Contact ORACLE support - this should not happen.
ORA-02794: Client unable to get key for shared memory
Cause: The client was unable to get a key so that it obtain shared memory for use with shared memory.
Action: Contact ORACLE support - this is an internal error.
ORA-02795: Request list is empty
Cause: The client was signalled by a server that it was done with a request but the "done" list was empty.
Action: Internal error - contact ORACLE support.
ORA-02796: Done request is not in correct state
Cause: A request is not in the right state.
Action: Internal error - contact ORACLE support.
ORA-02797: No requests available
Cause: No free request descriptors are available.
Action: Wait until some requests are filled and then retry the request, or shutdown the servers and initialize the package with a higher 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.
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-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-02801: Operations timed out
Cause: Some asynchronous operations timed out in kernel mode.
Action: Internal error - contact ORACLE support.
ORA-02802: No idle servers available in parallel mode
Cause: Internal error.
Action: Contact ORACLE support.
ORA-02803: Retrieval of current time failed
Cause: Internal error.
Action: Contact ORACLE support.
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-02805: Unable to set handler for SIGTPA
Cause: Internal error.
Action: Contact ORACLE support.
ORA-02806: Unable to set handler for SIGALRM
Cause: Internal error.
Action: Contact ORACLE support.
ORA-02807: Allocation of memory for I/O vectors failed.
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.
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-02809: Jump buffer not valid
Cause: Internal error.
Action: Contact ORACLE support.
ORA-02813: Unable to make temporary file name in order to get key
Cause: Internal error.
Action: Contact ORACLE support.
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-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-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-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-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-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-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-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-02822: Invalid block offset
Cause: A server was unable to seek to the designated block.
Action: Check the UNIX error number.
ORA-02823: Buffer is not aligned.
Cause: The buffer on which an I/O is being done is not on the correct boundary.
Action: Check the calling program.
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-02825: Request on free list was not free
Cause: Internal error.
Action: Contact ORACLE support.
ORA-02826: Illegal block size
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.
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-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-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-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-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-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-02833: Server was unable to close file
Cause: A server was unable to close a file being used for asynchronous I/O.
Action: See the UNIX error number for more information.
ORA-02834: Server unable to open file
Cause: The server was unable to open a file for use with asynchronous I/O.
Action: Check the UNIX error number for more information.
ORA-02835: Server unable to send signal to client
Cause: Internal error.
Action: Contact ORACLE support.
ORA-02836: Unable to create temporary key file
Cause: Internal error.
Action: Contact ORACLE support.
ORA-02837: Unable to unlink temporary file
Cause: Internal error.
Action: Contact ORACLE support.
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-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-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-02841: Server died on start up
Cause: A server exited during its initialization process.
Action: Check the servers' logs for more information.
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-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-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-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-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-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-02848: Asynchronous I/O package is not running
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.
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-02850: File is closed
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.
ORA-02851: Request list is empty when it should not be
Cause: This is an internal problem.
Action: Contact ORACLE support.
ORA-02852: Invalid critical-section time out value
Cause: The time given was not a positive number.
Action: Use a positive number.
ORA-02853: Invalid server list latch time out value
Cause: The time given was not a positive number.
Action: Use a positive number.
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-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-02875: smpini: Unable to get shared memory for PGA
Cause: Stated in errno.
Action: Resolve the problem.
ORA-02876: smpini: Unable to attach to shared memory for PGA
Cause: Stated in errno.
Action: Resolve the problem.
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-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-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-02880: smpini: Could not register PGA for protection
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-02881: sou2o: Could not revoke 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-02882: sou2o: Could not register SGA for protection
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-02899: smscre: Cannot create SGA with Extended Shared Memory feature
Cause: The environment variable EXTSHM was set before starting oracle.
Action: Unset the environment variable EXTSHM and startup oracle.
ORA-03001: unimplemented feature
Cause: This feature is not implemented.
Action: None
ORA-03002: operator not implemented
Cause: This is an internal error.
Action: Contact your customer support representative.
ORA-03007: obsolete feature
Cause: User attempted to use a feature which is no longer supported.
Action: None
ORA-03009: Incompatible OCI function call
Cause: An incompatible OCI function call was issued for new functionality.
Action: Do not use V7 OCI calls for this functionality.
ORA-03112: a server linked as single-task cannot use SQL*Net
Cause: A statement containing a SQL*Net connect string was issued to the single-task server. For example, a database link was used in a SQL statement.
Action: Do not use SQL*Net connect strings in a single-task environment.
ORA-03113: end-of-file on communication channel
Cause: The connection between Client and Server process was broken.
Action: There was a communication error that requires further investigation. First, check for network problems and review the SQL*Net setup. Also, look in the alert.log file for any errors. Finally, test to see whether the server process is dead and whether a trace file was generated at failure time.
ORA-03119: two-task detected inconsistent datatype specification
Cause: There was both a datatype, and an anonymous datatype declaration found.
Action: Correct the specification.
ORA-03122: attempt to close ORACLE-side window on user side
Cause: This is an internal error.
Action: Contact your customer support representative.
ORA-03123: operation would block
Cause: This is a status code that indicates that the operation cannot complete now.
Action: None; this is not an error. The operation should be retried again for completion.
ORA-03124: two-task internal error
Cause: Internal error.
Action: Contact your customer support representative.
ORA-03125: client-server protocol violation
Cause: The application received a bad escape sequence from the server and may indicate a problem with the client application user code.
Action: Contact your customer support representative.
No hay comentarios:
Publicar un comentario