RE: Splitting production and development/test at the DBA level?

Ah, but don't you know, you can only change the password once every 3-5 days, and the last 10 have to be different. That's also supposed to be SOX. Then again, I can't see the harm of a "temporary" change. I used to do that often. Root/happy, system/funny, etc.  

Michael Kline

Principal Consultant

Business to Business Solutions

13308 Thornridge Ct

Midlothian, VA 23112

O: 804.744.1545

Fax: 804.763.0114  

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Nancy Iles
Sent: Thursday, December 14, 2006 9:37 PM To: oracle-l_at_freelists.org
Subject: RE: Splitting production and development/test at the DBA level?  

Does option 'C' exist? I am not very fond of either option 'A' or 'B'!  

Thanks for the feedback,  

Nancy

Date: Thu, 14 Dec 2006 11:18:04 -0500
From: tomday2_at_gmail.com
To: oracle-l_at_freelists.org
Subject: Re: Splitting production and development/test at the DBA level?

The way that I've seen the cloning issue handled is either;  

A - The production DBA does the cloning and sets the passwords to something innocuous before handing over to the development DBA  

or  

B- The production DBA temporarily changes the paswords in production, takes the backup and hands it and the temporary passwords over to the development DBA to do the development database build, and then sets the production database passwords to something different.  

Check the weather nationwide with MSN Search Try it now! <http://search.msn.com/results.aspx?q=weather&FORM=WLMTAG>

--
http://www.freelists.org/webpage/oracle-l