Skip to main content Skip to complementary content

Create an Oracle connection

To access your data stored on an Oracle database, you will need to know the server and database name that you want to connect to, and you must have access credentials. Once you have created a connection to an Oracle database, you can select data from the available tables and then load that data into your app.

In Qlik Sense, you connect to an Oracle database through the Add data dialog or the Data load editor.

In QlikView you connect to an Oracle database through the Edit Script dialog.

Warning noteIf your Qlik Sense deployment is installed on the same computer as your Oracle database, there may be shared environmental variables. This could cause conflicts.

Setting database properties

There are two connection types: Basic and Oracle Wallets.

Basic connection

If you are using Qlik Sense Enterprise Client-Managed, the Oracle Connector requires additional configuration for the TNS service. The following two TNS files must be modified for the Oracle environment. You can get these files from your Oracle configuration.

  • tnsnames.ora: set the host addresses and ports for the TNS service.
  • sqlnet.ora: set the location of the Oracle wallet.
Database properties that can be configured for basic connections
Database property Description Required
Host name Host name to identify the location of the Oracle database. Yes, unless using TNS Service Name
Port Server port for the Oracle database. Yes, unless using TNS Service Name
Service name The alias name for the TNS service. Yes, unless using TNS Service Name
Use TNS Service name Use the TNS name defined in the tnsnames.ora file instead of the TNS alias name. This option only appears on Qlik Sense Enterprise Client-Managed. No
TNS Name The TNS name defined in the tnsnames.ora file. This option only appears on Qlik Sense Enterprise Client-Managed. No

Oracle Wallet connection

Your Oracle wallet-file must be in zip format. The maximum file size is 500 KB. The zip file must contain the following files:

  • An .sso file

  • tnsnames.ora

Database properties that can be configured for Oracle Wallet connections
Database property Description Required
Configuration File The Oracle wallet-file in zip format. After you add the file, click Validate. Yes
Service This dropdown will be populated with your service options once you validate your wallet-file. Yes

Authenticating the driver

Information noteThe Oracle Connector does not support NTLM authentication in version 4.0. For that reason, the Windows integrated security option is not available.

Qlik Sense: Oracle authentication properties

Authentication properties that can be configured
Authentication property Description
Username User name for the Oracle connection.
Password Password for the Oracle connection.
Name

Name of the Oracle connection.

The default name will be used if you do not enter a name.

QlikView: Oracle authentication properties

Authentication properties that can be configured
Authentication property Description
Username User name for the Oracle connection.
Password Password for the Oracle connection.

Account properties

Credentials

Credentials are used to prove that a user is allowed to access the data in a connection.

There are two types of credentials that can be used when making a connection in Qlik Sense SaaS. If you leave the User defined credentials check box deselected, then only one set of credentials will be used for the connection. These credentials belong to the connection and will be used by anyone who can access it. For example, if the connection is in a shared space, every user in the space will be able to use these credentials. This one-to-one mapping is the default setting.

If you select User defined credentials, then every user who wants to access this connection will need to input their own credentials before selecting tables or loading data. These credentials belong to a user, not a connection. User defined credentials can be saved and used in multiple connections of the same connector type.

In the Data load editor, you can click the Primary key underneath the connection to edit your credentials. In the hub or Data manager, you can edit credentials by right-clicking on the connection and selecting Edit Credentials.

See which authentication type applies on each connector's page.

Account properties that can be configured
Account property Description
User defined credentials Select this check box if you want users that access this connection to have to input their own credentials. Deselect this check box if credentials can be shared with anyone who has access to this connection.
New credentials Drop-down menu item that appears if User defined credentials is selected.
Existing credentials Drop-down menu item that appears if User defined credentials is selected.
User User name for the connection.
Password Password for the connection.
Credentials name Name given to a set of user defined credentials.

Load optimization settings

Load properties that can be configured
Property Description Required
Max String Length

Maximum length of string fields. This can be set from 256 to 16384 characters. The default value is 4096. Setting this value close to the maximum length may improve load times, as it limits the need to allocate unnecessary resources. If a string is longer than the set value, it will be truncated, and the exceeding characters will not be loaded.

No

Advanced options

Information noteThis section is for advanced users who want to add their own custom connection parameters that are not displayed above.
Advanced options that can be configured
Property Description Required

Name

Name of the custom property. You can add additional properties by clicking the Plus sign icon.

No
Value

Value of the property.

No
Information noteWhen you connect to an Oracle database with the Data load editor or the Edit Script dialog, Test Connection enables you to test the connection before you attempt to create it.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!