Sunday Mar 27, 2016

Announcing my new Oracle Database Cloud Cookbook from Oracle Press


Happy Easter to all of you and your families.

I am pleased to announce my new book "Oracle Database Cloud Cookbook with Oracle Enterprise Manager 13c Cloud Control" to be published by Oracle Press, and is now available as a pre-order from Amazon. The Amazon link is:

This practical Oracle Press guide “Oracle Database Cloud Cookbook with Oracle Enterprise Manager 13c Cloud Control” teaches cutting-edge techniques for building, configuring, and managing a secure private database cloud with Oracle Enterprise Manager 13c. This hands-on volume lays out ready-to-deploy roadmaps for the design and maintenance of high-performance private database clouds using Oracle Enterprise Manager 13c. Learn best practices for a wide variety of different approaches--Database as a Service, Snap Clone as a Service, Schema as a Service, and Pluggable Database as a Service. The book also explains how to use the RESTful API for performing DBaaS, SCHaaS and PDBaaS, and gives step by step instructions to set up the Oracle Database Hybrid Cloud using the Enterprise Manager Hybrid Gateway to connect to the Oracle Public Database Cloud.

Oracle Database Cloud Cookbook with Oracle Enterprise Manager 13c Cloud Control thoroughly explains how to architect, configure, and manage every component in a private/hybrid database cloud lifecycle. You will get an insider's solutions for securing your cloud-based infrastructure, generating reliable RMAN backups, and protecting your mission-critical enterprise information using Oracle Data Guard. This comprehensive volume from Oracle Press features detailed, step-by-step instructions with multiple screen shots and diagrams that illustrate each technique along the way.

• Real-world examples and case studies illustrate applications in various industries

• Offers essential skills for cloud administrators and DBAs

• Author is an Oracle Certified Master, previous Oracle ACE director, and experienced computing writer

Table of Contents:

Ch. 1: Consolidation Planning for the Cloud

Ch. 2: Database as a Service

Ch. 3: Schema as a Service

Ch. 4: Pluggable Database as a Service

Ch. 5: Hybrid Database Cloud

Ch. 6: Using the RESTful API

Ch. 7: Managing Database Backups

Ch. 8: Managing Standby Databases

Hope all my readers will enjoy this book which I have written in easy to understand English. Please recommend to your friends and clients as well.



PORUS HOMI HAVEWALA | Cloud (PaaS) Architect

Double Oracle Certified Master (OCM 10g & OCM 11g)

Thursday Aug 01, 2013

New White Paper: Advanced Uses of Oracle Enterprise Manager 12c (published AUGUST 2013)


I am pleased to say a new Oracle white paper of mine has been published on 1st August 2013:

White Paper: Advanced Uses of Oracle Enterprise Manager 12c

This white paper includes information on EM12c Release 3 ( and Managing Database 12c with EM12c Release 3.

This white paper is also currently visible in the main Oracle Enterprise Manager page:

Happy Reading!!



Thursday Feb 21, 2013

Endless Growth

Studies show that many corporations world-wide expect their IT footprint to grow in the coming years. They expect more servers, more databases, more data, and more of everything.

They require more floor space in their data centers, and also the corresponding greater power footprint. Have you heard of a data center where no more servers can be added because the power supply has reached its limit, or the UPS (Uninterruptible Power Supply) can no longer cope? This story is not new.

The growth seems to be endless, and this is fuelled by today's information age, where larger and larger volumes of data need to be stored and distributed to satisfy an ever-growing demand. More applications are coming to use those databases, on more and more application servers.

So for the IT Manager, this will mean more of everything in his/her data center. There may be different hardware platforms, there may be different operating systems (e.g. Solaris, Linux, IBM-AIX, Microsoft Windows), and in each case there may be different versions – such as the different flavors of Linux supplied by different vendors including Oracle Enterprise Linux, Red Hat, SUSE Linux, and so on.

To add to the complexity, nothing placed in production should be treated as static. Software changes in development cycles, enhancements take place, or security/functional issues are found. For almost anything in the IT world, new patches are bound to be released. These will also need to be applied to production, test, reporting, staging, and development environments in the Data Center on an ongoing basis.

For the Database side of things, Oracle releases quarterly a combination of security fixes known as the Critical Patch Update (CPU). Other patches are bundled together and released every quarter in the form of a Patch Set Update (PSU), and this also includes the CPU for that quarter.

Oracle strongly recommends applying either the PSU or the CPU every calendar quarter. If you prefer to apply the CPU, continue doing so. If you wish to move to the PSU, you can do so, but in that case continue only with the PSU.

The quarterly patching requirement, as a direct recommendation from Oracle, is followed by many companies which prefer to have their Databases secured with the latest security fixes. This underscores the importance of patching.

However, if there are hundreds of development, test, staging and production Databases in the Data Center to be patched, the situation quickly turns into a major manual exercise every three months. DBAs and their Managers start planning for the patch exercise in advance, and a lot of resources are allocated to make it happen – with the Administrators working on each Database serially, at times overnight and at times over the weekend.

There are a number of steps involved in patching each Database, such as locating the appropriate patch in My Oracle Support (MOS), downloading the patch, transferring it to each of the target servers, upgrading the OPATCH facility in each Oracle Home, shutting down the Databases and Listeners running from that Home, applying the patch, starting each of the Databases in restricted mode, applying any supplied SQL scripts, restarting the Databases in normal mode, and checking the patch inventory.

These steps have to be manually repeated on every Database Home on every server, and on every Database in that Home. Dull repetition of these steps in patching the hundreds of servers in a data center is a very monotonous task, and it can lead to an increase in human errors.

To avoid these issues inherent in manual patching, some companies decide not to apply the quarterly patches on their Databases. They wait for a year, or a couple of years, before they consider patching, and some even prefer to apply year-old patches instead of the latest patches. This is counter-productive and leads to their Databases being insecure and vulnerable to attacks, since the latest recommended CPUs from Oracle have not been applied.

What then is the solution, to convince these companies to apply patches regularly? If the patching process can be mostly automated (but still under the control of the DBAs), it would reduce the quarterly patching effort to a great extent. Companies would then have the confidence that their existing team of DBAs would be able to manage the patching of hundreds of Databases in a controlled and automated manner, keeping human error to a minimum.

The Database Lifecycle Management pack for Oracle Enterprise Manager Cloud Control 12c is able to achieve this via its Patch Automation capability. We will now look into Patch Automation and the close integration of Enterprise Manager with My Oracle Support.

 For the full Oracle Technet article, refer to


Blog by Porus Homi Havewala


« July 2016