Re: Oracle behaving strangely with multiple commands executing in a tight loop
- From: Steve Eichert <steve.eichert@xxxxxxxxx>
- Date: Thu, 20 Jul 2006 17:37:30 +0000 (UTC)
As soon as you don't group statements in 1 transaction, Oracle CAN
(but doesn't have to) schedule the queries to be executed in parallel.
I have no hard evidence that it doesn't happen as well inside a
transaction but it seems unlikely due to the uncommitted data only
reachable from the transaction participating connection.
FB
We ended up figuring this out. As you may have suspected it wasn't an issue with the commands stepping on each other but a matter of the import process running in parrallel with the validations. Setting the breakpoint made it so the complete import finished before the validations. Setting up the process to ensure the bulk import completes before running the validations resolved our issue.
Moral of the story: Assume it's your code that is messed up not somebody else's :)
Thanks for the help!
Cheers,
Steve
.
- References:
- 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: passa dataset through class
- Next by Date: Oracle Stored Procedure
- Previous by thread: Re: Oracle behaving strangely with multiple commands executing in a tight loop
- Next by thread: Invalid cast on SqlConnection.open
- Index(es):