Re: login.sql equivalent for RMAN
- From: Joey D'Antoni <jdanton1@xxxxxxxxx>
- To: Oracle-L Freelists <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 30 Apr 2009 10:06:55 -0700 (PDT)
Why not just setup O/S authentication for the Oracle (or other if needed) user?
That way you don't need to pass a password to the database.
I know this is dependent on how many others you share your Oracle o/s password
with for security, but it does make scripting easier.
________________________________
From: Jared Still <jkstill@xxxxxxxxx>
To: William Wagman <wjwagman@xxxxxxxxxxx>
Cc: Niall Litchfield <niall.litchfield@xxxxxxxxx>; Oracle-L Freelists
<oracle-l@xxxxxxxxxxxxx>
Sent: Thursday, April 30, 2009 12:58:35 PM
Subject: Re: login.sql equivalent for RMAN
On Thu, Apr 30, 2009 at 8:44 AM, William Wagman <wjwagman@xxxxxxxxxxx> wrote:
The problem is not so much platform as much as wanting to separate the
passwords from the script. Indeed, Jared's suggestion will work but I still
have the passwords in the RMAN script which is what I am trying to get away
from.
So, there are two problems you are trying to solve.
That script was just to demo the connection process.
Personally, I use the Password server from "Perl for Oracle DBA's"
It uses that 'Perl' language that Niall referred to. :)
The version in the book uses plain text config file.
It was 'enhanced' sometime after publication of the book to allow
storing the config file with the passwords in an encrypted
format using RC4.
RC4 is old, but still fairly robust.
There are commercial password servers that have similar capabilities.
Password Manager Pro for instance has facilities to retrieve passwords
from the command line for use in scripts.
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Other related posts:
