Oracle Forms (MOSC)

MOSC Banner

Reduce locking in database

edited Apr 19, 2017 10:20AM in Oracle Forms (MOSC) 3 commentsAnswered ✓

I'm a DBA managing a database with Forms connections. I see many SQLs updating primary keys e.g.

UPDATE APPTABLE SET ID=:1,NAME=:2,...

The developer would never add the code to "change" the value of PK column ID. It seems that if one column is updated, Forms adds all columns to the set-list. Is there a way to avoid that? Ideally, I'd like to have some Forms server config parameter to suppress this behavior. If not, code change is fine. If neither, we'll diligently index all unindexed foreign keys to reduce locking.

Also, some queries are appended with FOR UPDATE, not added by the developer. How do we avoid that? Thanks.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center