Explanation | Could not find the server specified on the ddlGen command. You can find expected location of the directory for the server configuration in the message. |
Action | Ensure that you can find the server configuration in the directory provided by the message. If necessary, modify the WLP_USER_DIR or WLP_INSTALL_DIR variables so that the correct path is used to find the server configuration files. |
Explanation | The server specified on the ddlGen command is not configured to accept local JMX requests. |
Action | Ensure that the server configuration includes the localConnector feature, and that the server is started. The URL required to establish a local JMX connection to this server is located in the WLP_USER_DIR/logs/state/com.ibm.ws.jmx.local.address file. |
Explanation | The server specified on the ddlGen command is not configured to accept local JMX requests. The file containing the URL used to create a JMX connection to the server is empty. |
Action | Ensure that the server configuration includes the localConnector feature, and that the server is started. The URL required to establish a local JMX connection to this server is located in the WLP_USER_DIR/logs/state/com.ibm.ws.jmx.local.address file. |
Explanation | The MBean that generates DDL was invoked, but no results were returned. The requested DDL might not have been generated. |
Action | Check the server logs and FFDC directory for a possible error message or exception. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The MBean that generates DDL was invoked, but an error was reported while generating DDL. The requested DDL might not have been generated. |
Action | Check the server logs and FFDC directory for an error message or exception. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The MBean that generates DDL was invoked, but no response code was returned in the result. The requested DDL might not have been generated. |
Action | Check the server logs and FFDC directory for a possible error message or exception. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The MBean which generates DDL was invoked, but the output directory used to write the DDL was not provided in the response. The requested DDL might not have been generated. |
Action | Check the target server output directory for the generated DDL. The output directory is specified in the server process by setting the WLP_OUTPUT_DIR variable. The DDL is generated into a ddl directory in the output directory. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The requested DDL was generated and is located in the directory indicated in the message. |
Action | No user action is required. |
Explanation | A JMX connection was established with the target server, but the DDL generation MBean was not found. This action could be expected if no features in the server configuration require access to a database. |
Action | Verify that a feature which requires DDL generation is configured in the target server. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | An unexpected exception was thrown by the DDL generation utility. The exception stack trace is printed to the stderr log file. The utility will stop processing. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The DDL generation utility completed successfully, but no features that require DDL are present in the server configuration. It is possible that part of the server configuration is missing or contains a syntactic error. |
Action | Verify that a feature that requires DDL generation is configured in the target server. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The logs directory must be available for the command to be able to locate the server's JMX connection information. This error may occur if the value of the WLP_OUTPUT_DIR variable in the current environment is not the same as the value used by the server. |
Action | Ensure that the value of the WLP_OUTPUT_DIR variable matches the value used by the server and ensure that the logs directory exists. |
Explanation | A DatabaseStore prefix can only contain numbers, letters, or the '_' symbol. |
Action | The DatabaseStore prefix must be modified to contain only numbers, letters, or the '_' symbol. |
Explanation | A DatabaseStore schema can only contain numbers, letters, or the '_' symbol. |
Action | The DatabaseStore schema must be modified to contain only numbers, letters, or the '_' symbol. |
Explanation | An attempt was made to operate on a DatabaseStore that has been deactivated. |
Action | No user action required. |
Explanation | The DatabaseStore was either automatically or manually configured to reject Unicode characters in PreparedStatement String arguments, and such a character has been found in a PreparedStatement String parameter. |
Action | Remove the Unicode character from the String parameter before trying again. |
Explanation | The DatabaseStore has logged this warning message. |
Action | Consult the DatabaseStore documentation. |
Explanation | The DatabaseStore has logged this error message. |
Action | Consult the DatabaseStore documentation. |
Explanation | To create a Cloundant client, you must specify either the url of a database or an account in the configuration. |
Action | Add a url or account attribute to the server configuration. |
Explanation | Modifiable resources such as CloudantBuilder must be looked up via a resource reference so that a new instance is returned for each lookup. If lookup without a resource reference were permitted, it would result in a shared ClientBuilder instance that would cause unpredictable behavior when applications look it up multiple times and modify it in different ways. |
Action | Include a resource reference in your application for the ClientBuilder and use the resource reference to look up the Cloudant ClientBuilder. Alternately, use resource injection (which implicitly creates a resource reference) to inject a ClientBuilder instance into your application. |
Explanation | The cloudant configuration element must either be configured with a libraryRef pointing at the Cloudant libraries, or the Cloudant libraries must be included in the application, in which case the Cloudant JNDI resource must be looked up from an application thread. |
Action | Add a libraryRef to the cloudant configuration element or update the application code to only look up the Cloudant JNDI resource from application threads. |