Tuesday, August 5, 2025

ORA-08177 Oracle RDBMS & Spring Batch framework

 Dear Readers,

Migration from Oracle RAC to Standalone database resulted in ORA-08177 error with few batch processes.


ORA-08177: can't serialize access for this transaction


The uniqueness amongst the batches are they are all written using spring batch frame work.

I saw the data model of the frame work on the db and I can confirm they are spring batch.

It had all the tables as mentioned in the below screenshot. The same can be found here



The reason for the error is even documented in the spring batch framework document here.



But one would wonder why such error message may come...

1. Since it is the same serialization in both standalone and rac db. But why standalone alone affected vs RAC no impact for several years.

2. No concurrent transactions were run on the db

This is where oracle on the SR I submitted confirmed that oracle RAC's multi cache gc related events handles the serialization transaction much better than oracle standalone's single cache.

So a pure technology change resulted in such behaviour.

This happened only with spring batch, other java programs behaved same.


Thanks



No comments:

Post a Comment

Troubleshooting the “Cannot Generate SSPI Context” Error After SQL Server Migration

  Introduction After a recent  SQL Server migration from 2012 to 2022 , our team encountered a classic authentication issue: The target prin...