Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> killing sql*loader

killing sql*loader

From: Lisa M. Lewis <lmg_at_isdsa.pgh.wec.com>
Date: 1997/06/18
Message-ID: <33A87C32.625EE0A4@isdsa.pgh.wec.com>#1/1

I was running sql*loader in direct mode, unrecoverable and I decided to kill the sql*loader job because I realized I needed to modify the data file I was loading. I didn't care about the state of the table I was trying to load into because I could just reload it. After I killed the sql*loader job, I tried to truncate the table that I was trying to load in order to start the whole process again. I got an error saying that the resource was busy -- it took quite a while before the resource freed up so that I could truncate the table. Oracle was churning doing something. What was it doing? Since I used UNRECOVERABLE in my control file I thought if I killed sql*loader while it was doing the direct load, I would regain control of that table very quickly. Can anyone set me straight on what is actually going on or what I should be doing instead?

Thanks!!

Lisa Received on Wed Jun 18 1997 - 00:00:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US