Oracle Communities

Oracle Analytics and AI

Child Item

OAS 2025 – Semantic Modeler option missing in Console/Data

Hello,

I’m on OAS 2025 (after migration from OBIEE 11g) with full BIAdministrator rights, but I can’t see the Semantic Modeler option under Console or Data (only Datasets, Connections, Data Flows, Sequences).

In Advanced System Settings there is no Preview Features / Semantic Modeler toggle either.

What actions do I need to take in order to start creating a Data Model using the new Semantic Modeler tool?

Find more posts tagged with

Console

Semantic Modeler

BIAdministrator

missing

Accepted answers

Gianni Ceresa

Hi,

Did you import and override the security of your OAS?

If you did, you "lost" the privileges required to access the semantic modeler, because those didn't exist in your old OBIEE security model.

You need to grant your admin role the lost policies again to have access to it. If you check MOS (or even the upgrade doc I believe), there are scripts you can execute to re-grant your admin role the needed policies.

PS: there isn't a "preview" toggle anymore, semantic modeler is there fully in OAS 2025.

All comments

Gianni Ceresa

Hi,

Did you import and override the security of your OAS?

If you did, you "lost" the privileges required to access the semantic modeler, because those didn't exist in your old OBIEE security model.

PS: there isn't a "preview" toggle anymore, semantic modeler is there fully in OAS 2025.

Themis

Hello @Gianni Ceresa ,

This is what actually happened. The privileges were lost during the migration from OBIEE 11g to OAS 2025 and I couldn't see Semantic Modeler through DV (Data Vizualisation) tool.

I ran the following command on file server and then restarted BI Server and BI Presentation Services and 'Semantic Modeler' appeared on DV interface

$DOMAIN_HOME/bitools/bin/grantPermissionSetsToBIRole.sh -r BIAdministrator -p semanticmodeler.author

Gianni Ceresa

This is typically one of the issues I have with the BAR import behaviour: full replacement, no way to merge things. Merging would be a valid option for the security.

Because of this every upgrade from OBIEE to OAS results in missing policies.

This is why what I now do is to never import security from BAR files, but instead use versioning and scripts: export the default security model and all the policies as WLST commands from a fresh OAS install, merge the new policies with the WLST commands creating my required security model (from a previous OAS or OBIEE), and that gives me a fresh set of WLST commands creating my whole security model.
From there I manage it like "change" scripts: commands to remove things, commands to apply or create things.

I like to have the full control over my security instead of letting a BAR decide if it does replace everything or nothing.