Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Duplicate transaction

Re: Duplicate transaction

From: sfama <silvia.fama_at_googlemail.com>
Date: 13 Jul 2006 00:53:04 -0700
Message-ID: <1152777184.479427.4820@b28g2000cwb.googlegroups.com>

sfama ha scritto:

> 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

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! Received on Thu Jul 13 2006 - 02:53:04 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US