In this article

Overview

Use this account type to connect Oracle Snaps with data sources that use Oracle accounts. This account uses dynamic values and enables you to specify account properties as expressions that reference Pipeline parameters.

Loading

Prerequisites

Kerberos authentication for Oracle setup in the Windows/Linux environment.

Known Issues

None.

Account Settings

Parameter Name	Data Type	Description	Default Value	Example
Label*	String	Required. Unique name for the account.	N/A	Oracle123DB
JDBC URL Source	Dropdown List	Required. The source of the JDBC URL that you want to use. 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 User Provided, the Hostname, Port Number, and Database Name fields are replaced by the Custom JDBC URL field.	Snap Generated	N/A
Account properties*	Fieldset	Required. Enter the information to create a connection to the database.	N/A	N/A
Hostname	String/Expressions	Required if JDBC URL Source is Snap Generated. The server address to which the application must connect. Loading If you need to connect to an on-premise server, specify the domain name or the IP address. For example, test.mydbserver.com or 190.159.0.124.	N/A	oratestdb2.cwztruwzzvnq.us-east-1.rds.amazonaws.com 190.159.0.124
Port number	String/Expressions	Required if JDBC URL Source* is* Snap Generated. The database server's port number to which the application must connect. Loading	1521	1521
Database name	String/Expressions	Required if JDBC URL Source* is* Snap Generated. The database name to which the application must connect. Loading	N/A	MYDB
Custom JDBC URL	String/Expressions	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: `jdbc:oracle:thin:@(DESCRIPTION=(FAILOVER=on)(ADDRESS_LIST=(LOAD_BALANCE=on)(CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS=(PROTOCOL=TCP)(HOST=host1)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=host2)(PORT=1522)))(CONNECT_DATA=(SERVICE_NAME=OracleTest)))` Loading	N/A	N/A
Username	String/Expressions	The 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. Loading	N/A	TECTONIC
Password	String/Expressions	The 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. Loading	N/A	N/A
JDBC JARs	Fieldset	List of JDBC JAR files to be loaded. Click to add a JDBC Driver, click to remove a JDBC Driver.	N/A	N/A
JDBC driver	String	Loading When you use the relative path for the JDBC JAR file in accounts across different projects, the pipelines fail with the `JAR FILE NOT FOUND` error. Therefore, you must use the absolute path for the JDBC JAR file to run your pipelines successfully. Only v11.2.0.4.0 of a JDBC driver supports user-defined types.	N/A	Project Spaces/my_diagnostic_space/my_diagnostic /sqljdbc4-2.0.jar
JDBC driver class*	String	Required. The name of the JBDC driver to use.	oracle.jdbc.OracleDriver	oracle.jdbc.OracleDriver
Database specifier type*	Dropdown List	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 name	Service name
SSL/ TCPS	Checkbox	Opt for or against connecting through SSL to the Oracle instance. If selected, the following format of URL is used internally: jdbc:oracle:thin@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCPS)(HOST=<HOST>)(PORT=<PORT>))(CONNECT_DATA=(<SID/ SERVICE_NAME>=<DATABASE_NAME>)))	Not Selected	Not Selected
Authentication method	Dropdown List	Choose the authentication method to use when connecting to Oracle. The available options are: User ID and Password Kerberos Kerberos authentication for Oracle supports both Windows and Linux-based databases and also supports Service account and User impersonation Kerberos authentication. When the authentication method is Kerberos, for service account, you must leave the Username and Password fields empty and add the below property to the URL Properties: `oracle.net.kerberos5_cc_name = <Path to cache file>`	User ID and Password	Kerberos
Kerberos config path	String/Expression	Appears when the Authentication method* is Kerberos.* Specify the path to the Kerberos configuration file. Kerberos authentication for Oracle supports both Windows and Linux-based databases and also supports Service account and User impersonation Kerberos authentication.	N/A	/opt/app/oracle/dbhome/network/admin/krb5.conf
Advanced properties	N/A	Specify advanced properties to connect to the database.	N/A	N/A
Auto commit	Checkbox/Expressions	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.	Selected	Selected
Batch size*	Integer/Expressions	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.	50	100
Fetch size*	Integer/Expressions	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.	100	100
Max pool size*	Integer/Expressions	Required. Set the maximum number of connections that a pool must maintain at a time.	50	50
Max lifetime (minutes)*	Integer/Expressions	Required. 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.	30	35
Idle timeout (minutes)*	Integer/Expressions	Required. 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.	5	5
Checkout timeout (milliseconds)*	Integer/Expressions	Required. Set the time in milliseconds to wait for a connection to be available when the pool is exhausted. If you provide 0, the Snap waits infinitely until the connection is available. Therefore, we recommend you not to specify 0 for Checkout Timeout.	10000	10000
URL properties	N/A	Specify input regarding URL properties.	N/A	N/A
URL property name	String/Expressions	Name for the URL property.	N/A	Batch_Refresh_Time
URL property value	String/Expressions	Value for the URL property.	N/A	10

Troubleshooting

Error	Reason	Resolution
`Unable to obtain Principal Name for authentication`	Caused by: javax.security.auth.login.LoginException.	Ensure to provide a valid ticket cache path `(/tmp/krb5cc_Administrator)` and have enough permissions.
`The service in the process is not supported.`	Operation unavailable.	Ensure to create the Kerberos ticket for the user using `"okinit -f"`
`Got minus one from the read call.`	Keytab is not valid.	Ensure to create a new keytab file and place it in `%ORACLE_HOME%/network/admin`.
`The service in the process is not supported.`	An Invalid name provided (Mechanism level: KrbException: Cannot locate default realm)	Ensure to provide valid `krb5.conf` path in the account settings.
`TNS:listener does not currently know of the service requested in the connect descriptor`	Oracle service is down.	Ensure the Oracle service is up and running.
`Cause: Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor`	The Listener refused the connection with the following error: ORA-12505, TNS: The listener does not currently know of the SID given in the connect descriptor.	For Linux environment: `USE_SID_AS_SERVICE_<YOUR_LISTENER_NAME>=on` For Windows environment: `USE_SID_AS_SERVICE_<YOUR_LISTENER_NAME>=on`

Oracle Thin Dynamic Account

Overview

Prerequisites

Known Issues

Account Settings

Troubleshooting

Related Content