Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
Cause: Insufficient swap space or system memory.
Action: Increase swap space or system memory.
Cause: Bad function parameter.
Action: Check function call.
Cause: Usually insufficient swap space or system memory.
Action: Increase swap space or system memory.
Cause: Failed to read data from an input device.
Action: Check the input device driver return code for further information.
Cause: Failed to write data to an output device.
Action: Check the output device driver return code for further information.
Cause: Failed to write data in the output buffer to an output device.
Action: Check the output device driver return code for further information.
Cause: An attempt to read or write data outside of a given data buffer.
Action: Check data buffer size.
Cause: An attempt was made to perform an operation which is not supported for the current mode.
Action: See documentation for a list of work modes and supported operations.
Cause: Could not identify transport layer parameters.
Action: Check the transport layer return code for further information.
Cause: Encountered an invalid record or an attempt to read beyond last record.
Action: See documentation for description of record handling methods.
Cause: Network address size is set to 0.
Action: See documentation for valid network address sizes.
Cause: Failed to send a message over network.
Action: Check the network interface return code for further information.
Cause: Failed to receive a network message.
Action: Check the network interface return code for further information.
Cause: Connection type is other than stream or message.
Action: See documentation for description of connection types.
Cause: Cannot do the encryption for the data.
Action: See the SNS documentation for more information.
Cause: Can not add the checksumming for the data.
Action: See the SNS documentation for more information.
Cause: An I/O operation returned with no data read/written because the transport connection is "non-blocking" and, to succeed, the operation would have needed to block.
Action: This is a soft error; retry the operation.
Cause: The format interpreter was given a data type it did not recognize.
Action: Check the types returned to the interpreter from either the type callback routine or from the type context structure.
Cause: The format interpreter was given an invalid type context.
Action: This error usually happens due to an improperly described aggregate. For example, declaring NCRF_END_STRUCT_DATA_TYPE within a context, without a complementary NCRF_STRUCT_DATA_TYPE, is invalid.
Cause: The data format layer received a session mode other than GET,PUT or FREE.
Action: No action required.
Cause: The data format layer received a floating point representation it did not recognize.
Action: Check incoming format descriptor for errors.
Cause: The data format layer received an improperly formed format descriptor. Subsequent data could not be formatted.
Action: Check for data integrity on receipt from remote host.
Cause: An error occurred while the interpreter was processing an NCRF_STREAM_DATA_TYPE.
Action: Check for data integrity, or for stream existence.
Cause: Failed to open tracing file.
Action: Make sure that this is a legal file name and that the user has write access.
Cause: An attempt to create either a call context or a service context has failed because all context slots are in use.
Action: Free context slots by destroying those contexts no longer required, or, reconfigure NCRO with more context slots.
Cause: Message read from service connection is not of the expected type. This is an application error.
Action: Debug and fix the application.
Cause: Message read from service connection is of unknown type. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Message read from service connection is for a call context that no longer exists. This is an application error.
Action: Debug and fix the application.
Cause: Attempted operation over call context is invalid. For example, attempting to send IN arguments for a procedure which is defined to have none. This is an application error.
Action: Debug and fix the application.
Cause: Attempted operation failed because service/call context is busy performing a previous operation. This is an application error.
Action: Debug and fix the application.
Cause: An attempt to execute a remote procedure has failed because the server has rejected the procedure ID.
Action: If wrong procedure ID, send the correct one. If the wrong server was contacted, then contact the right one.
Cause: Client and server NCRO layers are at incompatible versions levels.
Action: Upgrade to latest NCRO version.
Cause: Application transfer callback function has returned a "FAILED" status.
Action: Debug the transfer callback function.
Cause: Attempted operation has failed because the session context is in an invalid state. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Attempted operation is not supported on this service connection because it is incompatible with the NCRO version level of the remote application.
Action: Link remote application with latest NCR library.
Cause: A service context cannot be created because the transport address descriptor (contained in the binding context) is invalid. This is an application error.
Action: Initialize the transport address descriptor correctly.
Cause: A service context cannot be created because no transport address was provided (in the binding context) and the transport protocol uses datagrams. This is an application error.
Action: Provide a transport address.
Cause: Message read from service connection has bad address information. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Support for transport type RSLV has not been built.
Action: Re-compile the NCR library with NCR_USE_RSLV defined.
Cause: Failure to make RSLV connection usually means that the name resolution failed or the resolved TNS address is bad.
Action: Make sure that the name is in TNSNAMES.ORA and that it is set to the correct TNS address.
Cause: Attempt to initialize the Core thread package has failed. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The call context is not an valid call context.
Action: Call context was destroyed, probably because the Break was received
Cause: An Oracle partner is asking to reset the in-band line, after receiving a break.
Action: Reset the in-band line.
Cause: An error occurred when sending the break using the side-band channel.
Action: Read the documentation regarding to side-band break support issues.
Cause: An error occurred when receiving the break using the side-band channel.
Action: Read the documentation regarding to side-band break support issues.
Cause: Support for transport type LIST has not been built.
Action: Re-compile the NCR library with NCR_USE_LIST defined.
Cause: Failed to make LIST connection(s). This usually means one of the following:
Action: Check address list syntax and make sure that there is a 'listener' process for each (or some) of the supplied addresses.
Cause: The result buffer for holding the pickling result is too small.
Action: Enlarge the result buffer and try again.
Cause: Sender-makes-right needs the remote FID.
Action: Set up the remote session before using the Send Make's Right option.
Cause: Sender-makes-right was requested by the current side, but was refused by the server.
Action: Check the server side to see why it refused SMR.
Cause: An attempt to register an interface has failed because of an invalid interface descriptor.
Action: Check the interface descriptor passed into the NCRRRI_REGISTER_INTERFACE call.
Cause: An attempt to register an interface has failed because an interface already exists. This is an application error.
Action: Register a new interface, destroy the old one, or indicate that the old one must be replaced.
Cause: A service registration API call failed because of an invalid instance handle. This is an application error.
Action: Debug and fix the application.
Cause: A procedure/object registration failed because of an invalid procedural handle. This is an application error.
Action: Debug and fix the application.
Cause: A procedure registration failed because of an invalid argument descriptor. This is an application error.
Action: Debug and fix the application.
Cause: A service registration API call failed because of an invalid object handle, for example, one that does not exist. This is an application error.
Action: Debug and fix the application.
Cause: An attempt to register a remote procedure failed because the procedure already exists in this interface. This is an application error.
Action: Register a new procedure, destroy the old one, or indicate that the old one must be replaced.
Cause: An attempt to register an object failed because the object already exists in this interface. This is an application error.
Action: Register a new object, destroy the old one, or indicate that the old one must be replaced.
Cause: Service export or import failed to contact Names Server.
Action: Ensure the Oracle Names configuration is correct. If still no success, turn on Names tracing and/or contact Oracle Support Services.
Cause: Service export or import failed during interaction with Names Server.
Action: Turn on Names tracing and/or contact Oracle Support Services.
Cause: An NCRREI_EXPORT_INTERFACE call failed because of an invalid address descriptor. This is an application error.
Action: Debug and fix the application.
Cause: Attempted Names Server operation has failed because of insufficient authorization.
Action: Contact Oracle Support Services.
Cause: Service export or import failed because of an invalid instance name. This is an application error.
Action: Debug and fix the application.
Cause: Service export or import failed because of an invalid interface name. This is an application error.
Action: Debug and fix the application.
Cause: The instance handle passed in is the last instance handle in the list. This is an informational message indicating that the end of the list has been reached.
Action: No action required.
Cause: The instance handle corresponding to the instance name was not found. This is an application error.
Action: Debug and fix the application.
Cause: Unable to create the TNS address list from the interface instance list. This is an application error.
Action: Debug and fix the application.
Cause: Service export failed because the name already exists with the name server. This is an application error.
Action: Debug and fix the application.
Cause: Service expunge/query failed because the name does not exist in the name server.
Action: Turn on Names tracing and/or contact Oracle Support Services.
Cause: Service export/query failed because of pickler errors.
Action: Contact Oracle Support Services.
Cause: A procedure registration failed because of an invalid procedural descriptor. This is an application error.
Action: Debug and fix the application.
Cause: An object registration failed because of an invalid object descriptor. This is an application error.
Action: Debug and fix the application.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
