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.
Setting database properties
There are two connection types: Basic and Oracle Wallets.
This field will only appear if you selected the "via Direct Access gateway" data connection. Select the data gateway through which you need to connect to your data source.
Information noteUsers that need to leverage gateway-enabled data connections must have the Can Consume Data permission for the space with which the gateway is associated.
|Host name||Host name to identify the location of the Oracle database.||Yes|
|Port||Server port for the Oracle database.||Yes|
|Service name||The alias name for the TNS service.||Yes|
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
|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
Qlik Sense: Oracle authentication properties
|Username||User name for the Oracle connection.|
|Password||Password for the Oracle connection.|
Name of the Oracle connection.
The default name will be used if you do not enter a name.
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 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.
|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
If you have large datasets, the Bulk Reader will automatically load larger portions of data in the iterations within a load, instead of loading data row by row.
|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.
Name of the custom property. You can add additional properties by clicking the .
Value of the property.