Skip to main content

Prerequisites

Create a dedicated Prizm connection user in Oracle and grant it the minimum required privileges before connecting.
SELECT ON SYS.DBA_HIST_SQLSTAT requires the Oracle Diagnostics Pack license. If it isn’t licensed, skip this grant — the connector falls back to V$SQL/V$SESSION only and shows an advisory in the Prizm integration health dashboard rather than failing.

Required Privileges Reference

Connector Setup

1

Open the connector wizard

Navigate to Source and click the + icon next to the source list. Search for and select Oracle from the connector grid.
2

Enter source details

3

Provide credentials

Toggle Use Vault to retrieve credentials from a vault instead of entering them directly.
4

Save and verify

Click Next. Prizm validates the connection at this point — there’s no separate “Test Connection” step. If validation fails, a message appears identifying the problem (for example, Credential validation failed: [Errno -5] No address associated with hostname for an unreachable host). Once validation succeeds, Prizm runs an initial catalog crawl and assets appear in the catalog within a few minutes.Navigate to Settings → Connectors → Logs to monitor scan progress.

Next Steps

What We Collect

See the full field-level breakdown of every metadata object Prizm extracts.

FAQ

Common questions about credentials, scoping, and permissions.

Troubleshooting

Diagnose connection failures, permission errors, and timeouts.