Open prasanthks81 opened 5 days ago
Friendly reminder - Could you please provide an update on this?
Indeed, the issue should be resolved if you lower the transaction's isolation level.
However, the following is incorrect:
spring.batch.jdbc.isolation-level-for-create=READ_COMMITTED
spring.datasource.hikari.transaction-isolation=TRANSACTION_READ_COMMITTED
It should be:
spring.batch.jdbc.isolation-level-for-create=ISOLATION_READ_COMMITTED
spring.datasource.hikari.transaction-isolation=ISOLATION_READ_COMMITTED
There is a sample in the docs here: https://docs.spring.io/spring-batch/reference/job/configuring-repository.html#txConfigForJobRepository
Have you tried that?
Getting below ORA-08177 issue when multiple Spring batch jobs are triggered at the same time.
Property already added to set the Transaction isolation level as READ_COMMITTED
Versions used