Oracle
Integrate Oracle Database with Acceldata Data Observability Cloud (ADOC) to ensure end-to-end data reliability and observability across your Oracle ecosystem.
Oracle Database is a leading relational database management system (RDBMS) used for enterprise-scale data storage and processing. Integrating Oracle with ADOC enables organizations to gain visibility into data health, performance, and reliability. Once configured, ADOC continuously monitors data quality and operational metrics from your Oracle instances.
Supported Versions
ADOC supports integration with Oracle Database (both Standalone and Oracle Cloud Autonomous Database environments).
| Component | Supported Versions |
|---|---|
| Oracle Database | Oracle Database 21c Enterprise Edition Release 21.0.0.0.0 – Production<br>Version 21.3.0.0.0 |
| Oracle Cloud Autonomous Database (ADB) | Supported |
Ensure your Oracle instance is reachable through the configured JDBC connection before integration.
Supported Authentication Methods
| Authentication Type | Description |
|---|---|
| Username/Password | Standard authentication using Oracle database credentials. |
| Wallet-based Authentication (for Oracle ADB) | Uses Oracle Cloud wallet credentials for secure access. |
Prerequisites and Permissions
Before connecting Oracle to ADOC, ensure the following prerequisites are met:
- You have an existing or newly created Data Plane in ADOC. See Data Plane Installation Guide for setup instructions.
- The Oracle user account used for integration must have the following permissions:
GRANT SELECT ANY DICTIONARY TO <ORACLE_USER>;;GRANT SELECT_CATALOG_ROLE TO <ORACLE_USER>;;Replace <ORACLE_USER> with your Oracle username. Contact your DBA if additional privileges are required.
- You have the following Oracle connection details ready:
- JDBC URL (for example,
jdbc:oracle:thin:@<HOST>:<PORT>/<SERVICE_NAME>) - Username and password
- (Optional) Wallet credentials for Oracle Cloud ADB
- JDBC URL (for example,
Configuration Parameters
The following configuration parameters are required when adding Oracle as a data source:
| Parameter | Description | Mandatory | Example |
|---|---|---|---|
| Data Source Name | Unique name for the Oracle connection. | ✅ | Oracle-Prod-DB |
| Description | Optional notes about the data source. | ❌ | Production Oracle data source |
| Data Plane | Select the Data Plane to be used for observability. | ✅ | dp-west-us |
| JDBC URL | Oracle JDBC connection string. | ✅ | jdbc:oracle:thin:@mydb.us-east-1.oraclecloud.com:1521/ORCLPDB1 |
| JDBC Username | Oracle database username. | ✅ | adoc_user |
| JDBC Password | Oracle database password. | ✅ | |
| Wallet Credentials (ADB only) | Credential zip file for Oracle Cloud ADB. | ⚙️ Required for ADB | /path/to/wallet.zip |
| Database Name(s) | List of Oracle databases to monitor. | ✅ | HRDB, SALESDB |
| Crawler Execution Schedule | Time and frequency for data crawler jobs. | Optional | Daily 12:00 UTC |
Adding Oracle as a Data Source
Follow these steps to integrate Oracle Database with ADOC:
Navigate to the Register page from the left main navigation menu.
Click Add Data Source under the Data Sources tab.
Choose Oracle from the list of supported data sources.
Fill in the Data Source Details:
- Enter a name and optional description.
- Ensure the Data Reliability toggle is enabled.
- Select an existing or create a new Data Plane.
Click Next to configure Connection Details.
Choose your Oracle Environment Type:
- ** Standalone: Enter JDBC URL, username, and password.
** - Oracle Cloud ADB: Provide JDBC URL, credentials, and upload wallet files.
Click Test Connection to verify connectivity.
On the Set Up Observability page:
- Enter one or more database names to monitor.
- (Optional) Enable Crawler Execution Schedule and set a preferred frequency.
Click Submit to complete setup.
Once completed, an Oracle card appears in the Data Sources page, showing key statistics such as connection health, crawler status, and monthly cost.
Troubleshooting
Issue: Cadence Jobs Failing with ORA-00942 (Table or View Does Not Exist)
Possible Cause: The Oracle user does not have required permissions to access metadata tables.
Solution: Ensure the Oracle user is granted the following permissions:
GRANT SELECT ANY DICTIONARY TO <ORACLE_USER>;GRANT SELECT_CATALOG_ROLE TO <ORACLE_USER>;Replace <ORACLE_USER> with the user specified during configuration.
Next Steps
Explore the Data Reliability module for detailed monitoring options.