The 32-bit ODBC Adapter in Object Service Broker v6.0.0 fails to access Unicode data.
Article ID: KB0092435
Updated On:
| Products | Versions |
|---|---|
| TIBCO Object Service Broker Adapter for JDBC-ODBC | - |
| TIBCO Object Service Broker for z/OS | - |
| Not Applicable | - |
Description
Description:
Attempting to use the 32-bit ODBC Adapter in Object Service Broker v6.0.0 to access Unicode data fails with the message "Unicode feature is not licensed".
Symptoms:
When trying to use the 32-bit ODBC adapter in Object Service Broler v6.0.0 to access a table containing Uicode data, the message: "Unicode feature is not licensed" will be generated.
Cause:
The 32-bit version of the ODBC adapter makes use of DataDirect's Open Access product to perform ODBC access. Version 6.0.0 of TIBCO OBject Service Broker for Open Systems was shipped with an incorrect version of the initialization file, ISLV.INI which determines the set of features licensed for Open Acces.
Attempting to use the 32-bit ODBC Adapter in Object Service Broker v6.0.0 to access Unicode data fails with the message "Unicode feature is not licensed".
Symptoms:
When trying to use the 32-bit ODBC adapter in Object Service Broler v6.0.0 to access a table containing Uicode data, the message: "Unicode feature is not licensed" will be generated.
Cause:
The 32-bit version of the ODBC adapter makes use of DataDirect's Open Access product to perform ODBC access. Version 6.0.0 of TIBCO OBject Service Broker for Open Systems was shipped with an incorrect version of the initialization file, ISLV.INI which determines the set of features licensed for Open Acces.
Issue/Introduction
The 32-bit ODBC Adapter in Object Service Broker v6.0.0 fails to access Unicode data.
Resolution
Raise a service request with Customer Support. We will provide the correct version of the ISLV.INI initialization/license file.
Feedback
Yes
No
Powered by
