Oracle Enterprise sqlldr password
Posted: Fri May 11, 2007 12:34 pm
Hello,
Does anyone know of a way to "mask" or hide the password when using the Oracle Enterprise stage as a target, using the Oracle Enterprise stage "Load" write method?
This "Load" method uses the sqlldr Oracle utility to load the data, but uses the username and password in the connection, instead of using the userid parameter in the parameter file. The username/password in the connection or any in-line parameters will always override parameters in the parameter file, and the Oracle stage will not allow to omit the password. Thus, the username and password are visible as clear text when using "ps -ef" and in the Director logs.
example:
Oracle_Enterprise_13,0: The system(sqlldr ralq/cleartextpassword@etlpocT CONTROL=ora.11998.389758.0.ctl LOG=ora.11998.389758.0.log BAD=ora.11998.389758.0.log.bad SILENT=header PARFILE=ora.11998.389758.0.par) failed; see the log file for the Oracle specific message.
$ ps -ef | grep sqlldr
dsadm 15769 15765 11 11:33 ? 00:00:01 sqlldr ralq/cleartextpassword@etlpocT CONTROL=ora.15743.114366.0.ctl LOG=ora.15743.114366.0.log BAD=ora.15743.114366.0.log.bad SILENT=header PARFILE=ora.15743.114366.0.par
Any thoughts, comments, or suggestions are greatly appreciated.
Thanks,
Rob
Does anyone know of a way to "mask" or hide the password when using the Oracle Enterprise stage as a target, using the Oracle Enterprise stage "Load" write method?
This "Load" method uses the sqlldr Oracle utility to load the data, but uses the username and password in the connection, instead of using the userid parameter in the parameter file. The username/password in the connection or any in-line parameters will always override parameters in the parameter file, and the Oracle stage will not allow to omit the password. Thus, the username and password are visible as clear text when using "ps -ef" and in the Director logs.
example:
Oracle_Enterprise_13,0: The system(sqlldr ralq/cleartextpassword@etlpocT CONTROL=ora.11998.389758.0.ctl LOG=ora.11998.389758.0.log BAD=ora.11998.389758.0.log.bad SILENT=header PARFILE=ora.11998.389758.0.par) failed; see the log file for the Oracle specific message.
$ ps -ef | grep sqlldr
dsadm 15769 15765 11 11:33 ? 00:00:01 sqlldr ralq/cleartextpassword@etlpocT CONTROL=ora.15743.114366.0.ctl LOG=ora.15743.114366.0.log BAD=ora.15743.114366.0.log.bad SILENT=header PARFILE=ora.15743.114366.0.par
Any thoughts, comments, or suggestions are greatly appreciated.
Thanks,
Rob