-
Notifications
You must be signed in to change notification settings - Fork 13
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
Setting Isolation Level for Oracle DB in YAML files. #109
Comments
We were pointed at https://ibm.github.io/spm-performance-tuning/openshift/tune_jms_producer/tune_jms_producer/ on that internal Slack post. |
Ok, that link above solved the problem for us. Here is what we did:
|
The thing that does not feel quite right here is we changed the two yaml files, mentioned above, in place. Is there a way to make the required change in the overrides file? Regardless it works, so we are over the problem. Also changing isolation level does not seem like a "tuning" task. It would seems clearer if there was (also) reference to it in the runbook, in the 3rd party tools section for Oracle. |
In the April 2022 spm-kubernetes releases (v8 & v7) the WebSphere Liberty |
We have deployed Curam on AWS ROSA connecting to an Oracle DB. We are seeing isolation level errors in the producer pod logs when the server attempts to interact with the Oracle DB. This internal Slack post has some more detail on this.
When I search through the spm-kubernetes folder I see reference to isolationLevel="TRANSACTION_REPEATABLE_READ" in the configmap-dbconn.yaml file and the configmap-sessions.yaml file. This isolation level is only relevant if the database is DB2, as per this link.
Should we be overriding these occurrences of the isolationLevel configuration property? And if so how and where do we do that? Also what should we be setting this configuration property to for OracleDB?
The text was updated successfully, but these errors were encountered: