Re: No rollback

astalavista wrote:
>> Here is a short example that may explain what you are seeing:
>> Create a simple table:
>> CREATE TABLE T1 (MY_DATE DATE);
>>
>> Table created.
>>
>> Activate a 10046 trace for the session:
>> ALTER SESSION SET EVENTS '10046 TRACE NAME CONTEXT FOREVER, LEVEL 8';
>>
>> Insert 99,999 rows into the table.
>> INSERT INTO
>> T1
>> SELECT
>> TRUNC(SYSDATE)+ROWNUM
>> FROM
>> DUAL
>> CONNECT BY
>> LEVEL<100000;
>>
>> 99999 rows created.
>>
>> Close SQL*Plus:
>> EXIT
>>
>> Disconnected from Oracle Database 10g Release 10.2.0.2.0 - 64bit
>> Production
>>
>> (Reconnect to Oracle)
>>
>> Let's see how many rows are in the table:
>> SELECT
>> COUNT(*)
>> FROM
>> T1;
>>
>> COUNT(*)
>> ----------
>> 99999
>>
>> Taking a look at the last two lines of the 10046 trace file:
>> WAIT #0: nam='SQL*Net message from client' ela= 5831875 driver
>> id=1413697536 #bytes=1 p3=0 obj#=-1 tim=2429307593
>> XCTEND rlbk=0, rd_only=0
>>
>> The last line indicates that a COMMIT was performed automatically when
>> SQL*Plus closed. This is the default behavior for SQL*Plus.
>>
>> Charles Hooper
>> IT Manager/Oracle DBA
>> K&M Machine-Fabricating, Inc.

> 
> 
> I understand that if there is an exit, a commit is done
> but the session was killed ...

You are without a doubt incorrect about some aspect of what you are saying and we are trying to help you.

How was it killed?
Describe in detail the method?
Did you use kill -9? Did you use orakill.exe? Did you use alter system kill session?

And how did you verify the kill? And to that there is only one right answer ... SELECT ... FROM [g]v$session.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org