The Data Access layer allows BI platform to connect to Sybase SQL Anywhere 16 through ODBC on all supported platforms. After BOE client or server installation, you need to update the host and port number details. This is shipped for both the server and client. Warning: There is a known bug with the SQL Anywhere 16 Deployment Wizard where the system PATH and associated registry entries are not set correctly upon installation.See KBA 1986791 to resolve the issue or to use a work-around for current SQL Anywhere 16 versions.
The SQL Anywhere 16 - Oracle ODBC driver is custom-tailored for use with iAnywhere software. This driver does not work with third-party software.
If you use Oracle with MobiLink or remote data access, you must install an Oracle client on the same computer as this Oracle driver.
The Oracle driver can be configured using the ODBC Administrator, the .odbc.ini file (in Unix), or the dbdsn utility.
The following table provides the configuration options for the Oracle driver.
Sybase Sql Anywhere Client
Sybase Sql Anywhere 16
| Windows ODBC Data Source Administrator | Configuration for dbdsn command line or .odbc.ini file | Description |
|---|---|---|
| Data source name | For dbdsn, use the -w option. | A name to identify your data source. |
| User ID | UserID In dbdsn, set this option in the connection string. | The default logon ID that the application uses to connect to your Oracle database. If you leave this field blank, you are prompted for the information when you connect. |
| Password | Password In dbdsn, set this option in the connection string. | The password that the application uses to connect to your Oracle database. If you leave this field blank, you are prompted for the information when you connect. |
| TNS service name | ServiceName | The TNS Service Name that is stored in network/admin/tnsnames.ora under your Oracle installation directory. |
| Encrypt Password | For dbdsn, use the -pe option. Not supported for .odbc.ini. | Select this checkbox if you want the password to be stored in encrypted form in the data source. |
| Procedure returns results or uses VARRAY parameters | ProcResults In dbdsn, set this option in the connection string. ProcOwner In dbdsn, set this option in the connection string. | Select this field if your stored procedures can return results or if the stored procedures use Oracle VARRAYs. The default is that this option is not selected. If your download_cursor or download_delete_cursor scripts are stored procedure invocations, select this checkbox. If no stored procedures use VARRAYs and none of them returns a result set, clear this checkbox to improve performance. |
| Array Size | ArraySize In dbdsn, set this option in the connection string. | The size, in bytes, of the byte array used to prefetch rows, on a per-statement basis. The default is 60000. Increasing this value can significantly improve fetch performance (such as during MobiLink server downloads) at the cost of extra memory allocation. |
| Enable Microsoft distributed transactions | For dbdsn, use the enableMSDIC option in the connection string. Not supported for .odbc.ini. | Select this checkbox to enlist your transactions in the Microsoft Distributed Transaction Coordinator. When selected, the Oracle ODBC driver requires an Oracle binary file, oramts10.dll for Oracle Database 10g clients or oramts11.dll for Oracle Database 11g clients. |