Re: Is transaction ID unique for the life of a DB?

yong321_at_yahoo.com (Yong Huang) wrote in message > > Forget about "lifetime". If the database executes 20*(max sequence
> > value) of transactions a day or an hour, I would bet transaction IDs
> > will recycle. And I think ORACLE uses the "CYCLE" clause for the
> > sequence so no error will be generated when the sequence hits the max
> > and recycle.
>
> I found David's question on Metalink he posted at the same time as he
> posted to this newsgroup. For the benefit of all newsgroup readers,
> it's http://metalink.oracle.com/metalink/plsql/ml2_documents.showFOR?p_id=336635.995&p_showHeader=1&p_showHelp=1
>

Feels like I just opened a can of worms. I am surprised that ORACLE would not allow the sequence the recycle when it maxs out and you actually have to drop and recreate that particular rollback segment.

> BTW, why do you say Oracle is *not* keeping track of XIDs? It keeps
> track of that as well as SCNs.

That was a guess. I fail to see why ORACLE would want to keep track of "committed" or "rollbacked" transaction IDs. Any thoughts, DOCs or links on this you care to share?

• Jusung yang