Troubleshooting the SQL Adapter
Error | Database | Possible Reason | Solution |
---|---|---|---|
Read of BLOB fails with error " | DB2 with ODBC | The xUML Runtime cannot convert the database type to the xUML base type. | Add the setting |
Query results have wrong encoding. | MySQL | Old versions of MySQL may not respect the codepage setting (e.g. UTF-8). |
|
Error in bridgeserver log: | MySQL | MySQL cannot work on data ( | Increase |
CLOB is being cut off after 32767 chars when accessing it with the E2E Bridge. | Oracle | The xUML Runtime cannot convert the database type CLOB to the xUML base type. |
|
Error when using Oracle and trying to access a CLOB parameter returned by a stored procedure, e.g. " | Oracle | ||
Error in bridgeserverlog when requesting database:
| Oracle | Faulty connection string: use of backslash instead of forward slash. | Check the Oracle connection string. |
Performance problems: some SQL requests with a | Oracle | An existing index that corresponds to the | This may be a character encoding issue. Please find a more detailed explanation on Oracle: Performance Problems Due to Index Not Used. |
When trying to call a stored procedure, you get an error like " | Oracle | Database access encoding problem. | Try accessing the database in Unicode/non-Unicode mode (see SQL Adapter Reference). |
Encoding problems with special characters, e.g. the German umlauts, using Oracle on a Unix operating system. | Oracle on Unix | Different encoding on database client and database server is used. | Set NLS_LANG for your Bridge installation on Unix, see Installing and Configuring Database Access for Oracle in our installation guide. |
Error when trying to insert a record containing a datetime field, e.g. " | SQL Server | SQL Server datetime only supports zero to three digits, ranging from 0 to 999, that represent the fractional seconds. | Truncate the microseconds to three digits. |
Error while fetching results: After a commit in a bulk fetch loop the cursor disappears, error | SQL Server | The default setting in MS SQL is "Set cursor close on commit on". | Create one database session for the bulk fetch and a second database session for the other SQL calls including the commit. Create two aliases, one for each database session. |
The SQL handler throws the following error upon executing a database insert:
| SQL Server | A | Define the related fields to be of type CLOB (instead of String) in your service model. |
SQL rollback does not work. Error message is something like | SQL Server | Improper database settings and rollback statement. | Change the following in your database setup:
Add the following to your rollback statement:
|
Error when using SQL Adapter with SQLite: " | SQLite | This occurs, if multiple threads or processes want to read/write the SQLite database simultaneously. | There are two possible approaches to solve this conflict (they may also be combined, see Database Server-Specific Notes for SQL Adapters):
|