FDI - Custom schema recommended?

Question

Using a custom schema for ETL and semantic model extensions instead of OAX_USER has been our practice for a while, based on guidance like this:

FDI: Replicating access of OAX_USER for a Custom Schema

The original blog we used to reference for custom ETL setup is now a 404, and we're finding a few other older articles have gone the same way. The credential-sharing risk is the main argument we have on record, but we've also seen "creating a custom database schema is highly recommended" in the Write Back doc without much explanation of why.

Is there a more complete/current write-up of the reasoning anywhere? Specifically curious whether OAX_USER's grants or synonyms get touched during patches/upgrades in a way that could affect any custom objects sitting in that schema. We already follow the custom-schema approach but would like something official we can point to for internal documentation rather than relying on blog posts that keep disappearing.

RVohra · Answer

@Victor H , these recommendations are mostly provided by Oracle Analytics in house Architects for the greater benefit of the community via various channels like blogs/announcements/webinars etc. For the confirmed sources, either we directly reach out to the person who published the blog or get the help via Service Request. Hope it helps!

Victor H · Answer

Hi Rajesh , we know SME can be customized, the question is about the recommendation to use Custom schema for both ETL and semantic extensions.

In other words, what is lost if we use OAX_USER for everything?

We already use a custom schema and are just looking for confirmed sources that reinforce this decision.

RVohra · Answer

@Victor H ,

It is well documented that we can customize the semantic model to extend it for our business requirements. Please refer following official documentation - Customize Oracle Fusion Data Intelligence

Also, Oracle ADW is a symmetrical multiprocessing database. This database is provisioned as part of Fusion Data Intelligence instance creation. By default, you get these two users:

ADMIN – Access to create, modify, and lock custom users, reset the password for OAX_USER, and query the data dictionary and various administrator functionalities including creating Oracle Machine Learning users.

OAX_USER – Query all the data warehouse tables created. All of these tables have a prefix DW_ and are accessible as public synonyms. It is also published by Solution Architect from Oracle Analytics in here

FDI: Replicating access of OAX_USER for a Custom Schema | analytics

Although, I did not find anything where Oracle has documented whether OAX_USER's grants or synonyms get touched during patches/upgrades in a way that could affect any custom objects sitting in that schema. If you are really looking for a confirmation that I would advise logging a Service Request and hopefully it will be confirmed by the Oracle Analytics Product Team.

Hope it helps!

Thanks

Rajesh