Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Wed, 14 Sep 2005 @ 09:40:54 GMT


     
  <Prev Next>  
<<First
<Prev
Next> Last>>  


Subj:   ABORTED SESSION TAKES TOO LONG TO ABORT
 
From:   MOHAN WAGH

Dear TeraData Forum Member,

     Platform:-
     -----------
     TeraData Version
     ----------------
     RELEASE V2R.05.00.00.44
     VERSION 05.00.00.38
     Operating System
     ----------------
     NCR MP-RAS SVR4 UNIX

Scenario:-
----------

In one of my test databases I have a table with 3Gb of data. Using BTEQ-Windows GUI(session transactions in 'btet' mode) I was executing the following DML statement...

     ---------------------------------------------
     BT;
     DELETE FROM . ALL;
     ET;
     ---------------------------------------------

The deletion went on for more than 30 minutes and midway to the deletion my computer went into the Hang-mode and all activities on my machine got suspended, so I had to re-start my machine. Due to the reboot of my machine obviously the BTEQ session, which was executing the DML, got ABORTED.

When I checked the BTEQ-session status through the Performance Monitor, my Aborted BTEQ session status was shown as 'ABORTING'... And even after 16 hours, the session status is still showing as 'ABORTING'. There is a 'WRITE' LOCK on the table which was getting deleted and I am unable to release that lock or carry out any DDL or DML (except SELECT after ACCESS Mode Locking) on the locked table.

After 16 hours... I tried the following...

1> Using the "xgtwglobal" utility I KILLED the SESSION which was executing the DELETE statement.

In "qrysessn" The status for that KILLED session is "QUIESCED ABORT WITH LOGOFF"

In "xgtwglobal" the session is shown as KILLED.


2> Using the "xgtwglobal" utility I KILLED the USER under whom the session was executing the DELETE statement.

Still the status is...

In "xgtwglobal" the session is shown as KILLED.

In "qrysessn" The status for that KILLED session is "QUIESCED ABORT WITH LOGOFF".

In "qrysessn"


3> Using "xgtwglobal" and "DI SE <Session Number>" command, following is the output

     State              Event       Action     Partition
     ------------------ ----------- ---------- ---------
     CS_KILLWAITRSP     CE_KILL     CA_NOP     DBC/SQL

Question:-
----------

1>The table which I was deleting records from, Now I want to DROP that table. How to DROP that table?

2> Even after 16 hours, Why the session is still in ABORTING mode, when the data volumne is only 3GB?

Please help, This Rollback of data issue is a real twister everytime I face the issue of aborted session with large data.

Please help,


Thanking you,

regards,

Mohan Wagh.



     
  <Prev Next>  
<<First
<Prev
Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 27 Dec 2016