Security for Application Developers doing PL/SQL work in Oracle
Back in the days when I worked in an Oracle shop, we had a specific 'dev' (development) server, which had different security restrictions than the 'prod' (production) server.  Developers could do whatever they needed, and then we'd hand off the necessary scripts to the DBA to apply to the production server.

In the case of our critical systems (SCT Banner, for tracking classes &amp; students, and Oracle Financials), there were also 'test' and 'seed' servers.  Test was for user acceptance testing before stuff migrated from dev to prod;  'seed' was stock install of the software, so should we find a bug, we could verify if it was something we had introduced or came from SCT or Oracle's software.