Re: Duplicate transaction

sfama wrote:
> Yes,
> cause may happen that one or more clients not developed from me, start
> trasactions and set XIDs.
>
> We'd like to prevent that two clients set the same XID; I made some
> test and Oracle stops the transaction if one XID has just been used.
>
> We tried to set another transaction code: if we receive a request to
> start a transaction and a XID from the client, we set another
> trasaction code. This goes well. But if something wrong happens and a
> transaction was not completed, we lost the transaction code, but we
> have the XID (I don't know if I'm clear). So we'd like not to use the
> transaction code and use only th XID, but to avoid to have duplicate
> XID from different client, or if this happens, that Oracle manages it.
>
> About the manual, I'm giving a look at this!
> Thanks!
>
> Brian Peasland ha scritto:
>

>> sfama wrote:
>>> Yes, it could be a good solution,
>>> but if it couldn't be possible for me, is there a way to solve this
>>> problem or to have a workaroud?
>> The workaround is to not state a transaction identifier. Do you have a
>> specific need to do so? If you must state a transaction identifier, why
>> must you do that? If you do not need to, don't as it can cause you
>> problems. Did you read the concepts manual pertaining to transactions?
>>
>> HTH,
>> Brian
>>
>> --
>> ===================================================================
>>
>> Brian Peasland
>> dba_at_nospam.peasland.net
>> http://www.peasland.net
>>
>> Remove the "nospam." from the email address to email me.
>>
>>
>> "I can give it to you cheap, quick, and good.
>> Now pick two out of the three" - Unknown

Please stop top posting. Thank you.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org