. "Data Source Name Configuration Guide" . "Data Source Name Configuration of the Lite Edition (Single-Tier) ODBC Driver for JDBC Data Sources (a/k/a ODBC-to-JDBC Bridge), for macOS\r\n" . . . "Data Source Name Configuration of the Lite Edition (Single-Tier) ODBC Driver for JDBC Data Sources (a/k/a ODBC-to-JDBC Bridge), for macOS\n" . . . . . . . . "Data Source Name Configuration of the Lite Edition (Single-Tier) ODBC Driver for JDBC Data Sources (a/k/a ODBC-to-JDBC Bridge), for macOS\r\n" . . . . . . . . "Data Source Name Configuration of the Lite Edition (Single-Tier) ODBC Driver for JDBC Data Sources (a/k/a ODBC-to-JDBC Bridge), for Mac OS X\n" . . . . . . . "\r\n

\r\n
1. To configure an ODBC DSN, run the OpenLink iODBC Administrator located in the /Applications/iODBC folder:
\r\n
2. Click the System DSN tab, and then click the Add button.
\r\n
3. Select the OpenLink JDBC Lite Driver from the list of available drivers.
\r\n
4. Select the Unicode version of the driver if and only if you are working with multi-byte character sets, as unnecessary translations can significantly affect ODBC performance.
\r\n
5. Click Finish.
\r\n
6. The Data Source tab prompts a Data Source Name and optional description.\r\n
   \r\n
   • DSN: A brief and meaningful title for your Data Source Name
   \r\n
   • Description: An optional description for your Data Source Name
   \r\n
   \r\n
\r\n
7. The Connection Tab takes the minimum requirements that are necessary to connect to your JDBC data source.\r\n
   \r\n
   • JDBC Driver: The class name for your third-party JDBC driver, e.g., virtuoso.jdbc3.Driver
   \r\n
   • URL String: The JDBC connection URL for your third-party JDBC driver
   \r\n
   • Username: The username for your JDBC database
   \r\n
   \r\n
\r\n
8. The Options tab displays additional parameters that can be configured for the connection.\r\n
   \r\n
   • Row Buffer Size: The number of records to be transported over the network in a single network hop. Values can range from 1 to 99.
   \r\n
   • Hide Login Dialog: Suppresses the ODBC \"Username\" and \"Password\" login dialog boxes when interacting with your ODBC DSN from within an ODBC compliant application.
   \r\n
   • Read Only connection: Specifies whether the connection is \"Read-only.\" Make sure the checkbox is unchecked to request a \"Read/Write\" connection.
   \r\n
   • Drop Catalog from Meta calls: Enable this option to have the catalog name not appear for tables, views, and procedures when requesting database meta-data.
   \r\n
   • Drop Schema from Meta calls: Enable this option to have the schema name not appear for tables, views, and procedures when requesting database meta-data.
   \r\n
   • No support of quoted identifier: If set, the call SQLGetInfo for 'SQL_IDENTIFIER_QUOTE_CHAR' will return a space (\"\" \"\"). It can be used if the DBMS doesn't support quoted SQL like SELECT * from \"\"account\"\".
   \r\n
   • SQLStatistics disabled: Check this box to have SQLStatistics() return an empty result set. Use this if the underlying database does not support retrieval of statistics about a table (e.g. what indexes it has).
   \r\n
   • No support of search string escape: If set, the call SQLGetInfo(SQL_LIKE_ESCAPE_CLAUSE) will return a space (\"\" \"\"). It can be used if the DBMS doesn't support SQL escape patterns.
   \r\n
   • Patch of NULL size of SQL_CHAR: If set, this option overrides the size of SQL_CHAR column type returned by the database withthe value set in the text box (in bytes). With a default value of 0, the driver uses the size returned by the database.
   \r\n
   • SQL_DBMS Name: Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is required for products like Microsoft InfoPath (for which the value should be \"SQL Server\").
   \r\n
   \r\n
\r\n
9. Click Continue to view additional preferences that can be set for the connection.\r\n
   \r\n
   • Initialization SQL: Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.
   \r\n
   • Cursor Sensitivity: Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates checksums for each row in the current rowset and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the rowset. From the user's point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same. Deleted rows don't appear in the rowset. Updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset, if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the 'High Cursor Sensitivity' checkbox unchecked, as performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. If this option is enabled, the table oplrvc must have been created beforehand using the appropriate script for the target database.
   \r\n
   • Max Rows Override: Allows you to define a limit on the maximum number of rows to be returned from a query. The default value of 0 means no limit.
   \r\n
   • Show remarks: Affects output from the SQLColumns() ODBC API call. Use this option in conjunction with Oracle queries. When enabled, the REMARKS column of a SQLColumns() result set includes the comments from the COMMENTS column of the Oracle ALL_COL_COMMENTS data dictionary view. When disabled, the REMARKS column is empty. Disabling Show Remarks improves performance.
   \r\n
   • Disable autocommit: Changes the default commit behavior of the OpenLink driver. The default mode is AutoCommit (box unchecked).
   \r\n
   • Disable rowset size limit: Removes OpenLink's default 100 rowset restriction.
   \r\n
   • Defer fetching of long data: Defers fetching of LONG (BINARY, BLOB, etc.) data unless explicitly requested in a query. This provides significant performance increases when fields in the query do not include LONG data fields.
   \r\n
   • Always include VIEWS in table list:
   \r\n
   • Always include all types in table list:
   \r\n
   • Custom Catalogue Views: Dictates whether custom OpenLink views are used toreturn metadata for certain ODBC catalog functions: SQLForeignKeys(), SQLPrimaryKeys(), SQLProcedureColumns(), SQLProcedures(), and SQLSpecialColumns(). These custom views provide more metadata than is normally provided by the standard Oracle data dictionary views.
   \r\n
   • User's own tables first in SQLTables: This option is specific to OpenLink's Oracle drivers. It prompts the SQLTables() ODBC API call to display the connected user's tables first in table lists. The default ordering is alphabetical.
   \r\n
   • Count stored procedure parameters in SQL Procedures: This parameter is specific to the Oracle data source. It affects the output from SQLProcedures() when \"Custom Catalog Views\" is enabled.
   \r\n
   \r\n
\r\n
10. Click the Finish button to save your new Data Source Name.
\r\n
11. Click the Finish button to save your new Data Source Name.
\r\n

" . . "Data Source Name Configuration of the Lite Edition (Single-Tier) ODBC Driver for JDBC Data Sources (a/k/a ODBC-to-JDBC Bridge), for macOS\n" . . "Data Source Name Configuration of the Lite Edition (Single-Tier) ODBC Driver for JDBC Data Sources (a/k/a ODBC-to-JDBC Bridge), for Mac OS X\r\n" . . . "Data Source Name Configuration of the Lite Edition (Single-Tier) ODBC Driver for JDBC Data Sources (a/k/a ODBC-to-JDBC Bridge), for Mac OS X\n" . "

\n
1. To configure an ODBC DSN, run the OpenLink iODBC Administrator located in the /Applications/iODBC folder:
\n
2. Click the System DSN tab, and then click the Add button.
\n
3. Select the OpenLink JDBC Lite Driver from the list of available drivers.
\n
4. Select the Unicode version of the driver if and only if you are working with multi-byte character sets, as unnecessary translations can significantly affect ODBC performance.
\n
5. Click Finish.
\n
6. The Data Source tab prompts a Data Source Name and optional description.\n
   \n
   • DSN: A brief and meaningful title for your Data Source Name
   \n
   • Description: An optional description for your Data Source Name
   \n
   \n
\n
7. The Connection Tab takes the minimum requirements that are necessary to connect to your JDBC data source.\n
   \n
   • JDBC Driver: The class name for your third-party JDBC driver, e.g., virtuoso.jdbc3.Driver
   \n
   • URL String: The JDBC connection URL for your third-party JDBC driver
   \n
   • Username: The username for your JDBC database
   \n
   \n
\n
8. The Options tab displays additional parameters that can be configured for the connection.\n
   \n
   • Row Buffer Size: The number of records to be transported over the network in a single network hop. Values can range from 1 to 99.
   \n
   • Hide Login Dialog: Suppresses the ODBC \"Username\" and \"Password\" login dialog boxes when interacting with your ODBC DSN from within an ODBC compliant application.
   \n
   • Read Only connection: Specifies whether the connection is \"Read-only.\" Make sure the checkbox is unchecked to request a \"Read/Write\" connection.
   \n
   • Drop Catalog from Meta calls: Enable this option to have the catalog name not appear for tables, views, and procedures when requesting database meta-data.
   \n
   • Drop Schema from Meta calls: Enable this option to have the schema name not appear for tables, views, and procedures when requesting database meta-data.
   \n
   • No support of quoted identifier: If set, the call SQLGetInfo for 'SQL_IDENTIFIER_QUOTE_CHAR' will return a space (\"\" \"\"). It can be used if the DBMS doesn't support quoted SQL like SELECT * from \"\"account\"\".
   \n
   • SQLStatistics disabled: Check this box to have SQLStatistics() return an empty result set. Use this if the underlying database does not support retrieval of statistics about a table (e.g. what indexes it has).
   \n
   • No support of search string escape: If set, the call SQLGetInfo(SQL_LIKE_ESCAPE_CLAUSE) will return a space (\"\" \"\"). It can be used if the DBMS doesn't support SQL escape patterns.
   \n
   • Patch of NULL size of SQL_CHAR: If set, this option overrides the size of SQL_CHAR column type returned by the database withthe value set in the text box (in bytes). With a default value of 0, the driver uses the size returned by the database.
   \n
   • SQL_DBMS Name: Manually overrides the SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is required for products like Microsoft InfoPath (for which the value should be \"SQL Server\").
   \n
   \n
\n
9. Click Continue to view additional preferences that can be set for the connection.\n
   \n
   • Initialization SQL: Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.
   \n
   • Cursor Sensitivity: Enables or disables the row version cache used with dynamic cursors. When dynamic cursor sensitivity is set high, the Cursor Library calculates checksums for each row in the current rowset and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the rowset. From the user's point of view, the only visible difference between the two sensitivity settings is that a row status flag can never be set to SQL_ROW_UPDATED when the cursor sensitivity is low. (The row status is instead displayed as SQL_ROW_SUCCESS.) In all other respects, performance aside, the two settings are the same. Deleted rows don't appear in the rowset. Updates to the row since the row was last fetched are reflected in the row data, and inserted rows appear in the rowset, if their keys fall within the span of the rowset. If your application does not need to detect the row status SQL_ROW_UPDATED, you should leave the 'High Cursor Sensitivity' checkbox unchecked, as performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. If this option is enabled, the table oplrvc must have been created beforehand using the appropriate script for the target database.
   \n
   • Max Rows Override: Allows you to define a limit on the maximum number of rows to be returned from a query. The default value of 0 means no limit.
   \n
   • Show remarks: Affects output from the SQLColumns() ODBC API call. Use this option in conjunction with Oracle queries. When enabled, the REMARKS column of a SQLColumns() result set includes the comments from the COMMENTS column of the Oracle ALL_COL_COMMENTS data dictionary view. When disabled, the REMARKS column is empty. Disabling Show Remarks improves performance.
   \n
   • Disable autocommit: Changes the default commit behavior of the OpenLink driver. The default mode is AutoCommit (box unchecked).
   \n
   • Disable rowset size limit: Removes OpenLink's default 100 rowset restriction.
   \n
   • Defer fetching of long data: Defers fetching of LONG (BINARY, BLOB, etc.) data unless explicitly requested in a query. This provides significant performance increases when fields in the query do not include LONG data fields.
   \n
   • Always include VIEWS in table list:
   \n
   • Always include all types in table list:
   \n
   • Custom Catalogue Views: Dictates whether custom OpenLink views are used toreturn metadata for certain ODBC catalog functions: SQLForeignKeys(), SQLPrimaryKeys(), SQLProcedureColumns(), SQLProcedures(), and SQLSpecialColumns(). These custom views provide more metadata than is normally provided by the standard Oracle data dictionary views.
   \n
   • User's own tables first in SQLTables: This option is specific to OpenLink's Oracle drivers. It prompts the SQLTables() ODBC API call to display the connected user's tables first in table lists. The default ordering is alphabetical.
   \n
   • Count stored procedure parameters in SQL Procedures: This parameter is specific to the Oracle data source. It affects the output from SQLProcedures() when \"Custom Catalog Views\" is enabled.
   \n
   \n
\n
10. Click the Finish button to save your new Data Source Name.
\n
11. Click the Finish button to save your new Data Source Name.
\n

" . . . "Data Source Name Configuration of the Lite Edition (Single-Tier) ODBC Driver for JDBC Data Sources (a/k/a ODBC-to-JDBC Bridge), for Mac OS X\r\n" .