Oracle 12c helps developers

October 3rd, 2013


September/October Cover

I’m super excited about two aspects of 12c (among many). First is Oracle 12c EM Express which gives light weight access to Oracle performance information without all the agents and heavy infrastructure. You basically just point a browser at the database via a setup port and voila. Since EM Express has limited functionality  but gives powerful insight into performance on the database it’s perfect for developers to use and see the impact of their code in the databases where they are running their code.

The other feature in 12c that is exciting is pluggable databases. Why? Because for me as someone who clones 100s to 1000s of databases using virtual databases via Delphix where creating a clone is 4 clicks of a mouse, almost no storage usage and takes a few minutes, it means I can clone more databases. Why? Because each of these “free” virtual databases I create with Delphix still creates it’s own SGA which is at a minimum about  half a gigabyte. Now with pluggable databases that will go down to about 100 megabytes or 1/5 the size, which means I’ll be able to put a couple of hundred Delphix virtual databases on a machine thanks to Oracle pluggable databases.

What does all this mean? It means that each developer can have their own full copy of  production with a shared disk foot print, a shared memory caching footprint (only available in Delphix) and shared SGA components and instance processes. On top of that the developers can get clear and powerful views into the impact of the code they run on their databases.

Have an article in the latest  Oracle magazine, but don’t see a way to link the article in so here it is. There is also a video that goes along with the article at the bottom of this post.












  1. Trackbacks

  2. No trackbacks yet.

  2. iggy
    | #1

    “Now DBAs can give the developers read-only access to a simplified database management console so they can see the impact of their code.” I checked the documentation and found the following.
    Granting Access to EM Express for Nonadministrative Users

    As a database administrator, you can log in to EM Express with the SYS or SYSTEM user account to perform administrative and other tasks. Nonadministrative users may also want to log in to EM Express. For example, application developers may want to take advantage of the EM Express interface to create or modify tables, indexes, views, and so on. You must grant access to EM Express to these users before they can log in.

    For nonadministrative users to have access to EM Express, they must be granted the EM_EXPRESS_BASIC or the EM_EXPRESS_ALL role.

    The EM_EXPRESS_BASIC role enables users to connect to EM Express and to view the pages in read-only mode. The EM_EXPRESS_BASIC role includes theSELECT_CATALOG_ROLE role.

    The EM_EXPRESS_ALL role enables users to connect to EM Express and use all the functionality provided by EM Express (read/write access to all EM Express features). The EM_EXPRESS_ALL role includes the EM_EXPRESS_BASIC role.

    For an example of granting privileges and roles to a user account, see “Example: Granting Privileges and Roles to a User Account”.

1 + six =