Troubleshooting Database Access
Error | Possible Reason | Solution |
---|---|---|
The button to Apply the xUML service preferences is not enabled. | The user that has logged into the Bridge has no administration rights. | Login with another user that has administration rights (for instance the pre-defined user admin). |
The button to Apply the deployment settings of an xUML service is not enabled (tab Settings of the xUML service). | The user that has logged into the Bridge does not belong to a group with role ADMIN or MODELER. | Login with another user that has sufficient access rights (for instance the pre-defined user admin). |
The xUML service is still running. | Stop the xUML service. | |
An xUML service using the SQL adapter cannot be started. | User and password have not been defined in the deployment settings. | Enter the database user and password on tab Settings of the xUML service. |
Running a test case with a database example in the xUML Debugger reports an error. | DB2 | Either the DBMS client libraries have not been installed, or the path of the library file cannot be found. |
If the DBMS client has been installed, make sure the preferences are set correctly in the Bridge (tab Preferences of xUML Services). | ||
Oracle Linux: Error message: “... Library `libaio.so.1` loading fails..." | Either the DBMS client libraries have not been installed, or the path of the library file cannot be found. | |
If the DBMS client has been installed, make sure the preferences are set correctly in E2E Bridge (tab Preferences of xUML Services). | ||
MySQL Linux: Error message: “Can not connect. libmysqlclient.so: cannot open shared object file: No such file or directory. | Either the DBMS client libraries have not been installed, or the path of the Check the DBMS client installation. | |
If the DBMS client has been installed, make sure the preferences are set correctly in the Bridge (tab Preferences of xUML Services). | ||
Cannot connect to database via ODBC. Error:
| The problem may be caused by missing entries in the PATH environment variable. The variable might have been set by the driver installer and will be propagated to all newly-started applications (thus the third-party tools will be able to connect), but not to the windows services (regardless if they are restarted). Since Bridge services inherit the environment of the Console windows service, they also end up with missing entries. | Reboot after driver installation. |