Re: Calling SQL*Loader from a Procedure

[Quoted] [Quoted] Thanks for the ideas--gives me something to work with. I'm just kind of surprised that there isn't a more elegant/efficient/automatic way of calling SQL*Loader from a package. I assume that users importing new data into a database is a regular occurence. Have you run across this issue, and how did you handle it?

Thanks again for your help!

Clyde Reed

>
> Can it be done?
> By writing an external procedure calling the C system function, yes.
> Is it desirable to block the client session because of Sql*loader? Not sure.
> I think you have several alternatives.
> 1 you set up a .cmd or .bat file that is processed by the Win2k at command
> or whatever is has replaced it. At is basically a batch facility. You keep
> the filename of the batch constant, however, a pl/sql procedure in the
> application, will rewrite the file, using utl_file everyday with a new
> sql*loader call. Should work like a charm, assuming you can use an O/S
> authenticated account in your Sql*loader call, otherwise you would have to
> giveaway the password.
> 2 Write a vbscript program calling the VBA functions in Excel/Access to open
> a .csv file and dump it in Oracle using ODBC.
>
> Hth
Received on Sat Jun 22 2002 - 22:14:14 CEST