53 NCR-00001 to NCR-04028
- NCR-00001: NCR: Could not allocate memory
-
Cause: Insufficient swap space or system memory.
- NCR-00002: NCR: Invalid usage
-
Cause: Bad function parameter.
- NCR-00003: NCR: Initialization failure
-
Cause: Usually insufficient swap space or system memory.
- NCR-01003: NCRS: Read error.
-
Cause: Failed to read data from an input device.
- NCR-01004: NCRS: Write error.
-
Cause: Failed to write data to an output device.
- NCR-01005: NCRS: Failed to flush the output buffer.
-
Cause: Failed to write data in the output buffer to an output device.
- NCR-01006: NCRS: Data buffer overflow.
-
Cause: An attempt to read or write data outside of a given data buffer.
- NCR-01007: NCRS: Operation is not supported in a given mode.
-
Cause: Attempt to perform an operation which is not supported for the current mode.
- NCR-01008: NCRS: Failed to obtain transport parameters.
-
Cause: Could not identify transport layer parameters.
- NCR-01009: NCRS: Record handling error.
-
Cause: Encountered an invalid record or an attempt to read beyond last record.
- NCR-01010: NCRS: Invalid network address length.
-
Cause: Network address size is set to 0.
- NCR-01011: NCRS: Send message failure.
-
Cause: Failed to send a message over network.
- NCR-01012: NCRS: Receive message failure.
-
Cause: Failed to receive a network message.
- NCR-01013: NCRS: Unvalid connection type.
-
Cause: Connection type is other than stream or message.
- NCR-01018: NCRS: Encryption failure.
-
Cause: Can not do the encryption for the data.
- NCR-01019: NCRS: Checksumming failure.
-
Cause: Can not add the checksumming for the data.
- NCR-01020: NCRS: Operation would block.
-
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.
- NCR-02003: NCRF: Invalid type passed to format interpreter.
-
Cause: The format interpreter was given a data type it did not recognize.
- NCR-02004: NCRF: Invalid format interpreter type context
-
Cause: The format interpreter was given an invalid type context.
- NCR-02005: NCRF: Invalid session mode
-
Cause: The data format layer received a session mode other than GET,PUT or FREE.
- NCR-02006: NCRF: Invalid floating point representation received
-
Cause: The data format layer received a floating point representation it did not recognize.
- NCR-02007: NCRF: Invalid format descriptor received
-
Cause: The data format layer received an improperly formed format descriptor. Subsequent data could not be formatted.
- NCR-02008: NCRF: Error within stream processing in format interpreter
-
Cause: An error occured while the interpreter was processing an NCRF_STREAM_DATA_TYPE.
- NCR-02009: NCRF: Unable to open trace file
-
Cause: Failure to open tracing file.
- NCR-02010: NCRF: Call context is not available
-
Cause: Call context not passed to format context.
- NCR-02011: NCRF: Exceeded maximum number of rfids.
-
Cause: Exceeded maximum number of rfids.
- NCR-03002: NCRO: Maximum number of contexts has been reached
-
Cause: An attempt to create either a call context or a service context has failed because all context slots are in use.
- NCR-03003: NCRO: Unexpected message
-
Cause: Message read from service connection is not of the expected type.
- NCR-03004: NCRO: Unknown message
-
Cause: Message read from service connection is of unknown type.
- NCR-03005: NCRO: Orphan message
-
Cause: Message read from service connection is for a call context that no longer exists.
- NCR-03006: NCRO: Invalid operation
-
Cause: Attempted operation over call context is invalid. For example, attempting to send IN args for a procedure which is defined to have none.
- NCR-03007: NCRO: Context is busy
-
Cause: Attempted operation failed because service/call context is busy performing a previous operaion.
- NCR-03008: NCRO: Call rejected
-
Cause: An attempt to execute a remote procedure has failed because the server has rejected the procedure id.
- NCR-03009: NCRO: Protocol version mismatch
-
Cause: Client and server NCRO layers are at incompatible versions levels.
- NCR-03010: NCRO: Transfer callback error
-
Cause: Application transfer callback function has returned a "FAILED" status.
- NCR-03012: NCRO: Invalid session mode
-
Cause: Attempted operation has failed because the session context is in an invalid state.
- NCR-03013: NCRO: Operation not supportd
-
Cause: Attempted operation is not supported on this service connection because it is incompatible with the NCRO version level of the remote application.
- NCR-03014: NCRO: Bad transport address
-
Cause: A service context cannot be created because the transport address descriptor (contained in the binding context) is invalid.
- NCR-03015: NCRO: No transport address
-
Cause: A service context cannot be created because no transport address was provided (in the binding context) and the transport protocol uses datagrams.
- NCR-03016: NCRO: Message has bad address
-
Cause: Message read from service connection has bad address information.
- NCR-03017: NCRO: Transport type RSLV not supported
-
Cause: Support for transport type RSLV has not been built.
- NCR-03018: NCRO: Failed to make RSLV connection
-
Cause: Failure to make RSLV connection usually means that the name resolution failed or the resolved TNS address is bad.
- NCR-03019: NCRO: Unable to initialize thread support
-
Cause: Attempt to initialize the Core thread package has failed.
- NCR-03020: NCRO: Invalid call context
-
Cause: The call context is not an valid call context.
- NCR-03021: NCRO: Reset the in-band line
-
Cause: Our parnter is asking to reset the in-band line, after receiving a break
- NCR-03022: NCRO: Cannot send the break
-
Cause: There is an error occur when sending the break using the side-band channel
- NCR-03023: NCRO: Cannot receive the break
-
Cause: There is an error occur when receiving the break using the side-band channel
- NCR-03024: NCRO: Transport type LIST not supported
-
Cause: Support for transport type LIST has not been built.
- NCR-03025: NCRO: Failed to make LIST connection(s)
-
Cause: Failure to make LIST connection(s) usually means one of two things: (1) Address list syntax error, (2) Could not connect with supplied addresses
- NCR-03026: NCRO: The result buffer has overflowed
-
Cause: The result buffer for holding the pickling result is too small.
- NCR-03027: NCRO: No remote service session set up yet.
-
Cause: Sender-makes-right needs the remote FID.
- NCR-03028: NCRO: Partner refused request for sender-makes-right.
-
Cause: Sender-makes-right was requested by the current side, yet refused by the server.
- NCR-04002: NCRR: Invalid interface descriptor
-
Cause: An attempt to register an interface has failed because of an invalid interface descriptor.
- NCR-04003: NCRR: Interface exists
-
Cause: An attempt to register an interface has failed because an interface already exists.
- NCR-04004: NCRR: Invalid interface instance handle
-
Cause: A service registration API call has failed because of an invalid instance handle.
- NCR-04005: NCRR: Invalid procedure handle
-
Cause: A procedure/object registration has failed because of an invalid procedural handle.
- NCR-04006: NCRR: Invalid argument descriptor
-
Cause: A procedure registration has failed because of an invalid argument descriptor.
- NCR-04007: NCRR: Invalid object handle
-
Cause: A service registration API call failed because of an invalid object handle, for example, one that does not exist.
- NCR-04008: NCRR: Procedure exists
-
Cause: An attempt to register a remote procedure has failed because the procedure already exists in this interface.
- NCR-04009: NCRR: Object exists
-
Cause: An attempt to register an object has failed because the object already exists in this interface.
- NCR-04010: NCRR: Unable to contact Oracle Internet Directory Server
-
Cause: Service export or import failed to contact Oracle Internet Directory Server.
- NCR-04011: NCRR: Oracle Internet Directory error
-
Cause: Service export or import failed during interaction with Oracle Internet Directory Server.
- NCR-04012: NCRR: Invalid address descriptor
-
Cause: An ncrrei_export_interface call failed because of an invalid address descriptor.
- NCR-04013: NCRR: Insufficient authorization
-
Cause: Attempted Oracle Internet Directory Server operation has failed because of insufficient authorization.
- NCR-04014: NCRR: Invalid instance name
-
Cause: Service export or import failed because of an invalid instance name
- NCR-04015: NCRR: Invalid interface name
-
Cause: Service export or import failed because of an invalid interface name
- NCR-04016: NCRR: Last interface instance handle
-
Cause: The instance handle passed in is the last instance handle in the list.
- NCR-04017: NCRR: Unable to find the interface instance handle
-
Cause: The instance handle corresponding to the instance name was not found.
- NCR-04018: NCRR: Unable to create the TNS address list
-
Cause: Unable to create the TNS address list from the interface instance list.
- NCR-04019: NCRR: Interface or instance name already exists
-
Cause: Service export failed because the name already exists with the Oracle Internet Directory server
- NCR-04020: NCRR: Interface or instance name does not exist
-
Cause: Service expunge/query failed because the name does not exist with the Oracle Internet Directory server
- NCR-04021: NCRR: Pickler errors
-
Cause: Service export/query failed because of pickler errors
- NCR-04022: NCRR: Invalid procedure descriptor
-
Cause: A procedure registration has failed because of an invalid procedural descriptor.
- NCR-04023: NCRR: Invalid object descriptor
-
Cause: An object registration has failed because of an invalid object descriptor.
- NCR-04024: NCRR: Maximum number of procedures reached
-
Cause: A procedure registration has failed because the procedures array is filled up.
- NCR-04025: NCRR: Operation timed out
-
Cause: An operation for the Oracle Internet Directory server failed because it exceeded the timeout period.
- NCR-04026: NCRR: Operation not supported
-
Cause: An operation for the Oracle Internet Directory server failed because it met with a server referral to another instance.
- NCR-04027: NCRR: Operation failed
-
Cause: An operation for the Oracle Internet Directory server failed because the Service Registration interfaces met with invalid parameters.
- NCR-04028: NCRR: Operation failed
-
Cause: An operation for the Oracle Internet Directory server failed because the data involved exceeds the maximum allowed size.