Workiva Support Center

With the Oracle® RDBMS | ADW connector, you can use commands in a chain to perform structured query language (SQL) operations in Oracle Relational Database Management System (RDBMS) or Autonomous Data Warehouse® (ADW). For example, with this connector, you can:

• Execute SQL commands, including a CREATE or UPDATE statement or SELECT query
• Retrieve details about a table in Oracle RDBMS or ADW
• Insert records into Oracle RDBMS or ADW

Note: This connector is built by Workiva and connects to a third-party system. While our Support team can help configure this connector within your workspace, we are unable to troubleshoot or otherwise assist with any issues that originate outside of the Workiva platform.

Requirements

To enable the connection to the Oracle database, the connector uses Java database connectivity (JDBC), secured with basic username and password authentication. To set up the connector, you'll need:

• A designated integration user created in Oracle RDBMS or ADW for the connector
• The integration user's username and password
• The JDBC connection's URL, such as jdbc:oracle:thin:@db201905221856_high?TNS_ADMIN=./
• To connect to Oracle ADW, the database's client credentials or wallet files
• To connect to an on-premise database, a GroundRunner for the connection

Supported versions

The Oracle® RDBMS | ADW connector is compatible with the following database versions:

• 21.x
• 19.x
• 18.3
• 12.2
• 12.1
• 11.2.0.4

ADW wallet files

To enable a connection to Oracle ADW, first download the database's client credentials or wallet files. When you set up the connector, you'll upload these wallet files under Resources:

• cwallet.sso.lck\n* ewallet.p12.lck
• cwallet.sso
• ewallet.p12
• keystore.jks
• sqlnet.ora
• tnsnames.ora
• truststore.jks
• ojdbc.properties

To indicate the location of these resources in the connector's Connection URL property, enter the TNS_ADMIN path based on the GroundRunner's operating system:

• For UNIX, TNS_ADMIN=./
• For Microsoft® Windows®, TNS_ADMIN=.

Note: If the connector uses a CloudRunner, use the path TNS_ADMIN=./.

Set up the Oracle RDBMS | ADW connector

Note: To make the connector available for use in your organization's chains, an org security administrator first enables it from Configuration.

1. From Chain Builder, click Connections  compare_arrows, and then Create at the top right.
2. Under Connector Connection, select Oracle RDBMS | ADW and the runner to use with the connector.
   
3. Under Basic Info, enter a unique name and description to help identify the connection.
4. To connect to Oracle ADW, under Resources, upload the database's wallet files.
5. Under Properties, enter the connector's details:
   
   

   Property	Details
   Username	Enter the username of the connector's integration user.
   Password	Enter the password for the Username property.
   Connection URL	Enter the URL for the JDBC connection, such as jdbc:oracle:thin:@db201905221856_high?TNS_ADMIN=./. For Oracle RDBMS, append any optional properties for the connection. For Oracle ADW, append the TNS_ADMIN path for the database's wallet files, based on the selected runner and its operating system. Note: By default, the port for Oracle RDBMS is 1521; however, this may be different for your environment.

   Note: All sensitive credentials are automatically encrypted and stored at Advanced Encryption Standard (AES)-256 encryption. For security purposes, avoid including user credentials as optional properties within the Connection URL property.

6. Select the environments to use with the connection, and click Save.
7. To test the connection, create and run a chain with the connector's Get Table Definition command, and verify it returns a valid output. 

Troubleshooting

If the connection to Oracle RDBMS or ADW fails:

• Verify the integration user's authentication credentials.
• Check the URL for the JDBC connection.
• If connecting to an on-premise database, check the GroundRunner selected for the connector.
• If connecting to Oracle ADW, verify the database's wallet files are uploaded under Resources, and verify their TNS_ADMIN path in the Connection URL property. If necessary, download the wallet files from Oracle ADW and upload them under Resources again.

If the connection fails to perform a command, verify its inputs—such as its SQL syntax or table—are valid.