Hi,
Have you tried :
SELECT SYSLIB.AbortSessions(1,'your_user',0,'Y','Y');
Cheers,
Raja
Raja K Thaw
My wiki: http://en.wikipedia.org/wiki/User:Kt_raj1
Street Children suffer not by their fault. We can help them if we want.
Hi Noel,
If you have found a solution for this, then please kindly share.
The documentation says that it is not allowed.
Regards,
Vlad.
Hi Noel,
Just to add : I am curious if it is hard RI or soft RI too(it can be strange with data volume), can you please share this info for me .
Vlad,
If you dont mind, can you please share the document you refer to my mail id : ktraj1@gmail.com.
Thanks and regards,
Raja
Raja K Thaw
My wiki: http://en.wikipedia.org/wiki/User:Kt_raj1
Street Children suffer not by their fault. We can help them if we want.
Hi Raja,
I've seen it here: http://www.info.teradata.com/HTMLPubs/DB_TTU_14_00/index.html#page/Utilities/B035_1102_111A/RecoveryMgr.51.23.html
With kind regards,
Vlad.
Hi,
I used to kill jobs, either from Linux, unix prod as a last resort. It's usually fine. Of course, with other DBs, the index becomes unusabe or invalid most of the time.
Thank you very much for the link Vlad.
Cheers,
Raja
Raja K Thaw
My wiki: http://en.wikipedia.org/wiki/User:Kt_raj1
Street Children suffer not by their fault. We can help them if we want.
We attempted a large load on an empty table that was highly ineficient and had to abort the session after hours of running.
Now the rollback has been running for over 24hrs and is still locking the target table.
We tried Recovery Mananager with the "cancel rollback on table" command but gave us the "has referential integrity constraint" error.
We also tried to restart the database but the lock still persits.
Since the table was empty, we are fine in somehow dropping it forcefully but I'm not aware of a way that would help us do that.
Can someone provide me with some options?
Thanks,
Noel