Oracle Database

Connect Foundry to Oracle Database to read and sync data between Oracle databases and Foundry.

The Oracle Database connector is a Palantir-provided driver connector. Review the official documentation for this driver ↗.

Supported capabilities

Setup

1. Open the Data Connection application and select + New Source in the upper right corner of the screen.
2. Select Oracle from the available connector types.
3. Choose to run the source capabilities on a Foundry worker or on an agent worker.
4. Follow the additional configuration prompts to continue the setup of your connector using the information in the sections below.

Learn more about setting up a connector in Foundry.

Authentication

The Oracle Database connector supports authentication using a username and password. We recommend using service credentials rather than individual user credentials.

Networking

If running the connection on an agent worker, the agent must be allowed to connect to the Oracle database. This means that the agent must be able to reach the destination IP address, and the destination system must be configured to allow connections from the agent.

If running the connection in Foundry, be sure to add the appropriate egress policies to the connector:

The default port for Oracle database connections is 1521, but your specific configuration may use a different port.

Connection details

Change data capture

The Oracle Database source supports change data capture (CDC) syncs.

Foundry CDC syncs from Oracle Databases use Debezium to capture row-level changes. This requires one-time system configuration changes, privilege grants, and supplemental logging enabled at a table-level. To configure your Oracle Database to allow a user named PLTR to set up a CDC sync on MY_SCHEMA.MY_TABLE, you can run the following commands:

-- One time configuration changes
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
 
ALTER USER PLTR QUOTA UNLIMITED ON PALANTIR_DATA;
GRANT CONNECT, RESOURCE TO PLTR;
GRANT SELECT_CATALOG_ROLE TO PLTR;
GRANT SELECT ON V_$DATABASE TO PLTR;
GRANT SELECT ON V_$LOGMNR_CONTENTS TO PLTR;
GRANT SELECT ON V_$LOGMNR_LOGS TO PLTR;
GRANT SELECT ON V_$LOGMNR_PARAMETERS TO PLTR;
GRANT SELECT ON V_$LOGFILE TO PLTR;
GRANT SELECT ON V_$LOG TO PLTR;
GRANT SELECT ON V_$ARCHIVED_LOG TO PLTR;
GRANT SELECT ON V_$ARCHIVE_DEST_STATUS TO PLTR;
GRANT EXECUTE ON "SYS"."DBMS_FLASHBACK" TO PLTR;
GRANT EXECUTE ON "SYS"."DBMS_LOGMNR_D" TO PLTR;
GRANT EXECUTE ON "SYS"."DBMS_LOGMNR" TO PLTR;
GRANT EXECUTE ON DBMS_LOGMNR TO PLTR;
GRANT SELECT ANY DICTIONARY TO PLTR;
GRANT SELECT ANY TRANSACTION TO PLTR;
GRANT CREATE SESSION TO PLTR;
GRANT LOGMINING TO PLTR;
 
-- Table-level configurations, repeat for each table
GRANT SELECT, LOCK, FLASHBACK ON TABLE "MY_SCHEMA"."MY_TABLE" TO PLTR
ALTER TABLE "MY_SCHEMA"."MY_TABLE" ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;

Troubleshooting

Oracle listener logs can provide valuable information about the connection attempts from the Palantir CDC connector. Check the log for any connection-related errors or issues. The default location of the listener log is:

Copied!
1
$ORACLE_BASE/diag/tnslsnr/<hostname>/<listener_name>/trace/listener.log

You can check the active sessions in the Oracle Database to determine if the user is connected. To do this, run the following SQL query:

Copied!
1
SELECT username, osuser, status, machine, program FROM v$session WHERE username = `<user>`;

If the V_ $ tables grants fail, try running the following query with SYS.V_ $:

Copied!
1
GRANT SELECT ON SYS.V_$DATABASE TO `<user>`;

The Oracle alert log contains important information about the database's operations, errors, and other significant events. The location of the alert log depends on your Oracle version and configuration. It is typically located in:

Copied!
1
$ORACLE_BASE/diag/rdbms/<db_unique_name>/<instance_name>/trace/alert_<instance_name>.log

If the connector does not seem to be receiving new change events, it might be due to infrequent log switches. Query the V $ LOG_HISTORY view to see the history of log switches and their frequency:

Copied!
1
SELECT * FROM v$log_history ORDER BY first_time DESC;

Set parameter ARCHIVE_LAG_TARGET to force a switch at regular intervals if required.

Ensure that your Oracle database is running in ARCHIVELOG mode, as this is a requirement for the connector to work. You can check the current mode with the following query:

Copied!
1
SELECT log_mode FROM v$database;

If ARCHIVELOG mode is not enabled, you can enable it with the following commands:

Copied!
1
2
3
4
5
6
7
8
ORACLE_SID=<SID> <user> sqlplus /nolog
CONNECT sys/top_secret AS SYSDBA
alter system set db_recovery_file_dest_size = 10G;
alter system set db_recovery_file_dest = '/opt/oracle/data/recovery_area' scope=spfile;
shutdown immediate
startup mount
alter database archivelog;
alter database open;

Ensure that minimal supplemental logging is enabled at the database level. You can check if it is enabled with the following query:

Copied!
1
SELECT supplemental_log_data_min FROM v$database;

Virtual tables

This section provides additional details around using virtual tables from an Oracle Database source. This section is not applicable when syncing to Foundry datasets.

When using virtual tables, remember the following source configuration requirements:

• You must use a Foundry worker source. Virtual tables do not support use of agent worker connections.
• Ensure that bi-directional connectivity and allowlisting is established as described in the Networking section above.
• If using virtual tables in Code Repositories, refer to the related documentation for details about additional required source configurations.
• When setting up the source credentials, you must use username/password.