A Development Error Messages

This appendix shows the error messages that may occur during development.

Note:

For more general error messages, refer to Appendix B, "Exceptions" in Oracle Real-Time Decisions Installation and Administration Guide.

Table A-1 Development Error Messages

Error	Explanation
Internal error in code generator. See error log for details.	Check the Problems pane in Decision Studio for errors. If none are apparent, contact Oracle Support Services.
Cannot get Inline_Service from the database. Will mark it invalid	Check to make sure that the database server is running, that you have the proper drivers, and that you have connectivity to the database server.
Error loading Inline Service Inline_Service_Name. Will mark it as invalid in the database.	If you get an error from the server on loading your Inline Service, check to see if the logic in your Application Initialization logic and Session Initialization logic is correct.
Response for an asynchronous request to Advisor "Advisor_name" will not be sent	If you want a response from an Advisor, you must use the invoke() method, not invokeAsync().
Invoke failed	Make sure that you have connectivity to Real-Time Decision Server. Check that your properties file is properly configured.
Internal error	Contact Oracle Support Services.
Internal error while generating code for Inline_Service.	Contact Oracle Support Services.
Error in Application Session Cleanup.	This error can be caused by incorrect logic in the Application and Session elements. Check to see if the logic in your Application Cleanup logic and Session Cleanup logic is correct.
Failed to load study "study_name"	This error can be caused by database connection issues. Check to make sure that the database server is running, that you have the proper drivers, and that you have connectivity to the database server.
Failed to save study "study_name".	This error can be caused by database connection issues. Check to make sure that the database server is running, that you have the proper drivers, and that you have connectivity to the database server.
Failed to load prediction model "model_name"	This error can be caused by database connection issues. Check to make sure that the database server is running, that you have the proper drivers, and that you have connectivity to the database server.
Error delivering response message: error_details	Your invoke() on the Integration Point may have timed out. Check the timeout setting in the properties file.
Product sdstudio could not be found.	This error message is informational and can be ignored.