How to set log level in OAS for semantic modeler?

Szymon Grzęda

Hi,

I am trying to set the global/session log level within the Semantic Model for my OAS instance. I attempted to use the same method as the Admin Tool

Gather and Analyze Query Logs but it doesn't seem to take effect.

I found two articles from last year regarding this limitation, but I'm not certain if Oracle has made any progress on a fix:

Ability to set the system logging level for OAS in Console - System Settings — Oracle

Semantic Modeler - setting System Logging Level when deploying Semantic Model (in deployed RPD) — Oracle

Does anyone know if there is a current workaround or a roadmap update for this?

Michal Zima

Hi @Szymon Grzęda - you exactly pointed to missing feature. The only way how to change Logging Level for deployed Semantic Model is following (this is the way we use): after you deploy your Semantic Model into OAS instance (Semantic Model transformed into RPD and deployed) you open RPD in online mode (from BI Admin Tool) and do the change of Logging Level (from 0) to desired value here. You need to do this "after step" each time you make a ned deploy of Semantic Model. Not very nice, isn't it ?

There is also my Idea created for implementing this missing feature (you have not mentioned in your comments):

https://community.oracle.com/products/oracleanalytics/discussion/26938/semantic-modeler-setting-system-logging-level-when-deploying-semantic-model-in-deployed-rpd

So you can vote for it and hopefully it will get enough attention by Semantic Modeler Development/Product Mgmt team to get it implemented - am I right, @Pravin Janardanam-Oracle ?

Michal Zima

@Szymon Grzęda You are not switching. RPD is still the form of Semantic Model, which gets deployed into running OAS instance. Semantic Model in form of directory structure with JSON files is just development artefact. And this "production" RPD artefact is generated out of the "development" artefact = Semantic Model defined in web based Semantic Modeler. So changing Log Level in RPD on running OAS instance (via online connection to BI Server from BI Admin Tool) does not influence your Semantic Model definition in any sense.

Szymon Grzęda

@Michal ZimaThanks, that helps a lot! However, I’ve noticed some compatibility issues between the Admin Tool and Semantic Modeler. We recently moved our repository over from Admin Tool to Semantic Modeler, and some components stopped working. Do you think it’s actually safe to keep switching back and forth between them?

Gianni Ceresa

Adding on Michal correct answer, you should not keep switching back and forth between the model admin tool and the semantic modeler. From a development point of view, pick one tool and stick to it for your development processes (as you said there are things that change, aren't imported, are modified when you go from one to the other).

In your case you now selected the Semantic Modeler as your development tool for the semantic model, stick to it.

That's why Michal correctly makes the point that after you deployed the model on your server, the semantic model deployed isn't "connected" anymore to your development model. Making a change to it with the model admin tool doesn't mean switching back and forth.