Enhancement: OAC Data Flows – Support PostgreSQL as Output Target (Save Data / Write-back)

Alessandro_Moccia

We request an enhancement to Oracle Analytics Cloud (OAC) Data Flows to support PostgreSQL as a native output target for the “Save Data” / Data Flow output persistence feature.

Current limitation: PostgreSQL is supported as a data source for connectivity and analytics, but it does not support “Supports saving output from data flows” in the official PostgreSQL connector documentation. As a result, OAC Data Flows cannot persist curated/transformed outputs directly into PostgreSQL.

Our target architecture is enterprise-grade and private: OAC is deployed in a private subnet and reaches PostgreSQL hosted on Google Cloud Platform (GCP) via Private Access Channel (PAC) and private connectivity (OCI FastConnect + Interconnect). The required capability is to materialize Data Flow outputs back into PostgreSQL without introducing intermediate Oracle databases (ADW/ATP/Oracle DB) or Spark/Hive as staging layers.

Oracle Support SR 4-0001796564 confirmed this is not supported and stated there is no workaround, advising to submit an Idea Lab request for a future release.

Business need: enable governed data preparation in OAC (Data Flows) and publish curated datasets directly to PostgreSQL as an analytics-ready store, supporting standard load patterns (append/replace/upsert) and operational controls (scheduling, monitoring, retry). This reduces complexity, cost, and operational risk compared to external pipelines or intermediate staging databases