![](//teradataforum.com/imgs/ptdfw1.gif) |
![](//teradataforum.com/imgs/ptdfw2.gif) |
Archives of the TeradataForum
Message Posted: Thu, 20 Jul 2000 @ 11:23:32 GMT
Subj: | | Sessions cannot be killed |
|
From: | | Julie Sorrell |
I backed up a database a couple of days ago, using ARCMAIN on our TNT system. The job finished with a Dr Watson error (which ARCMAIN
seems quite prone to at the moment), but seemed successful, ie all the tables in the database were backed up. However, 3 of the 8 dbc
sessions were not closed after the backup - probably because of the Dr Watson error. All 3 dbc sessions were marked as idle, so I used
gtwglobal to kill these 3 sessions yesterday. But, a day later, they still haven't died! I am considering doing a tpareset, which should
kill these sessions, but I'd rather kill them without having to restart Teradata.
Has anyone else had problems with ARCMAIN on TNT V2R3 of this type? We have tried using ARCMAIN 06.04.01 and 06.05.00, but both display
the problem. Does anyone know why the dbc sessions aren't dying - I would assume that if you kill an idle session, it should disappear
pretty quickly?
TIA,
--
Julie Sorrell
| |