The Advanced tab allows you to specify additional data source settings. The fields are optional unless otherwise noted. On this tab, provide values for the options in the following table; then, click Apply.

Figure 1. Advanced tab

The Advanced Tab of the ODBC Oracle Service Cloud Driver Setup dialog box

Connection Options: Advanced Description
User Name The default user ID that is used to connect to your Oracle Service Cloud interface. Your ODBC application may override this value or you may override it in the logon dialog box or connection string. A user name is required.

Default: None
Create Database Determines whether the driver creates a new embedded database when establishing the connection.

If set to 0 - No, the driver uses the current embedded database specified by DatabaseName. If one does not exist, the connection fails.

If set to 1 - ForceNew, the driver deletes the current embedded database specified by Database and creates a new one at the same location.

Warning: This causes all views, data caches, and map customizations defined in the current database to be lost.

If set to 2 - NotExist, the driver uses the current embedded database specified by DatabaseName. If one does not exist, the driver creates one.

Default: 2 -NotExist
Transaction Mode Specifies how the driver handles manual transactions.

If set to 1 - Ignore, the data source does not support transactions and the driver always operates in auto-commit mode. Calls to set the driver to manual commit mode and to commit transactions are ignored. Calls to rollback a transaction cause the driver to return an error indicating that no transaction is started. Metadata indicates that the driver supports transactions and the ReadUncommitted transaction isolation level.

If set to 0 - No Transactions, the data source and the driver do not support transactions. Metadata indicates that the driver does not support transactions.

Default: 0 - No Transactions
Oracle Service Cloud Database Controls how the driver instructs the Oracle Service Cloud Web service to resolve queries. Oracle Service Cloud can satisfy queries against the production or the reporting database that backs the service. This property instructs the driver to indicate against which database the queries should be resolved.

If set to 0 - none, the driver sends the base ROQL command directly. This results in the default database behavior.

If set to 1 - report, the driver prepends a "USE REPORT; " statement to the base ROQL command. This results in the reporting database being used for subsequent queries.

If set to 2 - operational, the driver prepends a "USE OPERATIONAL; " statement to the base ROQL command. This results in the production database being used for subsequent queries.

Default: 1 - report
Application Using Threads Determines whether the driver works with applications using multiple ODBC threads.

If enabled, the driver works with single-threaded and multi-threaded applications.

If set to disabled, the driver does not work with multi-threaded applications. If using the driver with single-threaded applications, this value avoids additional processing required for ODBC thread-safety standards.

Default: Enabled
Enable Paging With Order By ID Specifies whether the driver can inject the Order By clause in the Select query for each ODBC call. When enabled, this option provides a stable paging mechanism for retrieving result sets larger than 10,000 rows.

Default: Enabled
Refresh Dirty Cache Specifies whether the driver refreshes a dirty cache on the next fetch operation from the cache. A cache is marked as dirty when a row is inserted into or deleted from a cached table or a row in the cached table is updated.

If enabled, a dirty cache is refreshed when the cache is referenced in a fetch operation. The cache state is set to initialized if the refresh succeeds.

If disabled, a dirty cache is not refreshed when the cache is referenced in a fetch operation.

Default: Enabled
Login Timeout The number of seconds the driver waits for a connection to be established before returning control to the application and generating a timeout error.

If set to 0, inactive connections are kept open.

If set to x (number of seconds), inactive connections are closed after the specified number of seconds passes.

Default: 15
Fetch Size Specifies the number of rows that the driver processes before returning data to the application.

If set to 0, the driver fetches and processes all of the rows of the result before returning control to the application.

If set to x (number of rows), the driver fetches and processes the specified number of rows before returning data to the application.

Default: 100
Varchar Threshold Specifies the threshold at which the driver describes columns of the data type VARCHAR as LONGVARCHAR. If the size of the VARCHAR column exceeds the value specified, the driver will describe the column as LONGVARCHAR when calling SQLDescribeCol and SQLColumns. This option allows you to fetch columns that would otherwise exceed the upper limit of the VARCHAR type for some third-party applications, such as SQL Server Linked Server.

Default: None. If no value is specified, the driver will not change the described type for VARCHAR columns.
Min Long Varchar Size Specifies the minimum count of characters the driver reports for columns mapped as SQL_LONGVARCHAR. If the size of a SQL_LONGVARCHAR column is less than the value specified, the driver will increase the reported size of the column to this value when calling SQLDescribeCol and SQLColumns. This allows you to fetch SQL_LONGVARCHAR columns whose size is smaller than the minimum imposed by some third-party applications, such as SQL Server Linked Server.

Default: None. If no value is specified, the driver will not change the column size reported for SQL_LONGVARCHAR columns.

Report Codepage Conversion Errors Specifies how the driver handles code page conversion errors that occur when a character cannot be converted from one character set to another.

If set to 0 - Ignore Errors, the driver substitutes 0x1A for each character that cannot be converted and does not return a warning or error.

If set to 1 - Return Error, the driver returns an error instead of substituting 0x1A for unconverted characters.

If set to 2 - Return Warning, the driver substitutes 0x1A for each character that cannot be converted and returns a warning.

Default: 0 - Ignore Errors
Log Config File Specifies the filename of the configuration file used to initialize the driver logging mechanism. If the driver cannot locate the specified file when establishing the connection, the connection fails and the driver returns an error.

Default: None
Initialization String One or multiple SQL commands to be executed by the driver after it has established the connection to the database and has performed all initialization for the connection. If the execution of a SQL command fails, the connection attempt also fails and the driver returns an error indicating which SQL command or commands failed.

Default: None
Config Options Determines how the embedded database and the mapping of the remote data model to the relational data model is configured, customized, and updated. See "Config Options" for more details.

Default: None

Extended Options: Type a semi-colon separated list of connection options and their values. Use this configuration option to set the value of undocumented connection options that are provided by Progress DataDirect Technical Support. You can include any valid connection option in the Extended Options string, for example: 

HostName=mysite.custhelp.com;UndocumentedOption1=value [;UndocumentedOption2=value;]

If the Extended Options string contains option values that are also set in the setup dialog or data source, the values of the options specified in the Extended Options string take precedence. However, connection options that are specified on a connection string override any option value specified in the Extended Options string.

If you finished configuring your driver, proceed to Step 6 in "Data source configuration through a GUI." Optionally, you can further configure your driver by clicking on the following tabs. The following sections provide details on the fields specific to each configuration tab:

  • General tab allows you to configure options that are required for creating a data source.
  • SQL Engine tab allows you to configure the SQL Engine's behavior.
  • Web Service tab allows you to configure web service behavior.
  • Pooling tab allows you to configure connection pooling behavior.