BI Publisher log level keeps changing

Adam Wickes

Hi all,

Got a weird issue in our 12c environment where BIP jobs utilising bursting are taking significantly longer to finish than in our 11g environment. (2 minutes vs 45 minutes).

From what I can see in my brief investigation, the logs are filling up a lot more in 12c than they do in 11g.
I've narrowed in down to the Oracle.XDO log level being set to (Trace: Fine) instead of (Notification: 1) which is what our 11g instance is set to.

The problem is that every time I change it to Notification:1 and then schedule a job, it changes it back to Trace: Fine.
I have ensured that I have set "Persist log level state....." to checked and have tried a number of different scenarios where I restart the entire app vs restarting just the biserver vs not restarting anything. Every time, it resets itself back to Trace.

Has anyone else seen this annoying issue before?

Thanks in advance,
Adam

FTisiot

Hi,

Where are you trying to change the loglevel?

It may be worth checking the value defined in EM, there is a note in oracle support which is about 11g but I believe it still applies to 12c

How to set Trace 32 Log levels for BI Publisher 11g (Doc ID 1459264.1)

Adam Wickes

Yeah that's exactly where i've been changing it.
Turns out a colleague of mine had turned xdodebug on and had forgotten to remove it.
After deleting that, i'm able to change log levels appropriately.