Setting Isolation Level for Oracle DB in YAML files.

[podgek]

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?

[podgek]

We were pointed at https://ibm.github.io/spm-performance-tuning/openshift/tune_jms_producer/tune_jms_producer/ on that internal Slack post.

[podgek]

Ok, that link above solved the problem for us. Here is what we did:

1. Replace TRANSACTION_REPEATABLE_READ with TRANSACTION_READ_COMMITTED in both the files:
   helm-charts/apps/templates/configmaps/configmap-dbconn.yaml and
   helm-charts/apps/templates/configmaps/configmap-sessions.yaml
2. helm uninstall release1
   helm dependency update apps
   helm push -f apps local-development
   helm dependency update spm
   helm push -f spm local-development
   helm repo update
   helm install release1 local-development/spm -f ~/Downloads/values-aws.yaml --timeout "15m0s" --debug

[podgek]

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.

[wwwild]

In the April 2022 spm-kubernetes releases (v8 & v7) the WebSphere Liberty isolationLevel setting has been removed from the database and session dataSource definitions so that Liberty will select the default appropriate to the database type. Similarly, the related information in the Tuning Guide has been removed in its corresponding release.