ORA-02797: No requests available

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-02796: Done request is not in correct state

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-02795: Request list is empty

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-02794: Client unable to get key for shared memory

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-02793: Close of asynchronous I or O failed.

ORA-02793: Close of asynchronous I or O failed.

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

Action: Contact ORACLE support - this should not happen.

ORA-02792: Unable to fstat() a file being used for asynchronous I or O.

ORA-02792: Unable to fstat() a file being used for asynchronous I or O.

Cause: The fstat(2) call on a file being used for asynchronous I or O failed.

Action: Check the file name.

ORA-02791: Unable to open file for use with asynchronous I or O

ORA-02791: Unable to open file for use with asynchronous I or O

Cause: The package could not open file for some reason.

Action: Check the file name.

ORA-02790: File name is too long

ORA-02790: File name is too long

Cause: The length of the name of a file that is being opened for asynchronous I or O is longer than the maximum. The additional information field is the maximum length.

Action: Use a shorter name.

ORA-02789: Maximum number of files reached

ORA-02789: Maximum number of files reached

Cause: The maximum number of files that can be used for asynchronous I or O has been reached.

Action: Shut down the servers and re-initialize the package with a higher number.

ORA-02788: Unable to find kernel process pointer in async process array

ORA-02788: Unable to find kernel process pointer in async process array

Cause: Internal error - Contact ORACLE support.

Action: none

ORA-02787: Unable to allocate memory for segment list

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-02786: Size needed for shared region is greater than segment size

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-02785: Invalid shared memory buffer size

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-02784: Invalid shared memory ID specified

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-02783: Both post and wait functions were not specified

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-02782: Both read and write functions were not specified

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-02781: Invalid value given for the timing wanted flag

ORA-02781: Invalid value given for the timing wanted flag

Cause: The value given was not TRUE or FALSE.

Action: none

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

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-02779: Stat failed on core dump directory

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-02778: Name given for the log directory is invalid

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-02777: Stat failed on log directory

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-02776: Value for request done signal exceeds maximum

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-02775: Invalid request done signal

ORA-02775: Invalid request done signal

Cause: The signal number was not a positive number.

Action: Use a positive number.

ORA-02774: Invalid request list latch time out value

ORA-02774: Invalid request list latch time out value

Cause: The time given was not a positive number.

Action: Use a positive number.

ORA-02773: Invalid maximum client wait time

ORA-02773: Invalid maximum client wait time

Cause: The time given was not a positive number.

Action: Use a positive number.

ORA-02772: Invalid maximum server idle time

ORA-02772: Invalid maximum server idle time

Cause: The time given was not a positive number.

Action: Use a positive number.

ORA-02771: Illegal request time out value

ORA-02771: Illegal request time out value

Cause: The number was not a positive number.

Action: Use a positive number.

ORA-02770: Total number of blocks is invalid

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-02769: Setting of handler for SIGTERM failed

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-02768: Maximum number of files is invalid

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-02767: Less than one request descriptor was allocated per server

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-02766: Invalid maximum of request descriptors

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-02765: Invalid maximum number of servers

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-02764: Invalid package mode

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-02763: Unable to cancel at least one request

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-02762: file number to be cancelled is greater than the maximum.

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-02761: File number to be canceled is negative.

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-02760: Client close of file failed.

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-02759: Not enough request descriptors available

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-02758: Allocation of internal array failed

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-02757: osnfop: fork_and_bind failed

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-02756: osnfsmnam: name translation failure

ORA-02756: osnfsmnam: name translation failure

Cause: The Fast driver encountered an error translating the shared memory filename ? or dbs or ftt_lamp;lt;lamp;nbsp;pidlamp;gt;.dbf.

Action: Contact your customer support representative.

ORA-02755: osnfsmcre: cannot create chared memory file ? or dbs or ftt_lamp;lt;lamp;nbsp;pidlamp;gt;.dbf

ORA-02755: osnfsmcre: cannot create chared memory file ? or dbs or ftt_lamp;lt;lamp;nbsp;pidlamp;gt;.dbf

Cause: The Fast driver failed to create a file for shared memory.

Action: Check the permissions on the directory ? or dbs

ORA-02754: osnfsmmap: cannot change shared memory inheritence

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-02753: osnfsmmap: cannot close shared memory file

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-02752: osnfsmmap: illegal shared memory address

ORA-02752: osnfsmmap: illegal shared memory address

Cause: The Fast driver failed to attach shared memory at the expected location.

Action: Contact your customer support representative.

ORA-02751: osnfsmmap: cannot map shared memory file

ORA-02751: osnfsmmap: cannot map shared memory file

Cause: The Fast driver failed to map a shared memory file for two-task communication.

Action: Contact your customer support representative.

ORA-02750: osnfsmmap: cannot open shared memory file ? or dbs or ftt_lamp;lt;lamp;nbsp;pidlamp;gt;.dbf

ORA-02750: osnfsmmap: cannot open shared memory file ? or dbs or ftt_lamp;lt;lamp;nbsp;pidlamp;gt;.dbf

Cause: The Fast driver failed to create a shared memory file for two-task communication.

Action: Check the permissions on the directory ? or dbs

ORA-02739: osncon: host alias is too long

ORA-02739: osncon: host alias is too long

Cause: The alias used for a sqlnet host is longer than 161 characters.

Action: Use a shorter alias.

ORA-02738: osnpwrtbrkmsg: incorrect number of bytes written

ORA-02738: osnpwrtbrkmsg: incorrect number of bytes written

Cause: The pipe driver apparently sent an imcomplete break message.

Action: Contact your customer support representative.

ORA-02737: osnpcl: cannot tell orapop to exit

ORA-02737: osnpcl: cannot tell orapop to exit

Cause: The Pipe driver failed to send orapop the command to exit.

Action: Contact your customer support representative.

ORA-02736: osnfpm: illegal default shared memory address

ORA-02736: osnfpm: illegal default shared memory address

Cause: The Fast driver failed to establish a default shared memory address.

Action: Contact your customer support representative.

ORA-02735: osnfpm: cannot create shared memory segment

ORA-02735: osnfpm: cannot create shared memory segment

Cause: The Fast driver failed to create a shared memory segment for two-task communication.

Action: Check whether the system-imposed limit on shared memory identifiers has already been reached for your system.

ORA-02734: osnftt: cannot reset shared memory permission

ORA-02734: osnftt: cannot reset shared memory permission

Cause: The Fast driver was unable to reset shared memory permissions.

Action: Contact your customer support representative.

ORA-02733: osnsnf: database string too long

ORA-02733: osnsnf: database string too long

Cause: While converting a database alias to a database ID, the resulting database ID string exceeded the ORACLE system-imposed limit.

Action: Contact your customer support representative.

ORA-02732: osnrnf: cannot find a matching database alias

ORA-02732: osnrnf: cannot find a matching database alias

Cause: Database alias specified was not identified in either $HOME or .sqlnet or or etc or sqlnet.

Action: Create the alias in a file called .sqlnet in your home directory for personal use or ask your system administrator to create the alias in or etc or sqlnet for system-wide use.

ORA-02731: osnrnf: malloc of buffer failed

ORA-02731: osnrnf: malloc of buffer failed

Cause: The specified driver could not find enough heap space to malloc a buffer.

Action: Contact your customer support representative.

ORA-02730: osnrnf: cannot find user logon directory

ORA-02730: osnrnf: cannot find user logon directory

Cause: The driver you have specified could not find your logon directory while searching for your local .sqlnet file.

Action: Set and export the HOME environment variable to identify your home directory. Check with your system administrator to make sure that your uid and home directory are correct in the or etc or passwd file.

ORA-02729: osncon: driver not in osntab

ORA-02729: osncon: driver not in osntab

Cause: The driver you have specified is not supported.

Action: Check with your database administrator which drivers are supported.

ORA-02728: osnfop: access error on oracle executable

ORA-02728: osnfop: access error on oracle executable

Cause: The Fast driver could not access the oracle executable.

Action: Check the permissions on the ORACLE executable and each component of the ORACLE_HOME or bin path.