After we post updated features to Oracle Spatial, the features are typically unlocked. Recently, we've seen that changed features are not always unlocked afterwards.
Is there a setting for this that we could have changed on accident?
-Rob
Rob,
Are you using "short transactions" (e.g. no Oracle Workspace Manager version)? If so, the lock being applied in Oracle is being done using SELECT FOR UPDATE approach. Are you seeing the locks persist after a session exit or connection close, or when?
Regards,
Jeff Bielefeld [Bentley]
Here's the scenario:
1. Query data from Oracle
2. Lock elements
3. Edit an element
4. Post
At this point, we would expect Map to prevent us from editing the just-posted feature. Our typical experience has been that it unlocks after posting. What we're actually seeing is that we can still edit the feature without re-locking.
This has only been observed on 2 of our installs. It's not a huge problem, we're just trying to figure out what's causing the different behavior.
I've not heard of that particular scenario, and you're correct, after the post operation the feature instances should be locked once again, preventing modification in the local design file cache. What version of Bentley Map are you using?
That's not quite clear Jeff :-) Once posted the features should be unlocked in the database, so they are read-only (uneditable, which you called "locked", in the dgn file)...
An additional note: are you getting post errors ? Whatever doesn't post will stay locked (in the database). This will either fail the whole posting, or only the error features if "partial posting" is on.
Hope this helps,
Martin
...correct, the "locked once again" reference was to the design file feature instances.