Considerations When Working with the Connector for ODBC - General

The following information is helpful when using the Connector for ODBC.

• When using an Archive activity, you cannot use an HCL Enterprise Integrator (HEI) ODBC connection document if you are accessing a SQL Server 7 database. To access the SQL Server 7 database, use an LEI OLE DB connection document instead.
• In order to use a Direct Transfer activity to create metadata that contains more than one column of type LONG VARCHAR (ODBC type that maps to Oracle's LONG) you must use the Oracle 7 Connector directly, instead of through ODBC. Oracle does not support more than one column of type LONG in a table or in an SQL statement.
• The Connector for ODBC does not support the Microsoft ODBC drivers. It does support the HCL-branded DataDirect ODBC driver and the native ODBC drivers supplied with your external system software, such as DB2 and Oracle.
• The Oracle ODBC interface does not allow access to user SYSTEM resources. If you require access to user SYSTEM tables, views or procedures, use the native Connector for Oracle.
• If you are using the Key Table option in a Virtual Documents activity, and connecting to ODBC using the DataDirect drivers, you need a full version of the DataDirect drivers. Because the Key Table option requires two connections, a single-user license of DataDirect drivers will not be enough.
• There is a limitation on how Connectors interpret a Notes NUMBER field. When you use the "Create Target Metadata" option from a Notes source, heavy precision loss may occur with Notes NUMBER fields.