Oracle

CARTO + Oracle is in private preview

Oracle connections are only enabled to selected organizations. To become part of the private preview, please get in touch with your CARTO representative.

If you want to learn more about what's included, please check the Oracle Supported Features and the Limitations & FAQs sections.

You can use CARTO with your data in an Oracle database, with full support for Oracle Spatial (SDO_GEOMETRY) and GeoRaster data types. CARTO supports Oracle Database 19c and higher.

Authentication with Oracle Wallet

Oracle connections in CARTO use Oracle Wallet for secure authentication. Oracle Wallet is a container that stores authentication and signing credentials, including private keys, certificates, and trusted certificates needed for secure connections.

If you want to create a connection to your Oracle database, you need to select the Oracle connector in the New connection dialog. After you select the connector click on the Setup connection button.

Required Parameters

To establish a connection, you need to provide the following:

• Name: The name for the Oracle connection you're creating. You can use the name to identify different connections.

• Wallet File (ZIP): Upload your Oracle Wallet file containing the security credentials and certificates. This file is typically provided by your Oracle database administrator.

• Wallet Password: The password protecting your Oracle Wallet file.

• Username: Name of the user account that will access the Oracle database.

• Password: Password for the user account.

About Oracle Wallet

Oracle Wallet files are ZIP archives containing security credentials. Your database administrator can provide this wallet file along with the connection string and wallet password. For Oracle Autonomous Database, you can download the wallet file from the Oracle Cloud Console.

Once you have entered all the parameters, you can click the Connect button. CARTO will try to connect to your Oracle database using the wallet credentials. If everything is OK, your new connection will be registered.

CARTO will try to minimize and reuse the number of connections (sockets) made to the Oracle database. But in some cases the amount of connections can grow rapidly. If you have a strong requirement to control the incoming connections to your database, we recommend configuring connection pooling on your Oracle database.

The connections are only reused if they are going through the same CARTO-Oracle Connection. If you set up many Connections in your organization, the amount of database connections will grow faster.

Advanced options

Note: Analytics Toolbox and Data Observatory locations are not yet available for Oracle connections.

• CARTO temp location

  Location to store temporary tables used during workflow execution. These include intermediate tables with hashed names created by nodes in a workflow. By default, CARTO uses a carto_temp schema per database. Example: my_oracle_db.carto_temp

IP Whitelisting

If you're using the cloud version of CARTO (SaaS), CARTO will connect to Oracle using a set of static IPs for each region. Check this guide to find the IPs you need to allow for your specific region.

Supported Features

Oracle Spatial & GeoRaster Support

Oracle connections fully support:

• Oracle Spatial (SDO_GEOMETRY): Native support for Oracle's spatial data type, including point, line, and polygon geometries

• GeoRaster: Support for raster data analysis with dedicated workflow components

• Self-Hosted Deployments: Available in both CARTO Cloud and Self-Hosted environments

Limitations & FAQs

Oracle connections in CARTO are currently under private preview currently have the following limitations:

• Analytics Toolbox: The general Analytics Toolbox (spatial analysis functions like clustering, enrichment, and spatial indexes) is not yet available for Oracle. However, 55+ standard workflow components are supported, including extensive spatial operations, plus Oracle-specific components for raster analysis and geocoding.

• Data Import: Direct file import to Oracle tables through the CARTO interface is not yet supported. Data must be loaded directly into Oracle using native tools.

• Workflows: Oracle supports most standard workflow components including spatial operations (buffer, intersection, centroid, etc.), data operations (select, join, filter, etc.), and Oracle-specific components (geocoding, raster loading and analysis). Components that depend on the Analytics Toolbox (H3/Quadbin indexes, clustering, enrichment, ML) are not yet available. See the Workflows Components documentation for the complete list.