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 may 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 it. |
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The installer needs this JDBC provider to exist to install the SDO repository. |
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 | None. |
Explanation | There is more than one server configured for the node. |
Action | Run the script specifying the names of a node and server. |
Explanation | The installer is creating a JDBC provider. |
Action | None. |
Explanation | The installer is creating the data source configuration object. |
Action | None. |
Explanation | The installer is creating a connection factory for the previously created data source. |
Action | None. |
Explanation | The installer is installing the application component of the SDO repository. |
Action | None. |
Explanation | The configuration changes are being saved. |
Action | None. |
Explanation | The installation has completed. |
Action | None. |
Explanation | The script was called with an incorrect set of parameters. |
Action | Call the script again with the parameters described in the message. |
Explanation | The uninstaller has removed the data source used by the SDO repository. |
Action | None. |
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 | None. |
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 | None. |
Explanation | The uninstaller has completed. |
Action | None. |
Explanation | The resource has been saved to disk. |
Action | None. |
Explanation | The resource cannot be exported the to the file. See the message for details. |
Action | Respond appropriately to the error message. |
Explanation | The resource has been loaded from disk. |
Action | None. |
Explanation | The resource cannot be imported the 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 | None. |
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 being searched for or add it 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 | None. |
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 | None. |
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, and run the installer again. |
Explanation | The script is declaring the server and node being used. |
Action | None. |
Explanation | An attempt was made to register a resource with a name that is longer than the underlying database will permit. |
Action | Use a shorter name when registering the resource. |
Explanation | An attempt was made to register a resource with that is longer than the underlying database will permit. |
Action | Break the resource into smaller pieces to store in the repository. |
Explanation | The cluster specified by the user does not exist. |
Action | Call the install script again with a valid cluster name. |
Explanation | The script is declaring the cluster being used. |
Action | None. |
Explanation | The server specified by the user does not exist. |
Action | Call the script again with a valid node and server names. |
Explanation | The installer will end because the SDO Repository application is already installed on the server. |
Action | No action required. The application is already installed. |
Explanation | The installer attempts to detect the type of database used by the repository during installation. This attempt has failed. |
Action | Ensure both the database server and target application server are running. Alternatively, manually set the BackendId using the install script. |
Explanation | The script is declaring the detected backend ID. This identifies the type of database the SDO Repository will be configured to use. |
Action | None. |
Explanation | The script is declaring the cluster being used. |
Action | None. |
Explanation | The JNDI lookup for the SDO Repository failed. |
Action | Install the SDO Repository on the server being used, and ensure the repository has started. |
Explanation | The SDO Repository is already installed because it is a permanent feature of the deployment manager. |
Action | None. |
Explanation | The SDO Repository is a permanent feature of the deployment manager and cannot be uninstalled. |
Action | None. |
Explanation | The SDO Repository requires a data source and database to be configured for use. |
Action | See the documentation for details on configuring a data source for the SDO Repository. |
Explanation | The SDO Repository can be configured for different types of database. The the current database does not match the repository's configuration. |
Action | Edit the repository's configuration by using the installSdoRepository.jacl script specifying the -editBackendId option. |
Explanation | The install script is displaying a list valid parameters |
Action | None. |
Explanation | The installer attempts to detect the type of database used by the repository during installation. This attempt has failed. The default backend ID will be used. |
Action | Check the default backend ID is correct the current database. If not, edit the repository's configuration by using the installSdoRepository.jacl script specifying the -editBackendId option. |
Explanation | The script is declaring that it is updating the backend ID of the SDO Repository application. |
Action | None. |
Explanation | The "-createDb" option creates an embedded Derby database. Embedded Derby can only be used by the SDO Repository on a standalone server. |
Action | See the InfoCenter for instructions on how to install the SDO Repository in a Network Deployment environment. |
Explanation | The "-createDb" option creates an embedded Derby database. Embedded Derby can only be accessed by one process at a time. z/OS WebSphere servers contain multiple processes. |
Action | See the InfoCenter 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. |