Bug 8425

GemStone/S

6.7, 6.6.5, 6.6.4, 6.6.3.3, 6.6.3.2, 6.6.3, 6.6.2, 6.6.1, 6.6, 6.5.8, 6.5.7.5, 6.5.7, 6.5.6, 6.5.5, 6.5.4, 6.5.2, 6.5.1, 6.5, 6.3.1, 6.3, 6.2.x, 6.2, 6.1.6, 6.1.5, 6.1.x, 6.0.x, 5.1.5.1, 5.1.5, earlier versions

All

Read lock on temporary object prevents a commit from making it permanent

A read lock on a temporary object prevents a commit from making
the locked object permanent because making the object permanent
is equivalent to writing the locked object.  The session must
write lock the object if it wants to lock it and modify it.

Workaround

Write lock any objects that you want to modify.  Alternatively,
you can release the read lock on objects you want to make permanent
and then commit.


Last updated: