Re: Oracle behaving strangely with multiple commands executing in a tight loop
- From: Steve Eichert <eichert12@xxxxxxxxxxx>
- Date: Tue, 18 Jul 2006 17:56:31 +0000 (UTC)
Oracle uses MVCC, which is a concurrency scheme within a
transaction: if a transaction with DML statements is executed, the
transaction can manipulate data without affecting other threads. This
means that another command issued could be executed in parallel with
the insert and it won't see the inserted data until that transaction
is completed.
On SqlServer, the update statement will block till the insert has
been completed.
Do you execute the insert and update in a single transaction? If not,
could you try to run it in a single transaction?
The issue that we're seeing isn't really a problem with the INSERT INTO and UPDATE that is executed right after it. At least it doesn't seem to be. We have a bunch of validations that are doing an INSERT INTO followed by the update, it appears that they are stepping on one another which is resulting in data not being inserted and rows not being updated. Would we have to execute all commands within a single transaction, or just each individual INSERT INTO/UPDATE combo?
Thanks,
Steve
.
- Follow-Ups:
- Re: Oracle behaving strangely with multiple commands executing in a tight loop
- From: Frans Bouma [C# MVP]
- Re: Oracle behaving strangely with multiple commands executing in a tight loop
- Prev by Date: Re: Copy all records from access MDB to others via ADONET
- Next by Date: Invalid cast on SqlConnection.open
- Previous by thread: Re: Can't seem to speed up Rows.Add in DataTable
- Next by thread: Re: Oracle behaving strangely with multiple commands executing in a tight loop
- Index(es):
Relevant Pages
|
|
