Configure Connection

Oracle Database guide

Install ODP.NET, prepare database account permissions, and configure and test the Oracle connection in NIM.

Before you startDirect link to Before you start

NIM requires Driver install path, Data source, and a service account or explicit credentials. Arrange an Oracle account with access to the tables or views your process will use.

Install the Oracle driverDirect link to Install the Oracle driver

Obtain the ODP.NET driver. The existing connector setup uses ODP.NET_Managed_ODAC122cR1.zip; confirm the package required by your connector version before substituting another release.
Extract the package on the NIM server.
From the extracted installer directory, run the existing installation command in an elevated Command Prompt:
```
install_odpm.bat C:\Oracle x64 true
```
Record the driver installation path and ensure it is accessible to the account running NIM.

Connect as an administratorDirect link to Connect as an administrator

Use an account authorized to create users and grant the required privileges. For example, start SQL*Plus and connect as SYSTEM, entering the password when prompted:

sqlplus system@your_db

Replace your_db with the target database service. For a multitenant database, connect to the intended pluggable database before creating a local integration user.

Create the integration userDirect link to Create the integration user

Replace nim_user and the password placeholder with your values:

CREATE USER nim_user IDENTIFIED BY "REPLACE_WITH_A_SECURE_PASSWORD";

If the account will own database objects and needs explicit storage settings, use this alternative instead, adapting the tablespaces and quota to your environment:

CREATE USER nim_user
IDENTIFIED BY "REPLACE_WITH_A_SECURE_PASSWORD"
DEFAULT TABLESPACE users
TEMPORARY TABLESPACE temp
QUOTA 100M ON users
ACCOUNT UNLOCK;

Tablespace quotas allocate storage for objects the account owns; they are not required merely to read another schema's data. See Oracle's user account guidance.

Grant connection and data permissionsDirect link to Grant connection and data permissions

Allow the account to sign in:

GRANT CREATE SESSION TO nim_user;

Grant read access to each required table or view, replacing source_schema.source_table with the actual object:

GRANT SELECT ON source_schema.source_table TO nim_user;

For a process that needs full CRUD on records in an existing table, grant the required data privileges:

GRANT SELECT, INSERT, UPDATE, DELETE
ON source_schema.source_table TO nim_user;

Use the grants needed by your process. The CONNECT and RESOURCE roles are not required for source collection and do not replace explicit access to another schema's tables. Have the administrator grant additional object-creation privileges only if your process needs them.

Enter the connection settingsDirect link to Enter the connection settings

In NIM Studio, open Systems > Overview and add an Oracle Database system, or select the existing system.
Open its Connection screen.
Enter the following settings and save the connection.

Setting	Value
Driver install path	The location of the ODP.NET installation used by the connector, such as `C:\Oracle`.
Data source	The Oracle connection identifier or descriptor supplied by your database administrator for the target database service.
Service account or credentials	The connection identity authorized for Oracle access. Use the NIM service account only when Oracle authentication is configured for that identity; otherwise specify the database username and password in the connection settings.

Test the database connectionDirect link to Test the database connection

Select Test Connection. NIM attempts to open a connection to the configured Oracle database.
Confirm that the connection opens successfully. If it fails, check the driver installation and path, data source, network access, credentials or service identity, and CREATE SESSION privilege.
Collect the system and inspect the expected tables or query results.
If connection succeeds but collection fails, verify schema-qualified object names and the account's table or view permissions.
Validate the collected records and matching rules before using Oracle as source or supplemental data for automation.

A successful connection test does not confirm access to every object or operation. Validate collection and any intended writes separately.

Step 1 of 4