URGENT :: kill rollng back process? or atleast the status to get the time estimated..

[technocrat]

i have a process thats in roll back state..i ts going on forever..i
need to kill it and would like to restart it with some changes....

if not atleast i need to know the status of the rollback to estimate
how longer it migt take...no use with this..but just for my info....

killing roll back process would be ideall...if not recommended what are
the risks that might come up due to rollback...becuase i badly need to
kill this and start all over again..i dont ahve miuch time...

APPRECIATE A VERY QUICK RESPONSE..
THNKS..

[Serge Rielau]

technocrat wrote:

i have a process thats in roll back state..i ts going on forever..i
need to kill it and would like to restart it with some changes....

if not atleast i need to know the status of the rollback to estimate
how longer it migt take...no use with this..but just for my info....

killing roll back process would be ideall...if not recommended what are
the risks that might come up due to rollback...becuase i badly need to
kill this and start all over again..i dont ahve miuch time...

If you rollback the rollback it may take longer than completing....
Depends on how far it got so far.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/

[technocrat]

roll back a roll back in the sense? and how cani know how far it
wnt..? is there any tool that tells me that?//?

first of all is it poss to kill a process thats in roll back state??
Serge Rielau wrote:

technocrat wrote:

i have a process thats in roll back state..i ts going on forever..i
need to kill it and would like to restart it with some changes....

if not atleast i need to know the status of the rollback to estimate
how longer it migt take...no use with this..but just for my info....

killing roll back process would be ideall...if not recommended what are
the risks that might come up due to rollback...becuase i badly need to
kill this and start all over again..i dont ahve miuch time...

If you rollback the rollback it may take longer than completing....
Depends on how far it got so far.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/

[Serge Rielau]

technocrat wrote:

roll back a roll back in the sense? and how cani know how far it
wnt..? is there any tool that tells me that?//?

first of all is it poss to kill a process thats in roll back state??

I don't know. And quite frankly before I'd do that I'd have a chat with
support.

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/

[Knut Stolze]

Serge Rielau wrote:

technocrat wrote:

roll back a roll back in the sense? and how cani know how far it
wnt..? is there any tool that tells me that?//?

first of all is it poss to kill a process thats in roll back state??

I don't know. And quite frankly before I'd do that I'd have a chat with
support.

I'm pretty sure that you can kill the process. My guess at what will/should
be happening is this:
(1) DB2 notices that the process is gone and shuts down the complete engine.
(2) Once the instance is restarted, Crash Recovery kicks in, finds the log
records for the rollback and continues with the rollback until it is done.
(3) If no log records are found, we still have an in-flight transaction,
which is rolled back as well after the restart.

At least that is how recovery works.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

[Gert van der Kooij]

In article <e7**********@lc03.rz.uni-jena.de>, st****@de.ibm.com says...

Serge Rielau wrote:

technocrat wrote:

roll back a roll back in the sense? and how cani know how far it
wnt..? is there any tool that tells me that?//?

first of all is it poss to kill a process thats in roll back state??

I don't know. And quite frankly before I'd do that I'd have a chat with
support.

I'm pretty sure that you can kill the process. My guess at what will/should
be happening is this:
(1) DB2 notices that the process is gone and shuts down the complete engine.
(2) Once the instance is restarted, Crash Recovery kicks in, finds the log
records for the rollback and continues with the rollback until it is done.
(3) If no log records are found, we still have an in-flight transaction,
which is rolled back as well after the restart.

At least that is how recovery works.

I do remember from the early days (DB2 2.1.2) that the Crash Recovery
could last for 'ages' compared to the 'normal' recovery process because
it did use a small default buffer pool. I guess this proces has been
optimized since then.

But I won't expect the Crash Recovery to be faster then the normal
rollback process so why would the OP cancel the rollback and use the
Crash Recovery to rollback all updates?

[technocrat]

some how things worked.....aftrer a marathon 48 hr no sleep
weekend....the DBA bounced the machine when the roll back is going
on....it stukc there for sometime and then when it came up after an
hour it started some recovery phase which eventually lasted for another
1.5 hrs..so a total of 5 hrs of rollback and 2.5 hrs of recovery...-
7.5 hrs...that was 8 am in the morning it was up again

Same thing happened again at 1030 am (transaction logs were fiull again
)but we somehow managed to avoid the rollback by bouncing it befdore it
goes into rollback state and it came up and recovery stage started
again and ended at around 4 hrs from 1030 ie 2 pm....so finally DB was
up at 2PM to run the transactions with some changes that would avoid
the logs to be fullagin and at 430 finally things were
done....fortunately 1 hrs before the UAT begain....and that saved my
job..:D

It was literally a nightmare...
Thanks all of you for the support!
Gert van der Kooij wrote:

In article <e7**********@lc03.rz.uni-jena.de>, st****@de.ibm.com says...

Serge Rielau wrote:

technocrat wrote:
> roll back a roll back in the sense? and how cani know how far it
> wnt..? is there any tool that tells me that?//?
>
> first of all is it poss to kill a process thats in roll back state??
I don't know. And quite frankly before I'd do that I'd have a chat with
support.

I'm pretty sure that you can kill the process. My guess at what will/should
be happening is this:
(1) DB2 notices that the process is gone and shuts down the complete engine.
(2) Once the instance is restarted, Crash Recovery kicks in, finds the log
records for the rollback and continues with the rollback until it is done.
(3) If no log records are found, we still have an in-flight transaction,
which is rolled back as well after the restart.

At least that is how recovery works.

I do remember from the early days (DB2 2.1.2) that the Crash Recovery
could last for 'ages' compared to the 'normal' recovery process because
it did use a small default buffer pool. I guess this proces has been
optimized since then.

But I won't expect the Crash Recovery to be faster then the normal
rollback process so why would the OP cancel the rollback and use the
Crash Recovery to rollback all updates?