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

[Cantor, Scott]

On 9/13/17, 9:39 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

> "idp.persistentId.computed" is a setting that allows the database-backed generator to produce the initial generation of values 
> using the same hashing that the other generator would use if there weren't a database. If you started with it commented out,
> you cannot have done this, and so you have produced random values stored in the database that are NOT compatible with the
> hash-based approach and you would break any application that was already depending on them.

Actually, I think that's not true. I believe it defaults internally to using that approach if the property is commented, which is not what I remembered, but that's what it's doing. I would simply look at the database, it's pretty wasy to see if the values are random short strings or longer base64 encoded data. But I suspect they'll be the latter, assuming you had a salt set.

As long as none of the values look like they were just randomized, switching to the computed bean would be a no-op for applications.

-- Scott