DQC

Connection to Oracle Database

Oracle Database is a first-class connector on the DQC Platform. To connect it, provide the credentials of a read-only database user, the service name of the target database, and allow the platform's static IP address. This guide covers every step, including the two Oracle specifics that most often cause a failed first connection: the service name and the uppercase schema.

Add an Oracle connector

To get started:

  1. Go to the Data Connectors screen

  2. Click the Oracle button

  3. Enter the connection details described below

  4. Test and save the connection

Required connection information

Field

Example

Description

Name

Finance_DB

A descriptive name for this connection

User

DQCREADER

Oracle user with read-only access

Password

your_password_here

Password for the specified user

Host

oracle.company.internal

DNS name or IP address of the Oracle server

Port

1521

Default Oracle listener port (adjust if needed)

Service name

ORCLPDB1

The service name of the target database — not an SID and not a file path

Schema

FINANCE (optional)

Default schema for unqualified table names; must be uppercase

Service name, not SID

The connector addresses the database by its service name. If you only know the SID, ask your DBA for the corresponding service name, or read it from the listener:

lsnrctl services

A wrong or unknown service name is rejected by the listener before authentication happens, which surfaces as ORA-12514. A host name that cannot be resolved surfaces as ORA-12545, and an unreachable listener as ORA-12541.

Schema names must be uppercase

Oracle stores unquoted identifiers in uppercase. The optional Schema field therefore only accepts uppercase names — allowed characters are uppercase letters, digits, underscore, dollar sign and hash, and the name must start with an uppercase letter or an underscore. The interface uppercases the value as you type; API clients have to send it already normalised, otherwise the connection is rejected with a validation error.

Leave the field empty to work with fully qualified table names instead. When it is set, the platform switches the session's current schema so unqualified names resolve there.

Best practices for secure authentication

Use a dedicated user

  • Avoid using administrative or shared credentials

  • Create a dedicated technical user for the DQC Platform

Grant read-only permissions

The user needs to log in and to read the tables you want to check — nothing else. For example:

CREATE USER dqcreader IDENTIFIED BY "your_password_here";
GRANT CREATE SESSION TO dqcreader;
GRANT SELECT ON finance.customers TO dqcreader;
GRANT SELECT ON finance.orders TO dqcreader;

Grant SELECT per table or per schema as your governance rules require. The platform runs its queries directly against the database and does not create views, tables or any other objects, so the user needs no CREATE privileges beyond CREATE SESSION.

Whitelist the DQC Platform IP address

Allow inbound connections from the following static IP address in your firewall, security group, or Oracle Connection Manager rules:

3.123.94.228

For Oracle Autonomous Database or Oracle Cloud Infrastructure, add the address to the access control list of the database or to the security list of its subnet.

Notes

  • Encrypted connections are strongly recommended; Oracle Native Network Encryption and TLS are both supported by the driver

  • ORA-01017 means the user name or password is wrong, ORA-28000 means the account is locked

  • Virtual tables and custom SQL rules are available for Oracle connections

  • Learn more: Supported data sources