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?

How much 'UNIX' stuff are you actually doing? If the batch jobs are entirely (or primarily) in the databases, you might consider using DBMS_JOBS to run the jobs from inside the databases. That behaves a lot like cron, adopting the submitting userid & permissions.

The relevant docco - although DBMS_JOB's been around for a while I like Oracle9i R2's Supplied PLSQL Packages description for this doc.

/Hans Received on Sat Aug 14 2004 - 23:09:23 CDT