: Re: Serial# changes when rolling back
Past experience with this problem seems to indicate that you might
be mistaken in that. Though the serial # may increment, I've never
seen another session take the SID until the session holding it is
completely gone.
This should be fairly easy
Title: Serial# changes when rolling back
Jared,Deepak
I did not see a reply on this. From a brief experiment I don't see the serial# changing when rolling back a transaction.
The code posted by Jared certainly works as the number of blocks to rollback reduces as the job nears completion
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc: (bcc: CHITALE Hemant Krishnarao/Prin DBA/CSM/ST Group)
Subject: Serial# changes when rolling back
Krishnarao/Prin DBA/CSM/ST Group)
Subject: Serial# changes when rolling
back
)
Subject: Re: Serial# changes when rolling back
]
cc: (bcc: CHITALE Hemant
Krishnarao/Prin DBA/CSM/ST Group)
Subject: Re: Serial# changes when
rolling back
: CHITALE Hemant Krishnarao/Prin DBA/CSM/ST
Group) Subject: Re: Serial# changes when rolling back
yeah i did read this thread but still wonder why
oracle needs to use serial# column at all. Does the
SID not gaurentee uniqueness for a session ... damn
the name says so atleast (session
