This tip is designed to increase the security of imports/exports during batch processing of backups. It avoids the security problem of putting passwords in script files for privileged users (such as system). This tip has been tested on Oracle 7.3.3, 8.0.5 and 8.1.6.
I created the same user/password in all my databases with the following three roles:
connect, exp_full_database, imp_full_database(Note: user has no space quota.) This enables standard scripts to be written for exports and imports. I can put this user name and password in my batch script files and eliminate the security issue of my previous practice of putting system user passwords in a batch file that anyone could read.
For More Information
- Feedback: E-mail the editor with your thoughts about this tip.
- More tips: Hundreds of free Oracle tips and scripts.
- Tip contest: Have an Oracle tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize -- submit your tip today!
- Ask the Experts: Our SQL, database design, Oracle, SQL Server, DB2, metadata, and data warehousing gurus are waiting to answer your toughest questions.
- Forums: Ask your technical Oracle questions--or help out your peers by answering them--in our active forums.
- Best Web Links: Oracle tips, tutorials, and scripts from around the Web.