Skip Headers
Oracle® Database Error Messages
11g Release 2 (11.2)

Part Number E17766-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

66 RDE-00000 to RDE-06020

RDE-00000: no error
Cause: Operation was successful.
Action: No action needed.
RDE-00001: unspecified error
Cause: An unknown error occurred. This is an internal error.
Action: Contact Oracle Customer Support and provide details about how and when the error occurred.
RDE-00002: provider busy
Cause: The provider is processing a request.
Action: This is not an error.
RDE-00003: no value found for service tag string.
Cause: A value was not found for the given service tag.
Action: This is normally not an error.
RDE-00004: operation timeout
Cause: A FIND or REGISTER operation timed out.
Action: For a FIND operation, this is only an error if the find was expected to successfully locate a service.
RDE-00005: invalid universe: "string"
Cause: An unknown universe was specified for the address.
Action: Specify a valid universe.
RDE-00006: invalid protocol: "string"
Cause: An invalid protocol was specified in an address.
Action: Specify a valid protocol.
RDE-00009: data too large for buffer. Buffer length: number. Required: number.
Cause: This error is for internal use only and should not normally be seen by users.
Action: Contact Oracle Customer Support.
RDE-00010: not found
Cause: A value was not found in a list.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-00011: invalid type: number
Cause: The type given for a piece of data was invalid.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-00012: no list name specified.
Cause: A name was not given for a list.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-00013: name busy.
Cause: This is an internal error.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-00014: operation was interrupted.
Cause: An operation was interrupted.
Action: None. This normally is not an error.
RDE-00015: load of provider library failed.
Cause: The load of a library which implements the interface for a provider failed.
Action: Enable tracing to determine the exact error that occurred.
RDE-00016: no provider libraries found.
Cause: It was not possible to locate any provider libraries.
Action: Make sure that the provider libraries have been installed.
RDE-00017: provider error.
Cause: A provider generated an error.
Action: If errors follow, examine them to determine the exact error. Otherwise, enable tracing to determine the exact error.
RDE-00018: regular expression compilation failed. Pattern "string" Error: number.
Cause: The creation of a pattern for use in a comparison failed.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-00019: pattern match failed. String: "string" Pattern: "string" Error: number.
Cause: A comparison against a regular expression failed.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-00020: no host name or IP address.
Cause: An address must contain either the name of the server or its IP address.
Action: Specify a host name or an IP address in the address.
RDE-00021: no providers found for universe "string".
Cause: A provider was not found for the specified universe.
Action: Either specify a different universe or obtain a provider library for that universe. Examine the errors that follow (if any) for more information.
RDE-00022: property not found.
Cause: A provider property was not found.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-00023: provider not found. Universe "string".
Cause: A provider was not found for the specified universe.
Action: Either specify a different universe or obtain a provider library for that universe.
RDE-00024: address invalid
Cause: The address is not in the correct format.
Action: Specify an address in the correct format. The syntax is described in rd.h.
RDE-00025: service type not specified.
Cause: The service type is not specified in the address.
Action: Specify an address with the service type.
RDE-00026: expected delimiter not found. Expected: "string" Found: "string"
Cause: The delimiter expected in the address was not found.
Action: Correct the address so that the delimiter is present.
RDE-00027: port number not found.
Cause: When a colon (":") follows the host name, it must be followed by a port number.
Action: Specify a port number.
RDE-00028: initialization failed.
Cause: Initialization of RD failed.
Action: Examine the errors that follow this one to determine the problem that is causing the error.
RDE-00029: no server found.
Cause: No server for the specified provider could be found to perform the desired operation.
Action: Start a server for the desired provider or use a different provider.
RDE-00030: memory allocation failure
Cause: An operation failed because it was not possible to allocate enough process memory.
Action: If memory is low on the system, terminate other processes and/or threads and try the operation again. Otherwise, this is an internal error and Oracle Customer Support should be contacted.
RDE-00031: invalid domain: number.
Cause: The application specified an invalid number for the domain.
Action: Specify a correct domain. See rd.h for the allowed values.
RDE-00032: length of service type "string" (number) is greater than than the maximum allowed: number
Cause: The user specified a service type which is longer than that permitted by the provider.
Action: Use a shorter service type.
RDE-00033: no universe specified.
Cause: The user did not specify a universe in the address.
Action: Specify a universe.
RDE-00034: address not registered: "string"
Cause: The application attempted to use an address which does not exist.
Action: Specify a registered address.
RDE-00037: invalid service instance tag: number
Cause: The value for a service instance tag was incorrect.
Action: Specify a valid tag. They are listed in rd.h.
RDE-00038: invalid protocol type: "string" Valid protocols: string
Cause: The user specified a protocol which is not supported by the provider.
Action: Specify a valid protocol. The protocol must be at least one character which is not a period (".").
RDE-00039: invalid host name: "string"
Cause: The name of the host specified was not in the correct format.
Action: Use the correct host name format. The host name must be one of the following:

1. The name of the machine;

2. A valid IPv4 address (N.N.N.N);

3. A valid IPv6 address (N[:N]*).

RDE-00040: invalid search domain: "string"
Cause: The name of the domain searched by the service was not in the correct format.
Action: Use the correct domain name format. A domain is a series of one or more alphanumeric characters.
RDE-00041: no protocol or domain specified.
Cause: The service name was followed by a period separator, but no protocol or domain was found after it.
Action: Specify a valid protocol and/or domain.
RDE-00042: invalid port number: "string"
Cause: The port specified in the service address was not valid. A port number may only be a positive decimal number.
Action: Specifiy a valid port number.
RDE-00043: no search domain specified.
Cause: No search domain followed the period separator.
Action: Specify a valid search domain.
RDE-00044: no protocol specified.
Cause: No protocol was specified for the service.
Action: Specify a valid protocol.
RDE-00045: port number required to register with a generic address.
Cause: Because of the requirements of some providers, the port number must be specified when registering using a generic address.
Action: Specify a port number.
RDE-00046: invalid attribute
Cause: An attribute was specified using an incorrect format.
Action: An attribute should be specified using the following format: "name=value[, name1=value1 ...]"
RDE-00047: no name specified for attribute.
Cause: A value was given for an attribute but no name was specified.
Action: Specify a name for the attribute.
RDE-00048: no attribute specified.
Cause: An attribute was not found in the address where it was expected.
Action: Specify a valid attribute. An attribute is composed of a name followed by an equals sign ("=") and then by an optional value. The name and value may both contain spaces.
RDE-00049: expected separator not found. Expected: "string" Found: "string"
Cause: The separator expected to be present between the mandatory and optional sections of the address was not found.
Action: Specify the separator.
RDE-00050: provider initialization for universe "string" failed.
Cause: The operation failed because providers could not be initialized for the specified universe.
Action: The message(s) that follow describe the errors encountered by the providers.
RDE-00051: provider "string" error.
Cause: The specified provider failed to perform an operation.
Action: The message(s) that follow describe the errors encountered by the provider.
RDE-00052: invalid numeric value specified: "string".
Cause: The value specified as a number was not valid.
Action: Specify a valid number.
RDE-00053: invalid or null service instance.
Cause: The service instance used for an operation is either invalid or null.
Action: Specify a valid service instance.
RDE-00054: invalid operation: number.
Cause: The operation specified was not valid.
Action: Specify a valid operation.
RDE-00055: no providers available.
Cause: No providers were available for an operation. This may be caused by the failure of a process or service needed by the provider (e.g. the mDNS service).
Action: Examine the trace and log files for details. Ensure that the process or service required by the process is running.
RDE-00056: registration of service instance "string" failed.
Cause: The registration of the specified service instance failed.
Action: Examine the errors that follow for more information about the error.
RDE-00057: unregistration of service instance "string" failed.
Cause: The deletion of the registration of the specified service instance failed.
Action: Examine the errors that follow for more information about the error.
RDE-00058: confirmation of service instance "string" failed.
Cause: The confirmation of the specified service instance failed.
Action: Examine the errors that follow for more information about the error.
RDE-00059: location of service types "string" failed.
Cause: It was not possible to retrieve types of services supported by Resource Discovery.
Action: Examine the errors that follow for more information about the error.
RDE-00060: service instance "string" was not found.
Cause: The location of the specified service.
Action: Examine the errors that follow for more information about the error.
RDE-00061: retrieval of details about service instance "string" failed.
Cause: It was not possible to get details about the specified service instance.
Action: Examine the errors that follow for more information about the error.
RDE-00062: termination failed.
Cause: The call to terminate the use of Resource Discovery failed.
Action: Examine the errors that follow for more information about the error.
RDE-00063: operation failed.
Cause: A FIND or REGISTER operation failed.
Action: Examine the errors that follow for more information about the error.
RDE-00064: retrieval of a provider for universe "string" failed.
Cause: It was not possible to retrieve a provider descriptor for the specified universe.
Action: Examine the errors that follow for more information about the error.
RDE-00065: creation of service instance failed.
Cause: An error occurred while trying to assemble a service instance using components.
Action: Examine the errors that follow for more information about the error.
RDE-00066: parsing of service instance "string" failed.
Cause: An error occurred while trying to parse the specified address.
Action: Examine the errors that follow for more information about the error.
RDE-00067: location of domain failed.
Cause: An error occurred while trying to locate domains of the specified type.
Action: Examine the errors that follow for more information about the error.
RDE-00068: length of universe component "string" (number) is longer than the maximum: number.
Cause: The string specified for the universe-specific portion of the service instance is longer than the maximum allowed by the provider.
Action: Specify a universe component which is shorter than the maximum. If this error occurs when no universe-specific portion was specified, the provider may have used the service type for the universe-specific component. In that case, make sure that the length of the service type does not exceed the maximum.
RDE-01999: internal error
Cause: RD failed due to some unforeseen reason.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-02000: invalid service type: "string"
Cause: The user specified a service type which does not conform to the standard specifed by RFC's 1034 and RFC 1123. The service type must be one or more characters and must start and end with a letter or digit. The interior characters may be letters, digits, or hyphens.
Action: Specify a service type which conforms to the RFC.
RDE-02001: failed to connect to the mDNS responder.
Cause: The provider was unable to make a connection with the mDNS responder.
Action: Check to ensure that the responder is running. If it is, this is an internal error and Oracle Customer Support should be contacted.
RDE-04000: client waiting
Cause: The client uses this error to signal to the server that it is waiting for query results.
Action: This error is used for signalling between the client and the DNS server. It should not be visible to the user. If it occurs, please contact Oracle Customer Support
RDE-04001: no error
Cause: Operation was successful.
Action: No action needed.
RDE-04002: unknown error has occurred
Cause: an unknown error has occurred.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-04003: no such name
Cause: a record could not be found with the given name.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-04004: memory allocation failed
Cause: An operation failed because it was not possible to allocate enough process memory.
Action: If memory is low on the system, terminate other processes and/or threads and try the operation again. Otherwise, this is an internal error and Oracle Customer Support should be contacted.
RDE-04005: invalid parameter
Cause: a record contained an illegal or non-existing value.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-04006: invalid reference
Cause: An unknown DNS record was found.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-04007: invalid state
Cause: This is an internal error.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-04008: invalid flags
Cause: This is an internal error.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-04009: unsupported operation
Cause: The provider interface attempted to perform an operation which is not supported by the provider.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-04010: not initialized
Cause: This is an internal error.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-04011: no cache allocated
Cause: a DNS query failed because no cache was allocated.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-04012: service already registered
Cause: The user attempted to register a service that was already registered.
Action: A service should only be registered once.
RDE-04013: service name conflict
Cause: The user attempted to register a service whose name already exists.
Action: A service should only be registered once.
RDE-04014: invalid record entry
Cause: The provider interface attempted to perform an operation whose record contained invalid or non-existent data.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-04015: client software incompatible with server
Cause: The version of the client software used by the provider interface is not compatible with the version of the server software.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-04016: invalid interface
Cause: The provider interface attempted to use an unknown interface.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-04017: cache size must be increased
Cause: The size of the cache maintained by the provider interface must be increased.
Action: This error is used as a status indicator. It should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-04018: configuration changed
Cause: The server configuration changed during an operation.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-04019: client should free resources
Cause: This error is used as an internal status indicator and should not be visible outside of the provider.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-06000: no more data
Cause: This error is used internally to signal that there is no more data to be passed by the SLP provider.
Action: This error is normal - no action is required.
RDE-06001: no error
Cause: Operation was successful.
Action: This error is normal - no action is required.
RDE-06002: language not supported
Cause: No service could be found that supports the language required.
Action: A service will have to be added or modified which supports the requested language.
RDE-06003: parse error
Cause: The SLP message rejected by a remote SLP agent.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-06004: invalid registration
Cause: The SLP provider attempted to register a URL which is malformed.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-06005: scope not supported
Cause: This is an internal error.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-06006: authenticator not provided
Cause: The SLP provider failed to authenticate itself.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-06007: authentication failed
Cause: The SLP provider failed to authenticate itself.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-06008: invalid update
Cause: An update for a non-existing registration was issued, or the update includes a service type or scope different than that in the initial registration, etc.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-06009: refresh rejected
Cause: Attempts were made to refresh a registration more frequently than the minimum refresh interval.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-06010: feature unimplemented
Cause: An unimplemented feature was used.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-06011: buffer overflow
Cause: An outgoing request overflowed the maximum network MTU size.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-06012: network timed out
Cause: An reply to an SLP request did not arrive in the configured timeout interval.
Action: Check the network connection and retry the request.
RDE-06013: network initialization failure
Cause: The network failed to initialize properly.
Action: Check the network connection and retry the request.
RDE-06014: memory allocation failed
Cause: The SLP provider was unable to allocate enough process memory.
Action: If memory is low on the system, terminate other processes and/or threads and try the operation again. Otherwise, this is an internal error and Oracle Customer Support should be contacted.
RDE-06015: invalid parameter
Cause: The provider attempted to pass an invalid parameter.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-06016: network error
Cause: The network failed to initialize properly.
Action: Check the network connection and retry the request.
RDE-06017: internal system error
Cause: The SLP subsystem failed for unknown reasons.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-06018: handle in use
Cause: The SLP provider attempted to recursively use a handle.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-06019: generic error
Cause: The provider failed for unknown reasons.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.
RDE-06020: unicast query must be sent.
Cause: The provider must send a unicast query.
Action: This error should not be visible to the user. If it occurs, please contact Oracle Customer Support.