Problem | An attempt was made to register a value in the repository using a null name. |
User response | Ensure all calls to store data in the repository specify non-null names. |
Problem | An attempt was made to register an empty byte array value in the repository. |
User response | Ensure all calls to store data in the repository specify a non-empty byte array as the value. |
Problem | An attempt was made to register a null value in the repository. |
User response | Ensure all calls to store data in the repository specify non-null values. |
Problem | An attempt was made to register a value using a name already used in the repository. |
User response | Use a different name or delete the existing value for the name or specify overwrite when writing to the repository. |
Problem | 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. |
User response | Check if the value should still be updated and, if so, repeat the command. |
Problem | A stream can only be closed once. This was probably caused by a client programming error. |
User response | Only close the stream once. |
Problem | Some resources in the repository are defined by the system. These resources cannot be edited. |
User response | Choose a different name for user-defined resources. |
Problem | The domain has not been registered to the system. |
User response | Ensure the domain name is correct and that a data access service factory has been registered for it. |
Problem | An attempt was made to register a data access service factory using a null domain name. |
User response | Ensure all calls to register data access service factories specify non-null domain names. |
Problem | An SDO repository instance cannot be created because the sib.sdoConfig.jar file is missing or corrupted. |
User response | 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/. |
Problem | A data access service registry instance cannot be created because the sib.sdoConfig.jar file is missing or corrupted. |
User response | 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/. |
Problem | The installer needs this JDBC provider to exist to install the SDO repository. |
User response | Restore the named JDBC provider or manually install the SDO repository. |
Problem | The installer cannot continue because the data source it will create already exists. |
User response | 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. |
Problem | The installer cannot continue because the connection factory it will create already exists. |
User response | 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. |
Problem | The script is declaring the server and node being used. |
User response | None. |
Problem | There is more than one server configured for the node. |
User response | Run the script specifying the names of a node and server. |
Problem | The installer is creating a JDBC provider. |
User response | None. |
Problem | The installer is creating the data source configuration object. |
User response | None. |
Problem | The installer is creating a connection factory for the previously created data source. |
User response | None. |
Problem | The installer is installing the application component of the SDO repository. |
User response | None. |
Problem | The configuration changes are being saved. |
User response | None. |
Problem | The installation has completed. |
User response | None. |
Problem | The script was called with an incorrect set of parameters. |
User response | Call the script again with the parameters described in the message. |
Problem | The uninstaller has removed the data source used by the SDO repository. |
User response | None. |
Problem | The data source created by the installer was not found. |
User response | Locate the repository's data source and manually remove it. |
Problem | The uninstaller has removed the connection factory used by the repository's data source. |
User response | None. |
Problem | The CMP connection factory created by the installer was not found. |
User response | Locate the repository's CMP connection factory and manually remove it. |
Problem | The uninstaller is uninstalling the application component of the SDO repository. |
User response | None. |
Problem | The uninstaller has completed. |
User response | None. |
Problem | The resource has been saved to disk. |
User response | None. |
Problem | The resource cannot be exported the to the file. See the message for details. |
User response | Respond appropriately to the error message. |
Problem | The resource has been loaded from disk. |
User response | None. |
Problem | The resource cannot be imported the from the file. See the message for details. |
User response | Respond appropriately to the error message. |
Problem | The resource has been removed from the repository. |
User response | None. |
Problem | The resource cannot be removed. See the message for details. |
User response | Respond appropriately to the error message. |
Problem | There was an error while listing the resources. See the message for details. |
User response | Respond appropriately to the error message. |
Problem | A resource with the given name is not stored in the repository. |
User response | Use the correct name for the item being searched for or add it to the repository under this name. |
Problem | There is more than one node configured for the cell. |
User response | Run the script specifying the names of a node and server. |
Problem | 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. |
User response | Reinstall the application server to repair the installation. |
Problem | The installer is creating the DDL file for the Derby database. |
User response | None. |
Problem | The installer is creating a Derby database using the DDL file. The results of the database creation are saved to a log file. |
User response | None. |
Problem | The installer cannot create a database in the named directory because the directory already exists. |
User response | Delete the directory if it safe to do so, and run the installer again. |
Problem | The script is declaring the server and node being used. |
User response | None. |
Problem | An attempt was made to register a resource with a name that is longer than the underlying database will permit. |
User response | Use a shorter name when registering the resource. |
Problem | An attempt was made to register a resource with that is longer than the underlying database will permit. |
User response | Break the resource into smaller pieces to store in the repository. |
Problem | The cluster specified by the user does not exist. |
User response | Call the install script again with a valid cluster name. |
Problem | The script is declaring the cluster being used. |
User response | None. |
Problem | The server specified by the user does not exist. |
User response | Call the script again with a valid node and server names. |
Problem | The installer will end because the SDO Repository application is already installed on the server. |
User response | No action required. The application is already installed. |
Problem | The installer attempts to detect the type of database used by the repository during installation. This attempt has failed. |
User response | Ensure both the database server and target application server are running. Alternatively, manually set the BackendId using the install script. |
Problem | The script is declaring the detected backend ID. This identifies the type of database the SDO Repository will be configured to use. |
User response | None. |
Problem | The script is declaring the cluster being used. |
User response | None. |
Problem | The JNDI lookup for the SDO Repository failed. |
User response | Install the SDO Repository on the server being used, and ensure the repository has started. |
Problem | The SDO Repository is already installed because it is a permanent feature of the deployment manager. |
User response | None. |
Problem | The SDO Repository is a permanent feature of the deployment manager and cannot be uninstalled. |
User response | None. |
Problem | The SDO Repository requires a data source and database to be configured for use. |
User response | See the documentation for details on configuring a data source for the SDO Repository. |
Problem | The SDO Repository can be configured for different types of database. The the current database does not match the repository's configuration. |
User response | Edit the repository's configuration by using the installSdoRepository.jacl script specifying the -editBackendId option. |
Problem | The install script is displaying a list valid parameters |
User response | None. |
Problem | 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. |
User response | 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. |
Problem | The script is declaring that it is updating the backend ID of the SDO Repository application. |
User response | None. |
Problem | The "-createDb" option creates an embedded Derby database. Embedded Derby can only be used by the SDO Repository on a standalone server. |
User response | See the InfoCenter for instructions on how to install the SDO Repository in a Network Deployment environment. |
Problem | 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. |
User response | See the InfoCenter for instructions on how to install the SDO Repository on z/OS. |
Problem | If the message does not give sufficient information, check previous messages for further help. |
User response | See previous messages for further information. |