How about using a DBMS_SCHEDULER job calling a wrapped stored procedure that passes a password variable into an O/S call to the batch file. On Sat, Apr 23, 2011 at 6:05 PM, Bill Myers <bwmyers@xxxxxxxxx> wrote: > Hi all, > I have the following commands in a batch file scheduled for daily > execution: > > set oracle_sid=mydatadb > rman target / catalog mycatusr/mycatpwd@mycatdb script Daily_Backup >> > backup.log > > My organization requires the catalog password (mycatpwd) above to be > encrypted and not stored as clear text in any other file or environment > variable. How can I still use this batch file for scheduled backups without > providing a clear text password? > > The only option I can think of is to compile the commands into a binary > executable. Any other ideas besides that? > > Thanks in advance. > Bill >