What you own, and what you rent

The product line has been renamed repeatedly, which is why searching for help scatters the answers across four names. The lineage runs OBIA, then OAX, then FAW, now FDI, and forum threads about any one of them often answer questions about another.

FDI is Oracle-managed end to end: Oracle’s schema, Oracle’s refresh cadence, Oracle’s pricing. Peer reviews, practitioner-reported, describe data-sync and accuracy issues, a challenging setup, and out-of-the-box content that needed significant rebuilding before it matched how the business actually reports. A frequent-refresh feature was flagged for deprecation while customers were mid-flight on it, which is what a vendor-owned roadmap means in practice.

Customization is where the boundary shows. Extending FDI beyond its delivered content requires a separate managed database and your own pipelines, and those pipelines face the same enablement constraints this catalog documents in what the delivered extractor does not carry. At that point you are running an ownership build anyway, inside someone else’s walls.

FDI is a reasonable choice when the delivered content is close to what you report, your toolchain is already Oracle’s analytics stack, and a managed refresh you do not control is an acceptable trade for not running pipelines. Plenty of shops fit that description, and for them the product does what it says.

Owning wins when the models are yours: custom facts the delivered schema does not carry, history retention you set rather than inherit, freedom to point any tool at the data, and exit rights.

That last one means the warehouse, the history, and the models stay with you when the vendor renames the product a fifth time. Either way, both paths exist because the embedded tool remembers nothing, and the only real mistake is staying there.