Explanation | An attempt was made to register a value in the repository using a null name. |
Action | Ensure all calls to store data in the repository specify non-null names. |
Explanation | An attempt was made to register an empty byte array value in the repository. |
Action | Ensure all calls to store data in the repository specify a non-empty byte array as the value. |
Explanation | An attempt was made to register a null value in the repository. |
Action | Ensure all calls to store data in the repository specify non-null values. |
Explanation | An attempt was made to register a value using a name already used in the repository. |
Action | Use a different name, or delete the existing value for the name, or specify "overwrite" when writing to the repository. |
Explanation | An optimistic update strategy is used to write to the repository when using an OutputStream. The update failed because the stored value changed. The change might have been made by another thread. |
Action | Check if the value should still be updated and, if so, repeat the command. |
Explanation | A stream can only be closed once. This was probably caused by a client programming error. |
Action | Only close the stream once. |
Explanation | Some resources in the repository are defined by the system. These resources cannot be edited. |
Action | Choose a different name for user-defined resources. |
Explanation | The domain has not been registered to the system. |
Action | Ensure the domain name is correct and that a data access service factory has been registered for the domain. |
Explanation | An attempt was made to register a data access service factory using a null domain name. |
Action | Ensure all calls to register data access service factories specify non-null domain names. |
Explanation | An SDO repository instance cannot be created because the sib.sdoConfig.jar file is missing or corrupted. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A data access service registry instance cannot be created because the sib.sdoConfig.jar file is missing or corrupted. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | To install the SDO repository, the installation program needs access to this JDBC provider. |
Action | Restore the named JDBC provider or manually install the SDO repository. |
Explanation | The installer cannot continue because the data source it will create already exists. |
Action | If the SDO repository is already installed, do not install it again. Otherwise manually install the SDO repository to avoid naming conflicts with the existing configuration. |
Explanation | The installer cannot continue because the connection factory it will create already exists. |
Action | If the SDO repository is already installed, do not install it again. Otherwise manually install the SDO repository to avoid naming conflicts with the existing configuration. |
Explanation | The script is declaring the server and node being used. |
Action | No action is required. |
Explanation | There is more than one server configured for the node, and the command does not know which server to use. |
Action | Run the script specifying the names of a node and server. |
Explanation | The installer is creating a JDBC provider. |
Action | No action is required. |
Explanation | The installer is creating the data source configuration object. |
Action | No action is required. |
Explanation | The installer is creating a connection factory for the previously created data source. |
Action | No action is required. |
Explanation | The installer is installing the application component of the SDO repository. |
Action | No action is required. |
Explanation | The configuration changes are being saved. |
Action | No action is required. |
Explanation | The installation has completed. |
Action | No action is required. |
Explanation | The script was called with an incorrect set of parameters. |
Action | Call the script again using the parameters as described in the message. |
Explanation | The uninstaller has removed the data source used by the SDO repository. |
Action | No action is required. |
Explanation | The data source created by the installer was not found. |
Action | Locate the repository's data source and manually remove it. |
Explanation | The uninstaller has removed the connection factory used by the repository's data source. |
Action | No action is required. |
Explanation | The CMP connection factory created by the installer was not found. |
Action | Locate the repository's CMP connection factory and manually remove it. |
Explanation | The uninstaller is uninstalling the application component of the SDO repository. |
Action | No action is required. |
Explanation | The uninstaller has completed. |
Action | No action is required. |
Explanation | The resource has been saved to disk. |
Action | No action is required. |
Explanation | The resource cannot be exported to the file. See the message for details. |
Action | Respond appropriately to the error message. |
Explanation | The resource has been loaded from disk. |
Action | No action is required. |
Explanation | The resource cannot be imported from the file. See the message for details. |
Action | Respond appropriately to the error message. |
Explanation | The resource has been removed from the repository. |
Action | No action is required. |
Explanation | The resource cannot be removed. See the message for details. |
Action | Respond appropriately to the error message. |
Explanation | There was an error while listing the resources. See the message for details. |
Action | Respond appropriately to the error message. |
Explanation | A resource with the given name is not stored in the repository. |
Action | Use the correct name for the item for which you are searching, or add the item to the repository under this name. |
Explanation | There is more than one node configured for the cell. |
Action | Run the script specifying the names of a node and server. |
Explanation | The install script cannot find the ij.bat or ij.sh command in the named directory. If this file does not exist the server installation is corrupted. |
Action | Reinstall the application server to repair the installation. |
Explanation | The installer is creating the DDL file for the Derby database. |
Action | No action is required. |
Explanation | The installer is creating a Derby database using the DDL file. The results of the database creation are saved to a log file. |
Action | No action is required. |
Explanation | The installer cannot create a database in the named directory because the directory already exists. |
Action | Delete the directory if it safe to do so, then run the installer again. |
Explanation | The script is declaring the server and node being used. |
Action | No action is required. |
Explanation | An attempt was made to register a resource with a name that is longer than the underlying database allows. |
Action | Use a shorter name when registering the resource. |
Explanation | An attempt was made to register a resource that is longer than the underlying database will permit. |
Action | Break the resource into smaller pieces to store in the repository. |
Explanation | The specified cluster does not exist. |
Action | Call the install script again with a valid cluster name. |
Explanation | The script is declaring the cluster being used. |
Action | No action is required. |
Explanation | The specified server does not exist. |
Action | Call the script again with valid node and server names. |
Explanation | The installation program endeds because the SDO repository application is already installed on the server. |
Action | No action is required. The application is already installed. |
Explanation | The script is declaring the detected backend ID. This identifies the type of database the SDO repository will be configured to use. |
Action | No action is required. |
Explanation | The script is declaring the cluster being used. |
Action | No action is required. |
Explanation | The JNDI lookup for the SDO repository has failed. |
Action | Install the SDO repository on the server being used, and ensure the repository has started. |
Explanation | The SDO repository requires a data source and database to be configured for use. |
Action | See the information center for details on configuring a data source for the SDO repository. |
Explanation | The install script is displaying a list of valid parameters. |
Action | No action is required. |
Explanation | The install script is displaying a list of valid parameters. |
Action | No action is required. |
Explanation | The script is declaring that it is updating the backend ID of the SDO repository application. |
Action | No action is required. |
Explanation | The "-createDb" option creates an embedded Derby database. Embedded Derby can only be used by the SDO repository on a stand-alone server. |
Action | See the information center for instructions on how to install the SDO repository in a Network Deployment environment. |
Explanation | The "-createDb" option creates an embedded Derby database. This database cannot be used on a z/OS system because embedded Derby can only be accessed by one process at a time, and Application Servers on z/OS contain multiple processes. |
Action | See the information center for instructions on how to install the SDO repository on z/OS. |
Explanation | If the message does not give sufficient information, check previous messages for further help. |
Action | See previous messages for further information. |