"No Log Found" error while viewing logs in Manage Sessions

Community DW Integration

Hi,

OBIEE 11.1.1.7.160119

I am struggling with a strange issue.  We have 5 OBI instances.  In 2 instances, I am getting this "No Log Found" error message when I try to view log for an OBIEE report via Administration -> Manage Sessions -> View Log.  I am able to view the log in remaining 3 OBI instances.  All these instances have been setup the same way (as far as I know) for approx 2 years now.  While checking the performance for a report, we noticed this strange behavior.

So I compared all the 5 instances and all the below settings are consistent across all the instances.

Repository - Logging level is set to 0.  I see lot of links suggesting to set this to 2 minimum.  I have no idea why it is working for us in certain instances.

Enterprise Manager - FMC - logging level is set to Info.

List of values for Log Level

If I set the log level for individual report by adding the below text to the report -> Advanced Tab -> Prefix text box, I can view the log.

SET VARIABLE LOGLEVEL=2,DISABLE_CACHE_HIT=1;

Since all the settings are same across all the instances and it is working for some and not for others is more confusing/bothering.  How can I go about troubleshooting this issue?

Thanks in advance.

Sherry George

What about user level logging in all the environments, is there anything specifically set?

Syedsalmancs110

Could you also check below points:

1. Open repository RPD in online mode in BI Administrator as the Administrator user.
   
   
2. Then choose -> Manage -> Identity Manager-> Locate if User exists here -> Check out individual user and check there log level.
   
   
3. Then choose Manage -> Variables -> Expand Session Variables -> Locate variable called LOGLEVEL -> Check what value is set here.
   
   

[Deleted User]

skull wrote:Repository - Logging level is set to 0

^--- This is why there's no query logs

skull wrote:I have no idea why it is working for us in certain instances....SET VARIABLE LOGLEVEL=2,

^--- This is why you have some logs.

So you have an inconsistent setup. With only some explicit analyses logging their stuff. Logging to 0 is a bad idea. No troubleshooting, no possibility to see what has happened.  Set it to minimum 2 for everything.

Also: If someone tells you "logging costs performance" .... basically get rid of that person. They don't know what they're talking about