[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DEC Rdb against the World |
|
Moderator: | HERON::GODFRIND |
|
Created: | Fri Jun 12 1987 |
Last Modified: | Thu Feb 23 1995 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 1348 |
Total number of notes: | 5438 |
679.0. "Oracle Locking" by VANISH::BROOMFIELD () Tue Jun 26 1990 12:42
Can somebody please clarify my understanding of Oracle's (V5) locking strategy?
Oracle staff talk about row level locks taken out on insert/update, but from
what I've read in this conference it would appear that this may not quite
be the case. I seem to remember a lock being taken on a dummy table to prevent
simultaneous commits, but other than that.....
1. Does V5 lock at the table, page or row level?
2. How does V5 handle situations that Rdb returns as deadlocks? (i.e.
contention for locks in an index)
3. How well does V5 support multiple updaters? (i.e. can an insert by one
user lock the whole index)
4. Can a read transaction be blocked by a write transaction?
5. Does Oracle's V5 locking strategy give rise to any problems with applications
developed in their 4GL tools, SQL*Forms and SQL*Reportwriter?
Thanks for any info.
T.R | Title | User | Personal Name | Date | Lines
|
---|