Hello Jason,
The solution really depends on what you need to do - very precisely
I understand that you do not have yet detailed information, so here is some examples :
Example #1 : mapping rdbms to rdbms
When using a Bind technique, there is no real need to make encryption. The data is read from source, and written to the target within the same process. Not stored anywhere else, so no need to encrypt it, right ?
Example #2 : exporting data to a file with FileExport, for future import into a target rdbms
In this case, you don't want the password to be stored as clear text in the file. The idea is simply to use the source rdbms' encryption functions. For example with a Mysql database:
dev.mysql.com/doc/refman/5.5/en/encryption-functions.html
; or DBMS_CRYPTO package on Oracle ; etc...
I hope this helps
If you have more info on what you need to do please share it : what are source and target technologies, are there temporary files, etc.
