Skip Headers
Oracle® Real-Time Decisions Installation and Administration Guide
Version 3.0.0.1

Part Number E13856-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
View PDF

B Exceptions

Table B-1 lists the exceptions that may appear as messages in your Oracle RTD log files. Suggested actions are shown for each exception. If these actions do not resolve your problem, contact Oracle Support Services.

Note:

For error messages that may occur during Inline Service development, see Appendix A, "Development Error Messages" in Oracle Real-Time Decisions Platform Developer's Guide.

Table B-1 List of Exceptions

Exception Action

Error reading file file_name

Check that the file exists and has read permissions.

Error writing file file_name

Check that the file exists and has write permissions.

Cannot load Inline Service with id id. No Decision Service is present.

Check that the server where the Decision Service is deployed is running. Use JConsole to find where the Decision Service is deployed. For information about JConsole, see Chapter 15, "Managing Oracle Real-Time Decisions".

Failure setting up Smart Client's default responses from file, file_name

Check the Smart Client properties file for the location of the file and check to make sure it exists.

Error connecting to server

Check your server connectivity and that your network is working properly.

There were compiler errors: errors

Compiler errors may occur on the server if you have configured an Inline Service in a newer version of Decision Studio than the version of the Server. Upgrade your Server version to correct the problem.

Internal Error.

Contact Oracle Support Services.

No default choice is defined for Inline Service Inline_Service_name, or its Integration Point Integration_Point_name.

Default choices are choices used by the calling application when the server is unavailable. Default choices are defined at the Integration Point level.

Could not create a backup of {0} in {1}

If the backup location is on your network, check the network connectivity. If the backup location is local, check that you have enough disk space for the backup.

Could not find JMX Server server_name

If the JMX Server is unavailable, check the database connectivity and make sure the server is running.

Unknown Decision Service message type received by HTTP endpoint: endpoint_name

Refer to Part II, Integration with Oracle RTD, in Oracle RTD Platform Developer's Guide for examples and specifications for HTTP queries.

Malformed SOAP query

Refer to Part II, Integration with Oracle RTD, in Oracle RTD Platform Developer's Guide for examples and specifications for SOAP queries.

Session merging not implemented, but found two keys in same request referencing different sessions

Session merging is not yet implemented. In your Inline Service, use only one session key.

Input column at location table_or_stored_procedure and name column_name has a null value which is not supported in where clauses

The Input column of a where clause cannot be null. Go to the data source indicated and provide a value for the column.

The current server server has a newer version of the metadata so Inline_Service cannot be loaded

This error can occur if you are using a newer version of Decision Studio with an older version of Real-Time Decision Server. Upgrade your server to correct the error.

The current server server_name supports metadata versions up to version_number, but the metadata of Inline_Server is at version version_number

This error can occur if you are using a newer version of Decision Studio with an older version of Real-Time Decision Server. Upgrade your server to correct the error.

Generation of Inline Service "Inline_Service_name" failed

This error can occur if you are using a newer version of Decision Studio with an older version of Real-Time Decision Server. Upgrade your server to correct the error.

Unable to read a study definition created by a newer version of the software.

This error can occur if you are using a newer version of Decision Studio with an older version of Real-Time Decision Server. Upgrade your server to correct the error.

Unable to read a prediction model created by a newer version of the software.

This error can occur if you are using a newer version of Decision Studio with an older version of Real-Time Decision Server. Upgrade your server to correct the error.

Encountered a database record created by a newer version of the software.

This error can occur if you are using a newer version of Decision Studio with an older version of Real-Time Decision Server. Upgrade your server to correct the error.

Unable to read a learning model created by a newer version of the software.

This error can occur if you are using a newer version of Decision Studio with an older version of Real-Time Decision Server. Upgrade your server to correct the error.

No result set found while getting result set of procedure "stored_procedure_name".

This error can occur if you have defined a result set for your data source, but there is none on the stored procedure. Check the stored procedure definition in the database.

Generic Exception caught while setting blob for procedure "stored_procedure_name".

This error can occur for several reasons. Check your database connectivity. Check that the database server is running.

Exception during output of batched statements: database insert/update/select/delete operation for table_or_stored_procedure took duration. Batch size is number_of_results.

This error can occur for several reasons. Check your database connectivity. Check that the database server is running.

The stored procedure "stored_procedure_name" was not found in database.

This error can occur for several reasons. Check your database connectivity. Check that the database server is running. Finally, check that the stored procedure named in the data source is named correctly and resident on the database.

Failed to find column "column_name" in table "table_name".

This error can occur for several reasons. Check your database connectivity. Check that the database server is running. Finally, check that the table named in the data source is named correctly and resident on the database.

Error setting up Smart Client properties.

This error can occur if you have not properly configured your Smart Client properties file. Refer to Part II, Integration with Oracle RTD, in Oracle RTD Platform Developer's Guide for information on using the Smart Client.

Failed to load Inline Service: Inline_Service_name

This error can occur on start-up of Real-Time Decision Server. Redeploy the Inline Services that did not start up. If the error reoccurs, contact Oracle Support Services.