Release 9.0.1
Part Number A88783-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle Dynamic Services User's and Administrator's Guide Release 9.0.1 Part Number A88783-01 |
|
The following sections describe the error messages of Oracle Dynamic Services.
The following errors are associated with execution engine exceptions:
Cause: A DSConnection object attempts to make any call before the connection is established.
Action: Make sure the connection has been established for the DSConnection object.
Cause: A DSConnection object attempts to establish a connection after the connection is established.
Action: Make sure that the DSConnection object does not establish a connection again.
Cause: A service consumer application attempts to modify Dynamic Services properties without the required privilege.
Action: Connect as DSSYS to modify a Dynamic Services property.
Cause: The requested Dynamic Services property is not found.
Action: Make sure the name of the property is correct, including the case. If the name of the property is correct, contact Oracle Customer Support Services.
Cause: Unknown error occurred during the processing of Dynamic Services properties.
Action: Contact Oracle Customer Support Services.
Cause: An unexpected runtime exception occurred during service execution.
Action: Contact Oracle Customer Support Services.
Cause: A mandatory header of a message is missing.
Action: Contact Oracle Customer Support Services.
Cause: The payload of a message is missing during validation.
Action: Populate the payload of the message.
Cause: The payload of a message is not well-formed XML.
Action: Correct the payload of a message so that it is well-formed.
Cause: Input/output related error occurred in writing the payload to a message from the designated Reader.
Action: Resolve the hardware or software failure that causes the error.
Cause: Input/output related error occurred in writing the payload to the designated Writer from a message.
Action: Resolve the hardware or software failure that causes the error.
Cause: Some error related to Java Messaging Service (JMS) occurred in deserializing a message from the message queue.
Action: Make sure the message queue and the associated hardware/software are functioning.
Cause: The supplied XPath, used to access a message, is not valid.
Action: Contact Oracle Customer Support Services.
Cause: An XSLT or XPath related error happened in processing a message.
Action: Contact Oracle Customer Support Services.
Cause: The message is of unrecognized type.
Action: Contact Oracle Customer Support Services.
Cause: An event message is invalid.
Action: Contact Oracle Customer Support Services.
Cause: Some error related to Java Messaging Service (JMS) occurred in deserializing an event from the event message queue.
Action: Make sure the event message queue and the associated hardware/software are functioning.
Cause: The payload of an event, generated by the service execution engine, is not well-formed XML unexpectedly.
Action: Contact Oracle Customer Support Services.
Cause: Invalid service consumer application credential is supplied in an attempt to connect to Dynamic Services engine.
Action: Supply a valid credential, such as a valid name and password combination. Contact your service administrator, if necessary.
Cause: The named module initialization failed due to failure in initializing the named queue.
Action: Make sure the installation and configuration of the named queue is correct.
Cause: The Request ID in a response message is unexpectedly null.
Action: Contact Oracle Customer Support Services.
Cause: Request count integrity is violated in an asynchronous DSDriver.
Action: Contact Oracle Customer Support Services.
Cause: The synchronous type is unexpectedly null in a message sent through an asynchronous channel.
Action: Contact Oracle Customer Support Services.
Cause: An input/output related error occurred in publishing an event.
Action: Make sure the associated hardware/software are functioning.
Cause: An error related to the message queue occurred in publishing an event.
Action: Make sure the message queue and the associated hardware/software are functioning.
Cause: Unexpected error occurred in event monitor daemon initialization.
Action: Make sure the event support installation and configuration is correct.
Cause: The user is unable to communicate with the registry. The inability to communicate with the registry might be a result of many factors, such as network partitioning, hardware or interface problems, failures on either the client or server side.
Action: Retry the call that causes the exception. If the problem persists, contact your system administrators.
Cause: The registry is not able to service the request. It might be unavailable for different reasons. For example, the server might be too busy to service the request, the server is running out of memory, and so forth.
Action: Retry the call that causes the exception.
Cause: The operation is not supported by the current release.
Action: Contact Oracle Customer Support Services for the workaround or the availability of the feature.
Cause: An attempt was made to remove a service category that contains subcategories or services.
Action: Remove all services and sub-categories under the category before re-attempting to remove the category.
Cause: Login to the registry is denied because of improper credential.
Action: Make sure the credential is correct. If the credential is correct, contact the service administrator.
Cause: The service consumer application attempted to perform an administrative operation without the required privilege.
Action: Ask the service administrator to perform the administrative operation.
Cause: The service consumer application does not have the service privilege for the named service.
Action: Ask the service administrator to grant the required service privilege to the service consumer application.
Cause: An attempt was made to revoke the administrative privilege of the service consumer application. However, the service consumer application does not have the administrative privilege.
Action: Do not revoke the administrative privilege.
Cause: An attempt was made to access a service that does not exist.
Action: Contact the service administrator to make sure that the service does exist and the required service privilege is granted.
Cause: An attempt was made to access a category that does not exist.
Action: Contact the service administrator to make sure that the category does exist.
Cause: An attempt was made to access a property that does not exist.
Action: Contact the service administrator to make sure that the property does exist for the connected service consumer application.
Cause: An attempt was made to access a service consumer application that does not exist.
Action: Contact the service administrator to make sure that the service consumer application does exist.
Cause: An attempt was made to access the metadata of an engine instance that has not been registered.
Action: Contact the service administrator to make sure that the engine instance is registered.
Cause: An attempt was made to access a document that does not exist. Examples of documents include input schema, output schema, input renderers, and output renderers.
Action: Contact the service administrator to make sure that the requested document does exist.
Cause: An attempt was made to access a binary file that does not exist. Examples include .jar file that contains specific resources or custom adaptors.
Action: Contact the service administrator to make sure that the requested binary does exist.
Cause: During service registration, the category specified in the service descriptor does not exist in the registry.
Action: Create the required category before registering the service.
Cause: The service to be registered already exists.
Action: If the intention is to replace the existing service, perform reregister. Otherwise, no action needs to be taken since the service already exists.
Cause: The category to be added already exists.
Action: No action needs to be taken since the category already exists.
Cause: The property to be added already exists.
Action: If the intention is to replace the existing property, remove the existing property before adding the property. Otherwise, no action needs to be taken since the property already exists.
Cause: The service consumer application to be added already exists.
Action: No action needs to be taken since the service consumer application already exists.
Cause: The engine instance to be registered already exists.
Action: If the intention is to update the metadata of the engine instance, unregister the current engine instance before registering it again. Otherwise, no action needs to be taken since the engine instance has been registered.
Cause: The named XML document, typically part of a service package, is not valid.
Action: Make sure the named XML document is XML well-formed and valid.
Cause: An error occurred in accessing the named component of a service package. It is typically a file in a service package.
Action: Make sure the component does exist and is accessible. If the service package is a file-based service package, make sure the path is correct.
Cause: The required element (or attribute) which serves as a key of the component is missing.
Action: Make sure the component does contain the required element (or attribute).
Cause: The category supplied is null or syntactically invalid.
Action: Make sure the category string is non-null and follows LDAP DN syntax.
Cause: An invalid classification scheme constant was used in conducting a search of services.
Action: Make sure the constant being used is one of those defined in the Java interface oracle.ds.registry.DSClassificationConstants.
Cause: The keyword supplied is null.
Action: Make sure the keyword string is non-null.
Cause: The interface name supplied is null.
Action: Make sure the interface name string is non-null.
Cause: The engine instance metadata supplied is null or invalid.
Action: Make sure the supplied metadata is non-null and is valid.
Cause: The object being accessed is invalid for some unexpected reason.
Action: Contact Oracle Customer Support Services.
Cause: An unexpected mis-configuration occurred.
Action: Make sure the installation is successful. If the installation is successful and you still get this error, contact Oracle Customer Support Services.
Cause: An unexpected mis-configuration occurred.
Action: Contact Oracle Customer Support Services.
Cause: An unexpected mis-configuration occurred.
Action: Make sure the installation is successful. If the installation is successful and you still get this error, contact Oracle Customer Support Services.
Cause: An unexpected internal error occurred.
Action: Contact Oracle Customer Support Services.
Cause: The integrity of the registry is compromised, possibly because of external intervention to the registry.
Action: Use a backup of the registry, if available. Otherwise, contact Oracle Customer Support Services.
Cause: An unexpected internal error occurred.
Action: Contact Oracle Customer Support Services.
Cause: An unexpected internal error occurred.
Action: Contact Oracle Customer Support Services.
Cause: The request message sent from a service consumer application is invalid. The execution engine cannot process it.
Action: Make sure the service consumer application generates a valid request message.
Cause: The raw response returned by the protocol adaptor is not supported by the output adaptor used.
Action: Modify and re-register the service package to use an output adaptor that supports the type of raw response returned by the protocol adaptor.
Cause: An error occurred in processing the named response.
Action: Make sure the named response is a well-formed XML document.
Cause: The response produced is an empty one. It means that the response contains one and only one XML element and the element is an empty element without an attribute.
Action: Modify the parameters of the appropriate adaptor in the service package so that the service does not return an empty XML element only. Re-register the service package after the modification. The adaptor is typically an execution adaptor or an output adaptor.
Cause: The DS session ID supplied in executing a service is invalid or expired.
Action: Make sure the DS session ID is valid. Obtain a new session, if necessary.
Cause: The named adaptor cannot be loaded for any reason. A typical cause is that there is a typo in the adaptor name in the service package.
Action: Refer to the underlying exception for actions.
Cause: The adaptor parameter is invalid either during service registration or service execution.
Action: If the error occurs during service registration, check the syntax used of the adaptor parameter in the service package. If the error occurs during service execution, make sure all the other runtime requirements such as alias resolution have been satisfied.
Cause: The named alias specified in the adaptor parameter is missing in the ALIASES declaration in the service package.
Action: Make sure the named alias is defined with a proper value (a proper XPath, string constant, and so forth) in the service package. Re-register the service package if any modification is made.
Cause: The named XML document used by an adaptor is invalid.
Action: Make sure the XML document supplied is valid.
Cause: The named XSLT document used by an adaptor is invalid.
Action: Make sure the XSLT document supplied is valid.
Cause: A protocol adaptor is required in a service.
Action: Add a protocol adaptor to the service package and re-register the service package. If you believe a protocol adaptor is not required, contact the support responsible for the execution adaptor being used regarding the requirement on protocol adaptor.
Cause: The named protocol is not supported by the module.
Action: If there is an error in the name of the protocol, correct it. Otherwise, contact Oracle Customer Support Services.
Cause: An error occurred in HTML parsing. This error should only occur in development tools.
Action: Make sure the HTML specified is valid.
Cause: An error occurred in HTML parsing. This error should only occur in development tools.
Action: Make sure the HTML specified is valid.
Cause: An error occurred in HTML parsing. This error should only occur in development tools.
Action: Make sure the HTML specified is valid.
Cause: An error occurred in processing the XSQL request in DSJDBCProtocolAdaptor.
Action: Check the adaptor parameter in the service package and make sure the XSQL request is valid.
Cause: An error occurred in opening a JDBC connection in DSJDBCProtocolAdaptor.
Action: Make sure the adaptor parameter in the service package contains connection elements with valid parameters, and the connection attribute of the page element refers to a valid connection.
Cause: An error occurred in closing the JDBC connection in DSJDBCProtocolAdaptor.
Action: Refer to the underlying SQL exception for actions.
Cause: When a service is executed in a DS session, an attempt was made to re-use an existing JDBC connection. However, the JDBC connection refers to a different database/schema.
Action: Make sure all the JDBC-based services executed in a DS session do not declare connections with the same name but different connection string.
Cause: An HTTP transport error occurred with the named HTTP error code in DSHTTPProtocolAdaptor.
Action: Refer to the HTTP error code for resolution.
Cause: The named HTTP status code is not supported by DSHTTPProtocolAdaptor.
Action: Make sure the status code is not caused by errors in the service package or the service request. Contact Oracle Customer Support Services, if necessary.
Cause: An HTTP error (with status code 4XX and 5XX) was reported by the HTTP server.
Action: Refer to the underlying status code for further action. The error can also happen because of errors in the service to be executed, such as missing HTTP parameters.
Cause: DSHTTPProtocolAdaptor cannot follow a redirect command because the Location header is missing from the HTTP response.
Action: Contact the administrator of the HTTP server.
Cause: DSHTTPProtocolAdaptor encounters an invalid cookie.
Action: Contact the administrator of the HTTP server.
Cause: An error occurred in establishing an SMTP connection to the named host in DSSMTPProtocolAdaptor.
Action: Make sure the host name and the port number are valid. If they are correct, contact system administrators to resolve any network, hardware, or software issues.
Cause: An error occurred in closing an SMTP connection to the named host in DSSMTPProtocolAdaptor.
Action: Contact the administrator of the SMTP server.
Cause: An error occurred in sending the message to the SMTP server.
Action: Make sure the message is correctly formatted. If necessary, contact system administrators.
Cause: An SMTP error (with status code 4XX and 5XX) was reported by the SMTP server.
Action: Refer to the underlying status code for further action. The error can also happen because of errors in the service to be executed, such as missing SMTP headers, invalid email address in From header, and so forth.
Cause: DSSMTPProtocolAdaptor reported that the named header is missing from the email to be sent.
Action: Make sure the named header is present in the adaptor parameter in the service package.
Cause: The named operation is not supported by DSFILEProtocolAdaptor.
Action: Correct the operation to be used in the adaptor parameter in the service package.
Cause: An Input/output related error occurred in accessing a file with the named operation.
Action: Make sure the named operation can be done on the file.
Cause: One or more dependent services in a compound service, executed by DSCompoundServiceExecutionAdaptor, failed.
Action: Refer to the underlying exception for actions.
Cause: Multiple modules are defined with the same unique identifier incorrectly. The error is specific to DSCompoundServiceExecutionAdaptor.
Action: Find all the modules that share the same IDs in the adaptor parameter of the service package and specify different IDs for each of the modules. Re-register the modified service package.
Cause: A module is either missing the ID or the implementation class. The error is specific to DSCompoundServiceExecutionAdaptor.
Action: Fill in the missing ID or class in the Module element in the adaptor parameter of the service package. Re-register the modified service package.
Cause: The Graph element in the service package, which defines the connectivity of the modules, does not map to the module declaration. The error is specific to DSCompoundServiceExecutionAdaptor.
Action: Change the Graph element or the Module elements in the adaptor parameter of the service package so that each row in the graph maps to a module. Re-register the service package.
Cause: The name attribute of a row element in a Graph element in the service package is missing or empty. The error is specific to DSCompoundServiceExecutionAdaptor.
Action: Find the row element and fill in the name attribute. Re-register the modified service package.
Cause: The Graph element in the service package, which defines the connectivity of the modules, does not map to the module declaration. The error is specific to DSCompoundServiceExecutionAdaptor.
Action: Change the Graph element or the Module elements in the adaptor parameter of the service package so that each column in the graph maps to a module. Re-register the modified service package.
Cause: In the Graph element in the service package, there is no starting row (indicated by 0 in all column elements). Such a row is required to indicate the first module to be invoked. The error is specific to DSCompoundServiceExecutionAdaptor.
Action: Correct the Graph element so that one row is set to be a starting row: all of its column elements are 0. Re-register the modified service package.
Cause: The implementation class of the named module does not implement the required DSEventListener interface. The error is specific to DSCompoundServiceExecutionAdaptor.
Action: Check the name of the implementation class of the module in the service package. Make sure the name is one of the modules defined in the User's and Administrator's Guide. Re-register the modified service package.
Cause: More than one message was generated by the last module in a compound service execution flow. The error is specific to DSCompoundServiceExecutionAdaptor.
Action: Check the last module being executed and change it so that it does not generate multiple messages. For example, a ServiceExecution module should only be used with executeSingleRequest option. Re-register the modified service package.
Cause: The Graph element in the service package, which defines the connectivity of the modules, does not map to the module declaration. The error is specific to DSCompoundServiceExecutionAdaptor.
Action: Change the Graph element or the Module elements in the adaptor parameter of the service package so that each module maps to a row in the graph. Re-register the modified service package.
Cause: Unexpected exception occurred in cloning a message. The error is specific to DSCompoundServiceExecutionAdaptor.
Action: Refer to the underlying exception to resolve the problem causing the error.
Cause: In the Graph element in the service package, there are multiple modules identified as the ending module, indicated by multiple empty columns. The error is specific to DSCompoundServiceExecutionAdaptor.
Action: Correct the Graph element so that one and only one module is the ending module: one and only one column has all its values to be 0. Re-register the modified service package.
Cause: An entry in the adaptor parameter of a failover service is either missing the priority or the service ID.
Action: Correct the entry so that it has both the priority and the service ID. Re-register the modified service package.
Cause: It is an indication that the named service execution fails. The failover service will attempt to execute a backup service.
Action: Service administrators should try to resolve the problem by referring to the underlying exception.
Cause: A failover service execution failed because all of the backup services to be executed fail.
Action: Resolve any problems that cause the execution of the backup services to fail.
Cause: An internal error occurred in processing the Dynamic Services response cache.
Action: Refer to the underlying exception for actions.
Cause: An unexpected internal error occurred in service execution.
Action: Contact Oracle Customer Support Services.
Cause: An error occurred in the transport layer between a service consumer application and a service engine. The error code, if available, is the transport-specific error code.
Action: Correct the underlying transport layer error. Contact the relevant administrator, if necessary.
Cause: The content type of the message returned by the transport layer is incorrect.
Action: Contact the service administrator.
Cause: Session information is missing in the transport layer.
Action: Contact the service administrator.
Cause: The XSLT element of the named module is missing or invalid.
Action: Make sure the named module in the compound service execution adaptor parameter has a valid XSLT element.
Cause: The named module receives more messages than it is designed to handle.
Action: Check the GRAPH element in the compound service execution adaptor parameter. Make sure the named module receives the correct number of messages.
Cause: The named module receives no or null message.
Action: Check the GRAPH element in the compound service execution adaptor parameter. Make sure the named module receives the correct number of messages.
Cause: The named module expects to receive a message with the named index out of an array of messages.
Action: Check the GRAPH element in the compound service execution adaptor parameter. Make sure the module that produces messages to the named module does create an message at the named index.
Cause: The named module encounters XSLT error in applying the named XSLT stylesheet.
Action: Make sure the named XSLT stylesheet is correct with respect to the input source.
Cause: The service execution of the named module fails.
Action: Check the nested exception for resolution.
Cause: Unexpected exception occurred in the named module.
Action: Contact Oracle Customer Support Services.
Cause: The resulting XML of the named message splitter module does not contain the required sectioning tags.
Action: Check the single XSLT stylesheet used in the message splitter module and make sure the XML document generated is compliant to the specification required by single transformation in a MessageSplitter.
Cause: The named module cannot depend on more than one other module.
Action: Check the GRAPH element in the compound service execution adaptor parameter. Make sure the named module depends on one and only one other module.
|
 Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|