Oracle Thin Account

In this article


Use this account type to connect Oracle Snaps with datasources that use Oracle accounts.


  • None.


  • None.

Account Settings

Parameter NameData TypeDescriptionDefault ValueExample
LabelStringRequiredUnique name for the account.N/AOracle123DB
JDBC URL SourceString

Required. Select the source of the JDBC URL. 

  • Snap Generated: The JDBC URL that SnapLogic generates using the details you provide in the Account Settings popup.
  • User Provided: The JDBC URLs that you provide directly into the Custom JDBC URL field. 

    If you select the User Provided option, the Host Name, Port Number, and Database Name fields are replaced by the Custom JDBC URL field.

Snap GeneratedN/A
Account propertiesStringRequired. Enter the information to create a connection to the database.N/AN/A
HostnameStringRequired if JDBC URL Source is Snap Generated. The server address to which the application must connect.N/
Port NumberStringRequired if JDBC URL Source is Snap Generated. The database server's port number to which the application must connect.15211521
Database nameStringRequired if JDBC URL Source is Snap Generated. The database name to which the application must connect.N/AMYDB
Custom JDBC URLString

Required if JDBC URL Source is User Provided. The JDBC URLs that you want to use to connect to your Oracle account.

Use this option if you want to use complex JDBC URLs (involving multiple hosts and advanced options) to connect to your Oracle instance. For example, if you want to connect to Oracle DataGuard, you can enter a JDBC like the one below:


UsernameStringThe user name that is allowed to connect to the database. It is used as the default username when retrieving connections. The user name must be valid in order to set up the data source.N/ATECTONIC
PasswordStringThe password used to connect to the data source. It is used as the default password when retrieving connections. The password must be valid in order to set up the data source.N/AN/A

List of JDBC JAR files to be loaded. Click  to add a JDBC Driver; click  to remove a JDBC Driver.

JDBC DriverString

Enter the JDBC jar file to be loaded. Use  to select an existing file. A different driver binary for a driver must have a different name, the same name can not be reused for a different driver. If this property is left blank, a default JDBC driver is loaded.

Only v11. or higher of a JDBC driver supports user-defined types.

JDBC Driver ClassStringRequired. The name of the JBDC driver to
Database specifier typeString

Specify the database specifier type to use. The selected option decides which format of URL for JDBC is to be used internally. The valid options are:

  • SID: Uses the jdbc:oracle:thin@HOST:PORT:DBNAME format.
  • Service name: Uses the jdbc:oracle:thin@//HOST:PORT/DBNAME format. 
Service nameService name

Opt for or against connecting through SSL to the Oracle instance.

If selected, the following format of URL is used internally:


Not SelectedNot Selected
Advanced propertiesN/ASpecify advanced properties to connect to the database.N/AN/A
Auto commitString

Opt for or against setting the auto-commit property for a database.

  • When selected, each of the batches is committed immediately after it is executed. If the Snap fails, only the batch being executed at that moment is rolled back.
  • When not selected, the Snap execution output is committed only after all the batches are executed. If the Snap fails, the entire transaction is rolled back, unless the Snap finds invalid input data before it sends the insert request to the server, and routes the error documents to the Error view.
Batch sizeInteger

Required. Set the number of statements that the Snap must execute at a time.

Select queries are not batched.

Using a large batch size could use up the JDBC placeholder limit of 2100.

Fetch sizeInteger

Required. Set the number of rows that the Snap must fetch at a time when executing a query.

Large values could cause the server to run out of memory.

Max pool sizeIntegerRequired. Set the maximum number of connections that a pool must maintain at a time.5050
Max life timeIntegerRequired. Set the maximum time (in minutes) of a connection in the pool. Ensure that the value you enter is a few seconds shorter than any database or infrastructure-imposed connection time limit. A value of 0 indicates an infinite lifetime, subject to the Idle Timeout value. An in-use connection is never retired. Connections are removed only after they are closed.3035
Idle TimeoutIntegerRequired. Set the maximum time (in seconds) that a connection is allowed to sit idle in the pool. A value of 0 indicates that idle connections are never removed from the pool.55
Checkout timeoutInteger

Required. Set the time in milliseconds to wait for a connection to be available when the pool is exhausted. Zero waits forever.

An exception is thrown after the wait time has expired.

URL PropertiesN/ASpecify input regarding URL properties.N/AN/A
URL property nameStringName for the URL property.N/ABatch_Refresh_Time
URL property valueN/AValue for the URL property.N/A10


Failed to validate account: Failed to retrieve a database connection. ORA-00604: error occurred at recursive SQL level 1 ORA-12705: Cannot access NLS data files or invalid environment specifiedConfiguring your Windows Registry key value, HKEY_CURRENT_USER\Control Panel\International\LocaleName, in the environment to true or en-US has been observed to work for some Windows-based Groundplex instances. Additional probable solutions can be found here

See Also