RE: Privileges by session
Date: Mon, 11 Jan 2010 08:17:09 -0500
The prerequisite for your solution is developer cooperation, as the developers have to agree to use the replicated environment. If my understanding of the situation is correct, this prerequisite does not exist.
Vlado Barun, M.Sc., OCE, OCA, MCP
Sr. Database Architect/Manager, Database Engineering and Operations Jewelry Television
Mobile: 865 335 7652
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Martin Bach Sent: Sunday, January 10, 2010 1:01 PM
Cc: martin.a.berger_at_gmail.com; wblanchard_at_societyinsurance.com; oracle-l_at_freelists.org Subject: Re: Privileges by session
Dear list members!
This is a really interesting thread with lots of useful information, but one important option (IMO) has not yet been mentioned.
If the main reason for allowing developers access to production data is for them to troubleshoot problems using current data, why don't you use your favourite replication mechanism such as streams or logical standby to a separate environment? Developers could use this to their heart's delight and you can impose your read only restrictions. There shouldn't be a logical argument against getting them off production with that approach either.
Any fixes can then be tested against the integration environment before it's rolled out to production by the DBAs. You could even use a physical standby to perform this testing: use flashback database or snapshot standby to activate it and test against current data, then revert it back to the standby role.
Hope this helps,
-- Martin Bach OCM 10g http://martincarstenbach.wordpress.com On 09/01/10 00:00, Upendra N wrote:Received on Mon Jan 11 2010 - 07:17:09 CST
> In our environment we have software dpkgs are built without the
[...] -- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-l