I built a proxy that makes Oracle Fusion Cloud look like a real Oracle DB on the wire - query it from sqlplus, SQL Developer, or a dblink

Getting data out of Oracle Fusion Cloud normally means BI Publisher, SOAP/XML, or standing up an OIC integration per report. Meanwhile your team already knows sqlplus, SQL Developer, and the Oracle databases they run every day. That mismatch always bugged me, so I built a thing.

ofpgproxy speaks Oracle's own protocol wire - the actual TNS/TTC bytes a real Oracle server sends. Your client thinks it's talking to a genuine Oracle instance. Underneath, every query becomes a call to Oracle's own BI Publisher service against your Fusion tenant.

The part I didn't expect to work as well as it does: even another Oracle database can't tell the difference. Point a dblink at it and it just works - so an EBS instance (or any Oracle DB) can reconcile against Fusion in plain SQL, existing PL/SQL and scripts unchanged.

What that gets you in practice:

- Cross-check EBS vs Fusion during a migration

- Join Fusion data into reports/queries you already run

- Browse the schema from SQL Developer / DBeaver / DataGrip — table tree and autocomplete work like normal

- Dashboards in Metabase, Superset, Power BI

- Pull extracts into DuckDB or dbt

Two things by design: it's read-only (BI Publisher can't write, and neither does the proxy), and it only uses Oracle's documented interface with credentials you supply - nothing scraped, no undocumented endpoints.

Fair warning / caveats: latency is BI-Publisher-bound, so it's built for correctness and querying, not high-QPS OLTP. It's a proxy for reporting/reconciliation workloads, not a Fusion replica.

Releases + quick start: https://github.com/krokozyab/ofpgproxy