I have a script that is run as root. In this script, I start up Oracle, connect as internal, spool off the system password, alter system user identified by a known password, login as system and do my stuff, and then alter user system back to the original password after completing my tasks. Is this a bad practice? I am specifically wondering if there is a posibility that the system tablespace could get corrupted doing this. Any information is greatly appreciated.
While I can say that this is "bad", it isn't necessarily the best way either. Probably the best way to accomplish this is to set up your own account to do your work. Make sure that you grant the privileges you will need to get your work accomplished. Then have your root script sign on as that user. You don't have to monkey with changing SYSTEM's password at all.
For More Information
- Dozens more answers to tough Oracle questions from Brian Peasland are available.
- The Best Oracle Web Links: tips, tutorials, scripts, and more.
- Have an Oracle or SQL tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical Oracle and SQL questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, Oracle, SQL Server, DB2, metadata, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
Dig Deeper on Oracle database design and architecture
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.