At 09:19 PM 24/02/2003 -0500, you wrote:

>Helen,
>
>Wow, that was fast... :)
>
>Anyway, the issue I am having is that, on occasion when several threads
>are writing to the database at once, I will get a message that says:
>
>"Connection to server not defined..." and then something about a "no
>wait" transaction. I don't have the error message available, so I am
>paraphrasing. It's very hard to duplicate this error and it's driving me
>nuts.
>
>As far as I can tell, it appears that one of the threads is not able to
>either read or write to the database while one of the other threads are
>writing, but I am having a devil of a time isolating the thread(s) that
>are involved. I am running all of the threads using "Read Committed",
>however, there are two threads that have a query that opens with a
>"Request Live" setting to insert a blob. I believe that this is probably
>where the problem is, but I am not sure.
>
>If you need more information, I'll try to capture the error and repost.

The info so far doesn't tell me what's going on but it does seem you have
two different errors here. More questions...
What's the client environment? Is it capable of totally isolating each
connection from all of the others?
What does your environment expect to do with a "Request Live" when
performing DML? Request Live seems to be an attribute that would be
applied to a SELECT statement, not an INSERT...
If you are using Read Committed transaction isolation in all of the
threads, how are you covering possible dependencies that would require
updates (as distinct from inserts) to be handled serially? This is a bit
of a wasp's nest and it might not be an issue...can't tell from the info
provided.

heLen