Re: HELP: How do I run batch programs with Oracle

In article <4apoml$8si_at_usenet.hydro.on.ca>, Jerry French <jerry.french_at_hydro.on.ca> wrote:

You can also put your username and password in a parfile and run loader with the following command:

sqlldr control=filname.ctl parfile=logon.par

where parfile looks like:

userid=username/password
silent=feedback

Make sure the your parfile is set so nobody else can read it.

> si002_at_seqeb.gov.au (Simon Inglis) wrote:
> >
> >Greetings all,
> > I have a simple problem. I need to run some Oracle unix software as
> >part of a batch load of an Oracle datbase. To load the database I need to
> >run SQL*LOADER. My problem is this: How can I run SQL*LOADER from a shell
> >script (cshell) so that my username/password does not appear when an user
> >does a "ps -ef"?
> >
> >My only solution so far is to pipe my username/password to the oracle
> >tools. Eg for sqlplus:
> >
> >-----start of shell script----------
> >echo "$MY_PASSWORD \
> >$1 $2 $3 $4 $5" | sqlplus -s
> >------end of shell script-----------
> >
> >Is there a more elegant solution?
> >_________________________________________________________________________
> >Simon Inglis
> >bss_simoni_at_seqeb.gov.au
> >singlis_at_gucis.cit.gu.edu.au
> >_________________________________________________________________________
> >
>
> ************************************************************************
> Hello Simon and world,
>
> Here are some simple lo-tech methods to protect Oracle and other package
> passwords in batch jobs, etc.
> These examples apply to most UNIX systems and shells (examples tested
> with sh and ksh on HP-UX (test with other shells as needed). Other
> languages/shells such as Perl, Tcl, Python, etc can also be used.
> ----------------------------------------------------------------------
>
> 1. HERE FILE method
>
> ***************************
> sqlplus -s <<!!
> `cat $password_file`
> sql_stuff
 

-- 
Dave Erwin
Lockheed Martin Missiles & Space
Email: derwin_at_lmsc.lockheed.com

The opinions expressed are those of the author and not necessarily those of
the Lockheed Martin Corporation.