Known Issues for ECDA Option for ODBC

If you add ECDA service information to a local sql.ini file, you see this message during start-up:

CT-LIBRARY error:
ct_connect(): directory service layer: internal
directory control layer error: Requested server name not found.

You must add ECDA service information to the global sql.ini file instead of the local sql.ini file. The global sql.ini file is located in <install_dir>\ini\sql.ini. The local sql.ini file is located in <install_dir>\DC-15_0\connectivity}\ini\sql.ini.

Workaround:None.

At start-up, ECDA Option for ODBC issues a warning that the ODBCDriverManager property is not set. ECDA issues this message because it uses the default configuration property, unixODBC, and does not find a value for this property in the dcany.cfg file. Because this message does not affect operation, you can safely ignore it.

Workaround: None.

Express transfer does not support the transfer of char datatypes to and from decimal datatypes.

Workaround: Convert query datatypes from char to decimal datatypes in the transfer query statement using the SQL CAST function.

Express transfer does not support the transfer of text datatypes to and from char datatypes.

Workaround: Convert query datatypes from text to char datatypes in the transfer query statement using the SQL CAST function.

Host name as IP address causes failure on Solaris

Specifying the host name as the IP Address causes a failure on some Solaris systems.

Workaround: Specify the IP Number as the IP Address.

CLOB data is limited to 32K and the BLOB datatype is not supported.

Workaround: Use the DirectConnect for z/OS Option.

(Microsoft SQL Server) NCHAR and NVARCHAR datatype support

Microsoft NCHAR and NVARCHAR datatypes are not supported but are translated to the single-byte character set of the operating system. Unicode characters that cannot be mapped are translated to a default character for the operating system.

Workaround: None.

Adaptive Server/Component Integration Services (CIS) is not correctly mapping the timestamp datatype, resulting in insert failures.

Workaround: None.

An update of read-only cursors fails to return errors against Microsoft SQL Server 2005.

Workaround: None.