Re: Calling SQL*Loader from a Procedure

I do this using sql loader and the windows task scheduler for our remote access logs which I load to an analytical database. Is this appropriate or does the load *have* to be interactive?

--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer

******************************************
"Charlie Edwards" <Charlie3101_at_hotmail.com> wrote in message
news:db479d88.0206250449.4d803f6a_at_posting.google.com...


> flyinghigh1962_at_yahoo.com (Clyde) wrote in message

news:<bf477768.0206212303.6dbe8bb6_at_posting.google.com>...


> > I'm creating an application(9i on W2000) where the user will need the

> > ability to hit a button and load data from a .csv file in a given


> > directory into the database.  There would be a new file on a daily

> > basis the user would need to load.  My original assumption was to use

> > SQL*Loader to move the data, but I'm having difficulty finding

> > examples of how it can be called from a procedure.  I'm familiar with

> > SQL*Loader, and writing packages and procedures, but haven't had the

> > need to put the two together until now.  I'd rather not get into Pro*C

> > if I can help it.  Is there a simple way to call SQL*Loader from a

> > procedure such as using DBMS_JOB, or some other Oracle supplied

> > package?  I believe all I would need to do would be to send a command,

> > or a string, to the DOS prompt to kick off the SQL*Loader.

> >

> > If I can't do this, what are my other options to load this data?  Each

> > of these files will probably be about 6M-10M.

> >

> > All ideas, suggestions, and direction greatly appreciated!

> >

> > Clyde Reed

>

> Have you considered using UTL_FILE?  Might be ok if you're not talking

> about much data.

>

> CE