Re: Best approach to retrieve Connect String

Wes Brooks wrote:
> Hello expert,
>
> My environment has 10 Oracle databases. The job is run called up by
> UNIX script. The job may need to sign on with different User IDs to
> different Oracle database instance in order to get the batch job
> running. To avoid to logon with a wrong database instance, the
> current practice is to hard-code the logon ID, password, and the
> Connect String on the UNIX script.
>
> If I want to remove the hard-code of the logon information, would you
> mind to share your experience how to handle this change? How to set
> up the UNIX User environment based on the job?

I agree with Hans but also suggest you explore the possibility of using externally authenticated accounts such as OPS$DEV, OPS$TEST, OPS$PROD1.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)