Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with result cache on 18c for logging by client id #87

Open
piotry opened this issue Jun 5, 2019 · 1 comment
Open

Problem with result cache on 18c for logging by client id #87

piotry opened this issue Jun 5, 2019 · 1 comment

Comments

@piotry
Copy link

piotry commented Jun 5, 2019

We got strange issue for 18c (Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production)

We created a functionality for user to be able to log on client_id in APEX application.

This way we can check stuff on prod systems.

But! :)

On 18c it is not working.
When one user is turning ON the logging only for his client id (USER:SESSION) it is turning this on for everybody.

Having a lot of logging in application we are not able to use it in there.

I was investigating and found out that this is happening when we got RESULT_CACHE in get_pref function. Removing that is making all good.

Also we got the same solution on 12c (Oracle Database 12c Standard Edition Release 12.2.0.1.0 - 64bit Production) and it works.

I checked in documentation what is different in result cache between those two. Nothing found ...

I can provide links to application where this can be changed.

@piotry
Copy link
Author

piotry commented Jun 5, 2019

Followup on this one :)
This list explains the difference between SE2 and EE:
http://bicarait.com/2016/12/06/1154/

Difference is that in SE2 result cache is not available hence it's not used.

I'll disable this in EE server for now.
But i think i would like to use result cache in EE for separate client id ones - how?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant