RE: Any ideas for running CRON jobs under Security Requirements

From: Ruth Gramolini <rgramolini_at_tax.state.vt.us>
Date: Fri, 13 May 2005 12:57:17 -0400
Message-ID: <00bf01c557dc$d21dff10$8459000a@vttaxnet.tax.state.vt.us>

You can run rman for backups using "connect target" as long as you set the oracle sid before starting the backup and are logged on to the box as ORACLE. If you have oem you can just set the preferred users in the job. This way their are no plain text user/password pairs anywhere.

HTH<
Ruth

-----Original Message-----

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Hemant K Chitale Sent: Friday, May 13, 2005 12:47 PM
To: oracle-l_at_freelists.org
Subject: Any ideas for running CRON jobs under Security Requirements

How do you run CRON jobs {Online Backups, DB Monitoring} on Database Servers
when IT Security / SOX requirements state that

No userid-password pairs are to be kept in plain-text in any files
connect / as sysdba is not to be used

I can handle a) with CRON jobs running under the "oracle" account with "connect / as sysdba"
at the beginning of SQL scripts. I can handle b) if I hard code a userid/password with the
appropriate privileges. How do I handle both requirements ?

Hemant K Chitale
http://web.singnet.com.sg/~hkchital

--

http://www.freelists.org/webpage/oracle-l

--

http://www.freelists.org/webpage/oracle-l Received on Fri May 13 2005 - 13:01:57 CDT