Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
Cause: Two-task driver failed to find the value of ORACLE_SID in the environment.
Action: Verify that the ORACLE_SID environment variable has been properly set and exported.
Cause: $ORACLE_HOME environment variable is not set.
Action: Verify that the $ORACLE_HOME environment variable has been properly set and exported.
Cause: $ORACLE_HOME environment variable is not set.
Action: Verify that the $ORACLE_HOME environment variable has been properly set and exported.
Cause: The pipe driver failed to create pipes for communications with the orapop process.
Action: Either the maximum number of open file descriptors per user has been exceeded, or the system file table is full. Examine the operating system error code, and contact system administrator.
Cause: The two-task driver failed to fork orapop.
Action: Verify that there are enough system resources to support another process. Either the user or system process limit has been exceeded, or the amount of free memory or swap space is temporarily insufficient.
Cause: The pipe driver failed while polling the communications channel.
Action: Contact Oracle Support.
Cause: The length of the host-string specified by the two-task environment variable exceeds the Oracle system-imposed limit.
Action: Contact Oracle Support.
Cause: The invoked UNIX two-task driver failed to allocate heap space for the context area.
Action: Contact Oracle Support.
Cause: The invoked UNIX two-task driver failed to find an entry in oratab for the sid supplied.
Action: Verify that there is read access to oratab, and verify that the desired sid is there. If necessary, add an entry to oratab for the desired sid.
Cause: The pipe driver failed to create pipes for two-task communications with the oracle shadow process.
Action: Either the maximum number of open file descriptors per user has been exceeded, or the system file table is full. Examine the operating system error code, and contact system administrator.
Cause: The pipe driver failed to fork the oracle shadow process.
Action: Verify that there are enough system resources to support another process. Either the user or system process limit has been exceeded, or the amount of free memory or swap space is temporarily insufficient.
Cause: The pipe driver failed to write to the orapop process.
Action: Contact Oracle Support.
Cause: The pipe driver failed to allocate enough heap space for its context area buffers.
Action: Contact Oracle Support.
Cause: The pipe driver failed to read a message from the communications channel.
Action: Contact Oracle Support.
Cause: The pipe driver failed to write a message to the communications channel.
Action: Contact Oracle Support.
Cause: The pipe driver received a message with an unrecognizable message type.
Action: Contact Oracle Support.
Cause: The pipe driver received a message with an unrecognizable message type.
Action: Contact Oracle Support.
Cause: The pipe driver sent a message that was apparently successful, but the number of bytes transmitted did not match the number of bytes furnished to the driver.
Action: Contact Oracle Support.
Cause: The two-task driver failed to reset the connection.
Action: Contact Oracle Support.
Cause: The fast driver failed to fork the oracle shadow process.
Action: Verify that there are enough system resources to support another process. Either the user or system process limit has been exceeded, or the amount of free memory or swap space is temporarily insufficient.
Cause: When the fast driver was invoked, processes failed to attach to the shared memory buffer. Either an illegal shared memory attach address was supplied, or the system ran out of data space to accommodate the buffer.
Action: Invoke the fast driver later, or use the default attach address.
Cause: The fast driver failed to get a semaphore set. The system-imposed limit on semaphores or semaphore identifiers may have been exceeded.
Action: Examine the operating system error code, and contact system administrator.
Cause: The pipe driver failed to send a break message to orapop.
Action: Contact Oracle Support.
Cause: The pipe driver failed to send a break message to the oracle shadow process.
Action: Contact Oracle Support.
Cause: The pipe driver failed to send a break message to orapop.
Action: Contact Oracle Support.
Cause: The pipe driver failed to send a break message to the oracle shadow process. Kill system call failed.
Action: Examine errno, and contact Oracle Support.
Cause: The pipe driver failed to access the oracle executable.
Action: Verify the permissions on the oracle executable and each component of the $ORACLE_HOME/bin path.
Cause: The pipe driver failed to access the orapop executable.
Action: Verify the permissions on the orapop executable and each component of the $ORACLE_HOME/bin path.
Cause: The fast driver failed to access the oracle executable.
Action: Verify the permissions on the oracle executable and each component of the $ORACLE_HOME/bin path.
Cause: The driver specified is not supported.
Action: Verify with database administrator which drivers are supported.
Cause: The driver specified failed to find the logon directory while searching for the local .sqlnet file.
Action: Set and export the HOME environment variable to identify the home directory. Verify with system administrator that the uid and home directory are correct in the /etc/passwd file.
Cause: The specified driver failed to find enough heap space to malloc a buffer.
Action: Contact Oracle Support.
Cause: Database alias specified was not identified in either $HOME/.sqlnet or /etc/sqlnet.
Action: Create the alias in a file called .sqlnet in the home directory for personal use, or have system administrator create the alias in /etc/sqlnet for system-wide use.
Cause: While converting a database alias to a database ID, the resulting database ID string exceeded the Oracle system-imposed limit.
Action: Contact Oracle Support.
Cause: The fast driver failed to reset shared memory permissions.
Action: Contact Oracle Support.
Cause: The fast driver failed to create a shared memory segment for two-task communication.
Action: Verify whether the system-imposed limit on shared memory identifiers has been reached for system.
Cause: The fast driver failed to establish a default shared memory address.
Action: Contact Oracle Support.
Cause: The pipe driver failed to send orapop the command to exit.
Action: Contact Oracle Support.
Cause: The pipe driver apparently sent an incomplete break message.
Action: Contact Oracle Support.
Cause: The alias used for a sqlnet host is longer than 161 characters.
Action: Use a shorter alias.
Cause: The fast driver failed to create a shared memory file for two-task communication.
Action: Verify the permissions on the directory $ORACLE_HOME/dbs.
Cause: The fast driver failed to map a shared memory file for two-task communication.
Action: Contact Oracle Support.
Cause: The fast driver failed to attach shared memory at the expected location.
Action: Contact Oracle Support.
Cause: The fast driver failed to close the shared memory file.
Action: Contact Oracle Support.
Cause: The fast driver failed to alter the inheritance attributes of the shared memory.
Action: Contact Oracle Support.
Cause: The fast driver failed to create a file for shared memory.
Action: Verify the permissions on the directory $ORACLE_HOME/dbs.
Cause: The fast driver encountered an error translating the shared memory filename $ORACLE_HOME/dbs/ftt_.dbf.
Action: Contact Oracle Support.
Cause: The fast driver failed to fork a process onto the desired cluster and node number.
Action: Verify that the desired node number in sercose[0] and cluster ID in sercose[1]. If these are valid, contact Oracle Support.
Cause: The package failed 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.
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.
Cause: The client failed to close a file after forking the servers. This is a system problem.
Action: Contact system administrator.
Cause: The file number contained with the sfiov structure is less than zero. This may be a programming error.
Action: If this is not a programming error, contact Oracle Support.
Cause: The file number contained with the sfiov structure is greater than the maximum.
Action: If this is not a programming error, contact Oracle Support.
Cause: No requests were found that could be cancelled.
Action: This error occurs when all the requests with that file number have already been filled.
Cause: The mode of the package can only be parallel or duplex.
Action: Examine sfa.h for the correct values.
Cause: The number of servers given was less than or equal to zero.
Action: Use a number greater than zero.
Cause: The number of request descriptors was less than or equal to zero.
Action: Use a number greater than zero.
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.
Cause: The maximum number of files to be used by the package was less than or equal to zero.
Action: Use a positive number.
Cause: The package failed to set up handling by the server for the termination signal. This is an internal error.
Action: Contact Oracle Support.
Cause: The total number of blocks to be allocated for use by the package was not greater than zero.
Action: Use a positive number.
Cause: The number 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 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 signal number was not a positive number.
Action: Use a positive number.
Cause: The value sent to the package for use as the "request done" signal exceeds the maximum allowed by the operating system.
Action: Contact system administrator.
Cause: The package failed to get information about the directory where the log files are to reside.
Action: Verify the permissions on the directory, or use a different directory name.
Cause: The name given for the directory where the logs will be kept does not correspond to a directory.
Action: Use a different name.
Cause: The package failed to get information about the directory where the servers are to dump core in the event of an exception.
Action: Verify the permissions on the directory, or use a different directory name.
Cause: The name given for the directory where the server processes will dump core in the event of an exception does not correspond to a directory.
Action: Use a different name.
Cause: The value given was not TRUE or FALSE.
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.
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.
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.
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.
Cause: The size of the shared segment that was specified for the shared buffer region is less than the number of bytes required.
Action: The first field of the "additional information" field is the size needed. The second is the size of the segment. Use a larger size segment or let the package allocate its own.
Cause: The package failed to 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.
Cause: This is an internal error.
Action: Contact Oracle Support.
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.
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.
Cause: The package failed to open file.
Action: Verify the file name.
Cause: The fstat(2) call on a file being used for asynchronous I/O failed.
Action: Verify the file name.
Cause: The client failed to close a file being used for asynchronous I/O.
Action: Contact Oracle Support.
Cause: The client failed to get a key to obtain shared memory for use with shared memory. This is an internal error.
Action: Contact Oracle Support.
Cause: The client was signalled by a server that it was done with a request, but the "done" list was empty. This is an internal error.
Action: Contact Oracle Support.
Cause: A request is not in the right state. This is an internal error.
Action: Contact Oracle Support.
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.
Cause: The number of operations sent to either sfard() or sfawrite() is less than zero.
Action: This is a user programming error.
Cause: The arming of a signal handler for the "done" signal failed. This is an internal error.
Action: Contact Oracle Support.
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. Contact Oracle Support.
Cause: Some asynchronous operations timed out in kernel mode. This is an internal error.
Action: Contact Oracle Support.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: The client failed to allocated a buffer for the name of the log file.
Action: Contact system administrator.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: The client failed to allocate memory for the array of I/O vectors that the servers will use.
Action: Contact system administrator.
Cause: The client failed to allocate memory for an array of flags that the servers will use.
Action: Contact system administrator.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: shmget(2) failed.
Action: Examine the UNIX number. If you are unsure what it means, contact Oracle Support.
Cause: shmat(2) failed.
Action: Examine the UNIX number. If you are unsure what it means, contact Oracle Support.
Cause: A server failed to die after being sent a kill signal. The process may be a runaway.
Action: Contact Oracle Support.
Cause: A server failed to read a requested amount of data. 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.
Action: Verify the call to sfard().
Cause: A server failed to 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 failed 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 be full.
Action: Examine the UNIX error number.
Cause: A server failed to write the requested amount of data out to disk. The disk may be out of space.
Action: Examine the UNIX error number.
Cause: A server failed to read the number of blocks that was requested. The end of the file may have been read.
Action: Verify the file on disk.
Cause: A server failed to seek to the designated block.
Action: Examine the UNIX error number.
Cause: The buffer on which an I/O is being done is not on the correct boundary.
Action: Verify the calling program.
Cause: The list from which the package allocates request descriptors is empty, because all the descriptors are in use.
Action: Wait until some become free, or initialize the package with a higher number of request descriptors.
Cause: This is an 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. This is a programming error.
Action: Use either a positive number or zero to get the default value.
Cause: The file number where an operation will be done is either less than zero or is greater than the maximum number of files than can be open.
Action: 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 failed to 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: Verify 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: Verify the calling program.
Cause: A server failed to close a file being used for asynchronous I/O.
Action: Examine the UNIX error number for more information.
Cause: The server failed to open a file for use with asynchronous I/O.
Action: Examine the UNIX error number for more information.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: The arming of a signal handler for the alarm signal failed. This is an internal error.
Action: Contact Oracle Support.
Cause: The server failed to flush its writes out to disk.
Action: Examine the UNIX error number.
Cause: The client process failed to open its log file.
Action: Examine the UNIX error number for more information.
Cause: A server exited during its initialization process.
Action: Examine the server logs for more information.
Cause: The client failed to spawn a server. Possibly, the operating system 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. This is a programming error.
Action: Verify the calling routine.
Cause: A value was given for the flag that determines whether a file is to be left open after the client verifies if the servers can use it. Only TRUE and FALSE are supported. This is a programming error.
Action: Verify 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. This is a programming error.
Action: Verify the calling routine.
Cause: A server failed to 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: Contact Oracle Support.
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 failed to read the requested amount of data from disk.
Action: Examine the UNIX error number.
Cause: A file where an asynchronous I/O operation will be performed has already been closed by the package. 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 the init.ora file is less than 0.
Action: Use a number that is greater than or equal to 0.
