Oracle Home Management – part 3: Strengths and limitations of Rapid Home Provisioning

In the previous post I mentioned that having a central repository storing the Golden Images would be the best solution for the Oracle Home provisioning.

In this context, Oracle provides Rapid Home Provisioning: a product included in Oracle Grid Infrastructure that automates home provisioning and patching of Oracle Database and Grid Infrastructure Homes, databases and also generic software.

rhp-conceptOracle Rapid Home Provisioning simplifies tremendously the software provisioning: you can use it to create golden images starting from existing installations and then deploy them locally, across different nodes, on local or remote clusters, standalone servers, etc.

Having a central store with enforced naming conventions ensures software standardization across the whole Oracle farm, and makes patching easier with less risks. Also, it allows to patch existing databases, moving them to Oracle Homes with a higher patch level, and taking care of service draining and rolling upgrades when RAC or RAC One Node deployments exist. Multiple databases can be patched in a single batch using one single rhpctl command.

I will not explain the technical details of Rapid Home Provisioning implementation operation. I already did a webinar a couple of years ago for the RAC SIG:

Burt Clouse, the RHP product manager, did a presentation as well about Rapid Home Provisioning 12c Release 2, that highlights some new features that the product was missing in the first release:

More details about the new features can be found here:

Close to be the perfect product, but…

If rapid home provisioning is so powerful, what makes it less appealing for most users?

In my opinion (read: very own personal opinion 🙂 ), there are two main factors:

First: The technology stack RHP is relying on is quite complex

Although Rapid Home Provisioning 12c Release 2 allows Oracle Home deployments on standalone servers (it was not the case with 12c Release 1), the Rapid Home Provisioning sever itself relies on Oracle Grid Infrastructure 12cR2. That means that there must be skills in the company to manage the full stack: Clusterware, ASM, ACFS, NFS, GNS, SCAN, etc. as well as the RHP Server itself.

Second: remote provisioning requires Lifecycle Management Pack (extra-cost) option licensed on all the RHP targets

If Oracle Homes are deployed on the same cluster that hosts the RHP Server, the product can be used at no extra cost. But if you have many clusters, or using standalone servers for your Oracle databases, then RHP can become pricey very quickly: the price per processor for Lifecycle Management Pack is 12’000$, plus support (pricelist April 2018). So, buying this management pack just to introduce Rapid Home Provisioning in your company might be an excessive investment.

Of course, depending on your needs, you can evaluate it and leverage its full potential and make a bigger return of investment.

Or, you might explore if it is viable to configure each cluster as Rapid Home Provisioning Server: in this case it would be free, but it will have the additional complexity layer on all your clusters.

For small companies, simple architectures and especially where Standard Edition is deployed (no Management Pack for Standard Edition!), a self-made, simpler solution might be a better choice.

In the next post, before going into the details of a hypothetical self-made implementation, I will introduce my thoughts about the New Oracle Database Release Model.


The following two tabs change content below.


Principal Product Manager at Oracle
Ludovico is a member of the Oracle Database High Availability (HA), Scalability & Maximum Availability Architecture (MAA) Product Management team in Oracle. He focuses on Oracle Data Guard, Flashback technologies, and Cloud MAA.

8 thoughts on “Oracle Home Management – part 3: Strengths and limitations of Rapid Home Provisioning

  1. Update from my side, I was successful in deploying the workingcopy but by using root`s password. Not sure what is wrong with the keys. So the feature does work, most probably the syntax I use in my command is not correct, but this is something out of the documentation.

  2. Hi Ludovico,

    I am trying to deploy a working copy of a DB home on a remote node (no GI , no RHP client – would be standalone) from a 19c cluster. What I have done so far as per documentation is to add the root key on the RHP server at /home/oracle/rhp/ssh-key/key . Also there is user equivalency between oracle on source and root on target. I get the following error:

    As oracle (RHPS owner):

    rhpctl add workingcopy -workingcopy db19_RU10 -image test_image -targetnode HOSTNAME -path /u01/app/oracle/product/19.3.0/db_home1 -oraclebase /u01/app/oracle -auth sshkey -arg1 user:root -arg2 identity_file:/home/oracle/rhp/ssh-key/key

    PRCG-1186 : missing “-user” option for standalone provisioning

    If I add the “-user oracle” argument I get:

    PRCC-1021 : One or more of the submitted commands did not execute successfully.

    The RHP log shows the following:
    [GHOperationCommonImpl.addWorkingCopy:3036] failed to determine if target node is a standalone node due to oracle.cluster.remote.ExecException : PRCC-1021 : One or more of the submitted commands did not execute successfully.

    Any ideas how that can be solved?

  3. Hi Ludovico,

    Thanks, Can you please help me understand this part

    Why to use GNS, we have a static ip’s registered in cluster name i.e

    This is how works – – > round robin – > connect to RAC -> vip -> load balancing..

    I am still not understanding this part , how GNS should sit on top of this scan resolution, how is it beneficial.

    Server: — dns server
    Address: xx.xx.xx.xx

    Non-authoritative answer:
    Addresses: xx.x.x.184

  4. Hi,

    I have the following doubts.
    -If I want to do a remote installation I can do it just giving the hostname target, or it’s mandatory everytime to configure it as a client server

    -To propagate a remote server installations it’s mandatory to have a NFS filesystem between the RHP servers and the targets, it I don’t have a NFS filesystem is there a way to do it?


    • The NFS server setup is managed by RHP. Actually, the RHP Server creates ACFS filesystems and HANFS services on top of it, presents it to the clients and depending on the deployment, it copies the OH to the client cluster.

  5. Pingback: Blog Post: Oracle Home Management – part 3: Strengths and limitations of Rapid Home Provisioning

  6. Pingback: Oracle Home Management – part 3: Strengths and limitations of Rapid Home Provisioning - Ludovico Caldara - Blogs - triBLOG

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.