Oracle Connection

Use this connection to access data in Oracle.

Configuration

Property

Macro Enabled?

Version Introduced

Description

Property

Macro Enabled?

Version Introduced

Description

Name

No

 

Required. Name of the connection. Connection names must be unique in a namespace. Connection names can only include letters, numbers, underscores, and hyphens.

Description

No

 

Optional. Description of the connection.

JDBC Driver Name

Yes

 

Required. Select the JDBC driver name to use.

Host

Yes

 

Required. Host name or IP address of the database server to connect to.

Default is localhost.

Port

Yes

 

Required. Port number of the database server to connect to. 

Default is 1521.

Connection Type

No

 

Required. Whether to use an SID, Service Name, or TNS Connect Descriptor when connecting to the database.

SID/Service Name/TNS Connect Descriptor

Yes

 

Required. Oracle connection point (Database name, Service name, or a TNS Connect Descriptor). When using TNS, place the full TNS Connect Descriptor in the text field. For example: (DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = 123.123.123.123)(PORT = 1521))(CONNECT_DATA =(SERVER = DEDICATED) (SERVICE_NAME = XE)))

Username

Yes

 

User identity for connecting to the specified database. Required for databases that need authentication. Optional for databases that do not require authentication.

Password

Yes

 

Password to use to connect to the specified database.

Role

No

 

Login role of the user when connecting to the database.

Default is Normal.

Transaction Isolation Level

Yes

6.7.0

Optional. The transaction isolation level of the databse connection

  • TRANSACTION_READ_COMMITTED: No dirty reads. Non-repeatable reads and phantom reads are possible.

  • TRANSACTION_SERIALIZABLE (default): No dirty reads. Non-repeatable and phantom reads are prevented.

  • Note: If the user role selected is SYSDBA or SYSOPER, the plugin will default to TRANSACTION_READ_COMMITTED to prevent ORA-08178 errors

Connection Arguments

Yes

 

Optional. A list of arbitrary string tag/value pairs as connection arguments. These arguments will be passed to the JDBC driver, as connection arguments, for JDBC drivers that may need additional configurations. This is a semicolon-separated list of key-value pairs, where each pair is separated by a equals ‘=’ and specifies the key and value for the argument. For example, ‘key1=value1;key2=value’ specifies that the connection will be given arguments ‘key1’ mapped to ‘value1’ and the argument ‘key2’ mapped to ‘value2’.

Path of the connection

To browse, get a sample from, or get the specification for this connection through Pipeline Microservices, the path property is required in the request body. It can be in the following form:

  1. /{database}/{schema}/{table} This path indicates a table. A table is the only one that can be sampled. Browse on this path to return the specified table.

  2. /{database}/{schema} This path indicates a schema. A schema cannot be sampled. Browse on this path to get all the tables under this schema.

  3. /{database} This path indicates a database. A database cannot be sampled. Browse on this path to get all the schemas under this database.

  4. / This path indicates the root. A root cannot be sampled. Browse on this path to get all the databases visible through this connection.

Created in 2020 by Google Inc.