Document 2097026.1

11/11/23, 9:10 PM Document 2097026.
PowerView is Off Parmanto (Available) Profile (2) Help

Time left:16:49:19
Knowledge RCA Customer Exceptions CMS Service Requests Patches & Updates Certifications Systems Collector Settings XNS Advanced
Copyright (c) 2023, Oracle. All rights reserved. Oracle Confidential.
How To Setup a Rapid Home Provisioning (RHP) Server and Client (Doc ID 2097026.1) To Bottom
In this Document Was this document helpful?
Goal Yes
No
Solution
Introduction
Document Details
Using Rapid Home Provisioning
GNS Setup
Type: HOWTO
Creating a Rapid Home Provisioning Server Status: PUBLISHED
RHP Server: Create the Rapid Home Provisioning Server resource Distribution: EXTERNAL
Visibility: EXTERNAL
RHP Server: Start the Rapid Home Provisioning Server resource Last Major Update: Feb 5, 2020
RHP Server: HA-VIP setup Last Update: Jun 13, 2023
RHP Server: Create client data file

RHP Client setup Related Products
Scenarios to Use Rapid Home Provisioning Oracle Database - Enterprise Edition
Oracle Database - Enterprise Edition
Adding Gold Images to the Rapid Home Provisioning Server Oracle Database Cloud Schema Service
Database Home provisioning Oracle Database Exadata Express Cloud Service
Gen 1 Exadata Cloud at Customer (Oracle Exadata
Database home provisioning (LOCAL) Database Cloud Machine)
Show More
Database home provisioning (NFS)
Database provisioning
Information Centers
Switch to Managed Homes
Information Center: Transportable Tablespaces (TTS)
Database Patching for Oracle Database [1461278.2]
Standby Database Patching 19c Database Upgrade - Self Guided Assistance with
Best Practices [1919.2]
Troubleshooting
Index of Oracle Database Information Centers
References [1568043.2]
インフォメーション・センター: データベースおよび
APPLIES TO: Enterprise Manager 日本語ドキュメント [1946305.2]
Information Center: Data Warehousing [1487754.2]

Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Show More
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later Document References
Oracle Cloud Infrastructure - Database Service - Version N/A and later Rapid Home Provisioning (RHP) setup in "1-Click"
IBM AIX on POWER Systems (64-bit) [2124960.1]
Linux x86-64
RHP: Rapid Home Provisioning Server - Minimum
Oracle Solaris on SPARC (64-bit) Requirement [2126710.1]
Oracle Solaris on x86-64 (64-bit)
RHP (Rapid Home Provisioning): mnttest tool to test
NFS 'export' and 'mount' functionalities [2167541.1]
GOAL
ODA (Oracle Database Appliance): How To Setup a
Rapid Home Provisioning (RHP) Server and Client
To provide the steps to setup a Rapid Home Provisioning (RHP) Server & Client [2054804.1]
SOLUTION
Recently Viewed
Show More
https://myaccess.oraclevpn.com/+CSCO+0075676763663A2F2F7A6266727A632E68662E62656E7079722E70627A++/epmos/faces/DocumentDisplay?_afrLoop=27183484852632&parent=DOCUMENT&sourceId=2126710.1&id=2097026.1&_afrWindowMode=0&_adf.ctrl-state=16cz4mmm0j_127 1/12
11/11/23, 9:10 PM Document 2097026.1
RHP: Rapid Home Provisioning Server - Minimum
Introduction Requirement [2126710.1]
Time left:16:49:19
RAC Rolling Install Process for the "Oracle
Rapid Home Provisioning (RHP) represents a standard way for provisioning, patching and update at organizational level, in a unified manner, across all architectural layers of software infrastructure – Oracle
JavaVM Component Database PSU/RU"
databases and custom software. (OJVM PSU/RU) Patches [2217053.1]
FPP: 19.15: PRGO-2467 : Working Copy "
Rapid Home Provisioning is a method of deploying software homes from single cluster where you create, store and manage templates of Oracle homes as images - called gold images - of Oracle <workingcopy_name>" already exists with the
software. The DBA can make a working copy of any gold image and then provision that working copy to any RHP Client in a data center. specified path "<oracle_home_path>" [2899264.1]
RHP is installed as part of Grid Infrastructure. Oracle Clusterware manages the components that form the Rapid Home Provisioning Server. These components include the RHP server itself, Grid PRCS-1115 : AN ATTEMPT TO RETRIEVE THE
Naming Service (GNS) which is used to advertise the location of the RHP server, a VIP to support HA-NFS (required if there are any clients that you want to provision to - whether you use NFS RAPID HOME PROVISIONING SERVER HOST NAME
storage for the workingcopies or not) and Oracle ASM Cluster File System (ACFS) which is used to store snapshots of the working copies. AND PORT NUMBER FAILED WITH THE
The gold images represent an installed home, whether that is an Oracle Database software home or some custom software home. The gold image is stored in an Oracle Automatic Software FOLLOWING ERROR: [29624966]
Management Cluster File System (Oracle ACFS). PRCS-1115 : AN ATTEMPT TO RETRIEVE THE
Metadata describing an installed home is stored as an image series in the Management Repository. The Management Repository (or Management Database MGMTDB) is created when installing RAPID HOME PROVISIONING SERVER HOST NAME
AND PORT NUMBER FAILED WITH THE
Oracle Grid Infrastructure. FOLLOWING ERROR: [29624973]
Note: in order to provide an Oracle Home (workingcopy) to an RHP Client will require about 60min if LOCAL, 30min if by NFS (storagetype NFS). Many operations are needed like DBHome cloning,
relink, etc.
Using the rhpctl utility, gold images can be imported from an installed home on any of the RHP clients or RHP Server.
An existing working copy can be promoted to a gold image.
A working copy is an instantiation of an Oracle database software home

Working copies are writable and independent of one another
Using RHP we can provision Oracle GI/DB software for the various versions
11.2.0.* (Oracle Database 11g)

12.1.0.* (Oracle Database 12c)
12.2.0.* (Oracle Database 12c)
It's recommended on RHP Server to use the latest GI (Grid Infrastructure) version (at the time of writing this article 12.2.0.1_180116).
Using Rapid Home Provisioning
Rapid Home Provisioning requires ASM, the Management DB and the Grid Naming Service (GNS). As part of the Grid Infrastructure deploy
ASM is configured
The Management Repository (Management DB) is available. The Management DB is installed by default with Oracle Grid Infrastructure 12.2.0.1
# $GRID_HOME/bin/srvctl status mgmtdb

Database is enabled
Instance -MGMTDB is running on node oda101
As the Management DB (MGMTDB) is doing a key role with the RHP, you should consider to setup a backup for it, in particular for the schema: 'GHSUSER' (for example using expdp).
The size of it depends on the number of images, workingcopies, sites, users, etc.
In general, the size requirement is very low since we only store the metadata: for 100 images, 2000 workingcopies and 25 RHP Clients, our internal test showed a size of about 200 Mb only.
You need to configure the GNS such that a GNS VIP is provided. A GNS with Zone Delegation is not required by RHP.
Note:
you could skip the manual steps to setup RHP Server using "setrhp" the "1-Click" utility described on Note:2124960.1 - Rapid Home Provisioning (RHP) setup in "1-Click"
GNS Setup
Execute the following command as root, providing a valid IP address (domain is not needed on RHP):
# $GRID_HOME/bin/srvctl add gns -vip {<vip_name> | <ip>}

# $GRID_HOME/bin/srvctl start gns
example:
# $GRID_HOME/bin/srvctl add gns -vip rhps-gns
# $GRID_HOME/bin/srvctl start gns
11/11/23, 9:10 PM Document 2097026.1
# $GRID_HOME/bin/srvctl status gns
GNS is running on node rhps.
GNS is enabled on node rhps. Time left:16:49:19
# $GRID_HOME/bin/srvctl config gns
GNS is enabled.
GNS VIP addresses: 10.xxx.51.63
Domain served by GNS: No domain is being forwarded.
Note: currently the GNS setup is required on RHP Server only. We advertise to GNS the exact host and port where RHP Server is running which is used by RHP Clients to connect to RHP Server.
Once the GNS is configured the Rapid Home Provisioning server can be configured.
Creating a Rapid Home Provisioning Server
The Rapid Home Provisioning Server uses an Oracle ACFS file system for Oracle database software homes that will be published to clients.
To configure the Rapid Home Provisioning Server you will need to:
Provide an ASM diskgroup (DATA/RECO). It is recommended that this diskgroup is with at least 100Gb in free space. The diskgroup is used to store gold images and RHP managed NFS-provisioned
workingcopies.
Provide a mount path that exists on all nodes of the RHP server. Oracle ACFS snapshots can be used to provision server-local workingcopies or NFS-mounted workingcopies on clients.
Configure an HA VIP. The NFS client, on the RHP client clusters will communicate with the NFS server on the RHP server over this IP address for NFS mounted homes. The VIP allows for the
configuration of HANFS. Note that the HA VIP has to be configured in the same subnet as the default network configured on the RHP server.
As HANFS requires NFS in order to run. It is assumed that NFS (and its associated needs) will be started by init scripts at node boot time. NFS will need to be running on all RHP server nodes. We can
check this on each node issuing:
# service rpcbind status

rpcbind (pid 13256) is running...
# service nfs status

rpc.mountd (pid 13858) is running...
nfsd (pid 13855 13854 13853 13852 13851 13850 13849 13848 13847 13846 13845 13844 13843 13842 13841 13840 13839 13838 13837 13836 13835 13834 13833 13832 13831 13830
13829 13828 13827 13826 13825 13824 13823 13822 13821 13820 13819 13818 13817 13816 13815 13814 13813 13812 13811 13810 13809 13808 13807 13806 13805 13804 13803
13802 13801 13800 13799 13798 13797 13796 13795 13794 13793 13792 13791 13790 13789 13788 13787 13786 13785 13784 13783 13782 13781 13780 13779 13778 13777 13776
13775 13774 13773 13772 13771 13770 13769 13768 13767 13766 13765 13764 13763 13762 13761 13760 13759 13758 13757 13756 13755 13754 13753 13752 13751 13750 13749
13748 13747 13746 13745 13744 13743 13742 13741 13740 13739 13738 13737 13736 13735 13734 13733 13732 13731 13730 13729 13728) is running...
rpc.rquotad (pid 13713) is running...
# service nfslock status

rpc.statd (pid 23372) is running...
If one of these is not running, you could start it by using (as root):
/etc/init.d/<service> status
The 'chkconfig' command can be used to ensure that these services are started at boot time
chkconfig nfs on
chkconfig rpcbind on
chkconfig nfslock on
Note: on OL5, the "rpcbind" service is called "portmap"
NFS operations such 'export' and 'mount' may fail due to misconfiguration or bugs.
You may verify the NFS functionalities with 'mnttest' tool, see note:2167541.1 - RHP (Rapid Home Provisioning): mnttest tool to test NFS 'export' and 'mount' functionalities
NFS Usage: NFS is not required for 19c RHPS managing 19c RHPC or 18.4RHPC or later, however RHPS needs NFS for managing 122 RHPC.
11/11/23, 9:10 PM Document 2097026.1
Time left:16:49:19
Once the pre-requisites mentioned above have been met, the RHP server can be added to Grid Infrastructure and started.
RHP Server: Create the Rapid Home Provisioning Server resource
Starting with Oracle Grid Infrastructure 18.1.0.0.0, when you install Oracle Grid Infrastructure, the Rapid Home Provisioning Server is configured, by default, in the local mode to support the local
switch home capability. If you must configure the general Rapid Home Provisioning Server product, then you must remove the current local-mode Rapid Home Provisioning Server, using the following
commands, as root:
# srvctl stop rhpserver
Ignore a message similar to "Rapid Home Provisioning Server is not running".
# srvctl remove rhpserver
Assuming DATA diskgroup usage, and '/rhp_storage' as ACFS mount point, issue the following command (as 'root' user):
# $GRID_HOME/bin/srvctl add rhpserver -storage <rhp_acfs-storage_path> -diskgroup <disk_group_name>
example:
$GRID_HOME/bin/srvctl add rhpserver -storage /rhp_storage -diskgroup DATA
Note: The storage path "/rhp_storage" is automatically created by srvctl
If adding rhpserver with above command you are getting the warning message:
PRCT-1431 : The Oracle ASM Dynamic Volume Manager compatibility attribute is not set for disk group
you can set it up with the command (attaching ASM instance with sqlplus)
ALTER DISKGROUP data SET ATTRIBUTE 'compatible.advm' = '12.2';
You can check the status for rhp server doing:
# $GRID_HOME/bin/srvctl status rhpserver

Rapid Home Provisioning Server is enabled
Rapid Home Provisioning Server is not running
On all RHP Server nodes at this time, you have a new ACFS mount point:
[root@oda101 ~]# mount

(...)
/dev/asm/<MOUNT_PT> on /rhp_storage/chkbase type acfs (rw)
RHP Server: Start the Rapid Home Provisioning Server resource
Issue the following command (as 'root' user):
# $GRID_HOME/bin/srvctl start rhpserver
example:
[root@oda101 ~]# $GRID_HOME/bin/srvctl start rhpserver
[root@oda101 ~]# $GRID_HOME/bin/srvctl status rhpserver
11/11/23, 9:10 PM Document 2097026.1
Rapid Home Provisioning Server is enabled
Rapid Home Provisioning Server is running on node oda102
Time left:16:49:19
RHP Server: HA-VIP setup
On the RHP server as the Grid Infrastructure owner determine if an HA-VIP has been created (as 'grid' user):
$ $GRID_HOME/bin/srvctl config havip

HAVIP exists: /rhphavip/10.xxx.51.64, network number 1
Description:
Home Node:
HAVIP is enabled.
HAVIP is individually enabled on nodes:
HAVIP is individually disabled on nodes:
If it's not configured, you need to issue the following command (as root):
# $GRID_HOME/bin/srvctl add havip -id id -address {host_name | ip_address}
example
[root@oda101 ~]# $GRID_HOME/bin/srvctl add havip -id rhphavip -address 10.xxx.51.64
RHP Server: Create client data file
On RHP Server create the RHP client configuration file (as 'grid' user), RHPCTL creates the client data file in the directory path you specify after the -toclientdata flag. The name of the client data file is
"client_cluster_name".xml:
$GRID_HOME/bin/rhpctl add client -client <client_cluster_name> -toclientdata <path>
example:
[grid@oda101 ~]$ $GRID_HOME/bin/rhpctl add client -client odaremote1-c -toclientdata /home/grid
oda101.<DOMAIN_NAME>: Creating client data ...
oda101.<DOMAIN_NAME>: Client data created for user "odaremote-c".
[grid@oda101 ~]$ ls –al /home/grid/stormcloud-cluster.xml

-rw-r—-r-- 1 grid oinstall 3158 Oct 31 21:59 /home/grid/odaremote-c.xml
Note: to get the (RHP Client) cluster name (as grid user) issue the following command:
$GRID_HOME/bin/cemutlo -n
move the RHP Client config file created above to the RHP Client:
example:
[grid@oda101 ~]$ scp odaremote-c.xml root@odaremote1:/home/grid
At this time you should configure the RHP Client.
RHP Client setup
12.1.0.2 target cluster cannot be an RHP client of an 12.2 RHP Server. For a 12.2 RHP server cluster, pre-12.2 targets can be accessed using one of the connectivity mechanisms - sudo or root or ssh.
This situation applies only between 12.1 and 12.2
Perform the following actions on the RHP client cluster (as 'root' user):
1. Create the RHP client using the XML wallet created for this cluster
11/11/23, 9:10 PM Document 2097026.1
2. Start the RHP client.
Time left:16:49:19
$GRID_HOME/bin/srvctl add rhpclient –clientdata <path/rhpclient_configfile.xml>
$GRID_HOME/bin/srvctl start rhpclient
example:
[root@odaremote1 ~]# $GRID_HOME/bin/srvctl add rhpclient -clientdata /home/grid/odaremote-c.xml
[root@odaremote1 ~]# $GRID_HOME/bin/srvctl status rhpclient
Rapid Home Provisioning Client is enabled
Rapid Home Provisioning Client is not running
[root@odaremote1 ~]# $GRID_HOME/bin/srvctl start rhpclient
The command “srvctl add rhpclient” has two optional arguments:
-diskgroup <dg_name> A disk group from which to create the ACFS file systems for image storage.
-storage <base_path> A location which is available on every cluster node and is not necessarily shared.
"-diskgroup" and "-storage" are defined as a pair (you cannot define one without the other). They can be provided in "srvctl add rhpclient", and they may be modified or added with "srvctl modify
rhpclient". The specified diskgroup and storage location are used in two scenarios:
1. when provisioning working copies of Oracle Database Homes in to RHP_MANAGED_STORAGE. RHP_MANAGED_STORAGE is the recommended storage type for Oracle Database Homes because it
leverages ACFS features to minimize storage footprint.
2. If the client is a multi-node cluster. When a working copy of a software home (Grid, DB or generic) is provisioned to the client, the client will create a local cached copy in ACFS, and then copy it to the
other nodes of the cluster locally. (Otherwise, the RHP Server itself must provision the working copy to each node.)
Scenarios to Use Rapid Home Provisioning
Adding Gold Images to the Rapid Home Provisioning Server
Rapid Home Provisioning Server stores and serves gold images of software homes. These gold images must be instantiated on the Rapid Home Provisioning Server. Gold images are read-only, preventing a
client from running programs from them. Gold images are not used as software homes directly. Rather, the gold image is used to create working copies. These working copies are usable as software homes
on RHP Client.
The DBA can import software to the Rapid Home Provisioning Server using any one of the following methods:
- Import a gold image from an installed home on the Rapid Home Provisioning Server using the following command:
rhpctl import image -image <image name> -path <source oracle home path> -imagetype ORACLEDBSOFTWARE
- Import a gold image from an installed home on a Rapid Home Provisioning Client, using the following command run from the RHP Client:
rhpctl import image –image <image name> –path <source oracle home path>
- Promote an existing workingcopy to a gold image using the following command:
rhpctl add image –image <image name> -workingcopy <workingcopy name>
As example, let's suppose you have created several Oracle homes (on RHP Server)
Oracle Home Name Oracle Home version Home Location

---------------- ------------------- ------------
OraDb11203_home1 11.2.0.3.14(20299017,17592127) <DB_HOME_1>
OraDb11204_home1 11.2.0.4.6(20299013) <DB_HOME_2>
OraDb12102_home1 12.1.0.2..4(20831110,20831113) <DB_HOME_3>
You could make them available as gold image issuing the following command (as 'grid' user):
example:
$ $GRID_HOME/bin/rhpctl import image -image OraDb11203_home1 -path <DB_HOME_1> -imagetype ORACLEDBSOFTWARE
slcac464.<DOMAIN_NAME>: Creating a new ACFS file system for image "OraDb11203_home1" ...
slcac464.<DOMAIN_NAME>: Copying files...
slcac464.<DOMAIN_NAME>: Copying home contents...
slcac464.<DOMAIN_NAME>: Changing the home ownership to user oracle...
slcac464.<DOMAIN_NAME>: Transferring data to 1 nodes
slcac464.<DOMAIN_NAME>: 10% complete
11/11/23, 9:10 PM Document 2097026.1
slcac464.<DOMAIN_NAME>: 40% complete Time left:16:49:19
slcac464.<DOMAIN_NAME>: Changing the home ownership to user grid...


Note as at this time you will have three new ACFS filesystems (for every single rhpctl import command, a new ACFS mount point will be created):
$ df -h
Filesystem Size Used Avail Use% Mounted on
(...)
/dev/asm/<MOUNT_PT> 1.0G 141M 884M 14% /rhp_storage/images/chkbase
/dev/asm/ghvol960162-338
15G 5.2G 9.9G 35% /rhp_storage/images/iOraDb11203_home1673418
15G 5.2G 9.9G 35% /rhp_storage/images/iOraDb11204_home1977401
18G 5.9G 13G 33% /rhp_storage/images/iOraDb12102_home1267449
Database Home provisioning
The command rhpctl add workingcopy is used to provision an ORACLE_HOME for use by an Oracle database. This command can be run on the RHP Server or on the RHP Client. If run on the RHP Server,
the command can provision an Oracle database either RHP-server-local or remotely on any RHP Client. When using the rhpctl command on the RHP Server, use the -client option to specify the remote
cluster.
- Create the mount point for the working copy on all nodes of the RHP Client
example:
[root@odaremote1 /]# mkdir -p /u01/rhp_base
[root@odaremote1 /]# chown -R oracle:oinstall /u01/rhp_base
11/11/23, 9:10 PM Document 2097026.1
[root@odaremote2 /]# mkdir -p /u01/rhp_base
[root@odaremote2 /]# chown -R oracle:oinstall /u01/rhp_base
Time left:16:49:19
Database home provisioning (LOCAL)
Usage: rhpctl add workingcopy -workingcopy <workingcopy_name> -image <image_name> [-oraclebase <oraclebase_path>] [-path <where_path>] [-storagetype {NFS | LOCAL |
RHP_MANAGED}] [-user <user_name>] [-dbname <unique_db_name> [-dbtype {RACONENODE | RAC | SINGLE}] [-datafileDestination <datafileDestination_path>] [-dbtemplate
<file_path> | <image_name>:<relative_file_path>] {-node <node_list> | -serverpool <pool_name> [-pqpool <pool_name> | -newpqpool <pool_name> -pqcardinality
<cardinality>] | -newpool <pool_name> -cardinality <cardinality> [-pqpool <pool_name> | -newpqpool <pool_name> -pqcardinality <cardinality>]} [-cdb] [-pdbName
<pdb_prefix> [-numberOfPDBs <pdb_count>]]] [-client <cluster_name>] [-ignoreprereq | -fixup] [-responsefile <response_file_path>] [-clusternodes <nodelist>] [-groups
<grouplist>] [-root | -sudouser <sudo_user_name> -sudopath <sudo_binary_path>] [-notify [-cc <user_list>]] [-asmclientdata <data_path>] [-gnsclientdata <data_path>]
[-clustermanifest <data_path>] [-softwareonly] [-local] [-inventory <inventory_path>] [-targetnode <target_node_name>] [-agpath <read_write_path> -aupath
<gold_image_path>] [-setupssh] [-useractiondata <user_action_data>] [-help <options>]
-help [REMOTEPROVISIONING|STORAGETYPE|ADMINDB|POLICYDB|DBWITHPQPOOLS|DBTEMPLATE|PDB|GRIDHOMEPROV|SWONLYGRIDHOMEPROV|STANDALONEPROVISIONING] Typical options (context

sensitive) for various use cases
-workingcopy <workingcopy_name> Name of the working copy to be created

-image <image_name> Image name from the configured images
-oraclebase <oraclebase_path> ORACLE_BASE path for provisioning Oracle database home or Oracle Grid Infrastructure home
-inventory <inventory_path> Location of Oracle Inventory
-path <path> The absolute path for provisioning software home (For database images, this will be the ORACLE_HOME)
-storagetype {NFS | LOCAL | RHP_MANAGED} Type of storage for the home
-user <user_name> Name of the user for whom the software home is being provisioned
-dbname <unique_db_name> Name of database (DB_UNIQUE_NAME) to be provisioned

-dbtype {RACONENODE | RAC | SINGLE} Type of database: RAC One Node or RAC or Single Instance
-datafileDestination <datafileDestination_path> Data file destination location or ASM disk group name
-dbtemplate <filepath> | <image_name>:<relative_file_path> Absolute file path for the template file or relative path to the image home directory on Rapid Home
Provisioning Server
-node <node_list> Comma-separated list of nodes on which database will be created
-serverpool <pool_name> Existing server pool name
-newpool <pool_name> Server pool name for pool to be created
-cardinality <cardinality> Cardinality for new server pool
-pqpool <pool_name> Existing PQ pool name
-newpqpool <pool_name> PQ pool name for pool to be created
-pqcardinality <cardinality> Cardinality for new PQ pool
-cdb To create database as container database
-pdbName <pdb_prefix> The pdbName prefix if one or more PDBs need to be created
-numberOfPDBs <pdb_count> Number of PDBs to be created
-client <cluster_name> Client cluster name
-ignoreprereq To ignore the CVU pre-requisite checks
-fixup Execute fixup script. Valid only for Grid Infrastructure provisioning.
-responsefile response file to be used to perform Oracle Grid Infrastructure provisioning
-clusternodes <node_name>:<node_vip>[:<node_role>][,<node_name>:<node_vip>[:<node_role>]...] Comma-separated list of node information on which Oracle Clusterware
will be provisioned
-groups "OSDBA|OSOPER|OSASM|OSBACKUP|OSDG|OSKM|OSRAC=<group_name>[,...]" Comma-separated list of Oracle groups to be configured in the working copy.
-root Use root credentials to access the remote node

-sudouser <username> perform super user operations as sudo user name
-sudopath <sudo_binary_path> location of sudo binary
-notify Send email notification
-cc <users_list> List of users to whom email notifications will be sent, in addition to owner of working copy
-asmclientdata <data_path> File that contains the ASM client data

-gnsclientdata <data_path> File that contains the GNS client data
-clustermanifest <data_path> Location of Cluster Manifest File
-local Perform Grid Infrastructure software-only provisioning on the local node.
-softwareonly Perform Grid Infrastructure software-only provisioning.
-targetnode <node_name> Name of a node in a remote cluster with no Rapid Home Provisioning Client
-agpath <read_write_path> Read-write path for OLFS-based Oracle home.
-aupath <gold_image_path> Gold image path for OLFS-based Oracle home
-setupssh sets up passwordless SSH user equivalence on the remote nodes for the provisioning user
-useractiondata <user_action_data> Value to be passed to useractiondata parameter of useraction script
Provide an Oracle Home to RHP Client available as "oracle" user making it available "locally" (as 'grid' user from RHP Server)
example:
[grid@oda101 ~]$ rhpctl add workingcopy -workingcopy WC_OraDb11204_home1 -image OraDb11204_home1 -oraclebase /u01/rhp_base
11/11/23, 9:10 PM Document 2097026.1
Note: the path defined by "-oraclebase" must be writable by the user defined by "-user" option
Time left:16:49:19
Creating a workingcopy, a new ACFS snapshot of the DB Home gold image will be created, example:
[root@oda101 ~]# acfsutil snap info /rhp_storage/images/iOraDb11204_home1977401

snapshot name: wWC_OraDb11204_home1
snapshot location: /rhp_storage/images/iOraDb11204_home1977401/.ACFS/snaps/wWC_OraDb11204_home1
RO snapshot or RW snapshot: RW
parent name: /rhp_storage/images/iOraDb11204_home1977401
snapshot creation time: Tue Sep 8 00:58:57 2015
number of snapshots: 1
snapshot space usage: 1614921728 ( 1.50 GB )
Database home provisioning (NFS)
Provide an Oracle Home to RHP Client available as "oracle" user making it available by "NFS" (HA-NFS) (as 'grid' user from RHP Server):
example:
[grid@oda101 ~]$ rhpctl add workingcopy -workingcopy WC_OraDb11204_home1 -image OraDb11204_home1 -oraclebase /u01/rhp_base -client odaremote-c -storagetype NFS -user
oracle
Database provisioning
Using RHP 'rhpctl add workingcopy', you can provide also a (RAC, RacOne, Single Instance) database (non-CDB, CDB).
Note: In case your RHP Client is an ODA (Oracle Database Appliance), it is not recommended to provision the database using "rhpctl add workingcopy -dbname"
- there is no flexibilty on having the redologs file on REDO diskgroup (SSD) and the recovery files on RECO dg.
- the db template used is a generic template and not specialized for ODA
- special enhancements are done on ODA to store the database on ACFS filesystem
Switch to Managed Homes
A DBA can switch databases from an Oracle home that was not provisioned using Rapid Home Provisioning (unmanaged Oracle home) to an Oracle home provisioned and managed by Rapid Home
Provisioning Server.
Assume the following:
Oracle Home installed at /u01/app/product/12.1.0/dbhome (currently an unmanaged home) on an RHP client cluster named odaremote. This home has one or more databases created from it.
A gold image named ORACLEDB12 is managed by the RHP server.
(Optionally) the gold image ORACLEDB12 has a working copy named myDB12HOME1 created on the client cluster odaremote from it.
Example:
RHP Client
Name Type Storage HomeName HomeLocation Version

----- ------ -------- -------------- ---------------- ----------
odasdb SINGLE ACFS OraDb12102_home2 <DB_HOME_4> 12.1.0.2.4(20831110,20831113)
----------------------------------------------------------------------------
RHP Server
[grid@oda101 ~]$ rhpctl query image
Image name: OraDb11203_home1
[grid@oda101 ~]$ rhpctl query workingcopy

Working copy name: WC_OraDb11203_home1
11/11/23, 9:10 PM Document 2097026.1
[grid@oda101 ~]$ rhpctl move database -sourcehome <DB_HOME_4> -client odaremote-c -patchedwc WC_OraDb12102_home1 -dbname odasdb
---------------------------------------------------------------------------- Time left:16:49:19

RHP Client
----- ------ -------- -------------- ---------------- ----------
odasdb SINGLE ACFS WC_OraDb12102_home1 <RHP_WC_HOME_for_home_4> 12.1.0.2.4(20831110,20831113)
Note: Moving a RAC database from un-managed Oracle Home to an RHP managed Oracle Home by default will be done in rolling mode
Database Patching
Similar to the above scenario, patching involves moving a database from one workingcopy to a new patched workingcopy.
Workingcopies are independent and multiple workingcopies can be created from the same gold image.
A typical scenario would involve creating an initial workingcopy from a base release. As new patches, PSUs are a good example, get released create a new workingcopy from your current gold image and
apply the PSU.
The latest workingcopy would be promoted as a new gold image from which new databases are created. Existing databases can then be moved to this latest gold image (which contains the current PSU).
This maintains a lineage of homes, allows for reverting to an older home if necessary, and keeps databases up to date, with regard to PSU application.
Assume you are moving all databases from a workingcopy named wcDB12PSU1 to a workingcopy named wcDB12PSU2, you would issue the command:
rhpctl move database -sourcewc wcDB12PSU1 -patchedwc wcDB12PSU2 –image DBIMGPSU2
This command creates a new ORACLE_HOME based on the patched image, if it does not exist, and then switches all Oracle databases from their current ORACLE_HOME location to the new
ORACLE_HOME.
By default, patching is performed in a rolling mode. Use the -nonrolling option to perform patching in non-rolling mode. The database is then completely stopped on the old ORACLE_HOME, and is then
restarted using the newly patched ORACLE_HOME.
For databases versions 12.1.0.1 or higher, the command rhpctl move database also executes any SQL commands required for database patching. For database versions earlier than Oracle Database 12c
Release 1, a message is displayed asking the user to run the SQL commands for database patching manually. If only a specific database is to have its ORACLE_HOME moved, include the -dbname switch:
rhpctl move database -sourcewc wcDB12PSU1 -patchedwc wcDB12PSU2 -dbname myDB
Standby Database Patching
Similar to the above scenario, standby database patching involves moving a database oracle home from one workingcopy to a new patched workingcopy without applying any dictionary patch.
On RHP Client a standby database is running under 12.1.0.2.0:

----- ------ -------- -------------- ---------------- ----------
STDBY SINGLE ACFS OraDb12102_home1 <DB_HOME_3> 12.1.0.2.0
From the RHP Server provide a new OH 12.1.0.2.3 (as 'grid' user):
rhpctl add workingcopy -workingcopy WC_OraDb121023_home1 -image OraDb121023_home1 -oraclebase /rhp_oracle_home -client odaremote-c -storagetype NFS -user oracle
Now, on RHP Client a new OH 12.1.0.2.3 is show:
Oracle Home Name Oracle Home version Home Location

---------------- ------------------- ------------
OraDb12102_home1 12.1.0.2.0 <DB_HOME_3>
WC_OraDb121023_home1 12.1.0.2.3(20299023) /rhp_oracle_home/product/12.1.0.2/WC_OraDb121023_home1
At this point we can move the remote standby from binaries 12.1.0.2.0 to 12.1.0.2.3 (patch the standby OH), as 'grid' user:
rhpctl move database -sourcehome <DB_HOME_3> -client odaremote-c -patchedwc WC_OraDb121023_home1 -dbname STDBY
The STDBY database is now attached to the new OH provided above:
11/11/23, 9:10 PM Document 2097026.1

----- ------ -------- -------------- ---------------- ---------- Time left:16:49:19
STDBY SINGLE ACFS WC_OraDb121023_home1 /rhp_oracle_home/product/12.1.0.2/WC_OraDb121023_home1 12.1.0.2.3(20299023)
Note: Rapid Home Provisioning is Standby Database aware. The standby database will be in mount state, no db dictionary patches are applied (as part of PSU) waiting them by redo shipping from the
primary DB.
Troubleshooting
- The RHP Server logs are located at the following location:
<oracle_base>/crsdata/<node_name>/rhp
- The RHP Client logs are located at the following location:
<gihome>/oc4j/j2ee/home/log/gh*.log
- In order to investigate what an srvctl command is doing:
export SRVM_TRACE=TRUE ; SRVCTL_TRACEFILE=/tmp/srv.trc
Depending on the nature of the error, enable additional tracing by defining SRVM_NATIVE_TRACE=TRUE and SRVM_JNI_TRACE=TRUE. This will produce additional jni trace information and is helpful to
isolate issue in the jni layer.
REFERENCES
https://docs.oracle.com/en/database/oracle/oracle-database/18/cwadd/rapid-home-provisioning.html#GUID-CCEC5960-EDA4-4A3F-9643-0CA308EA49AA
NOTE:2124960.1 - Rapid Home Provisioning (RHP) setup in "1-Click"
https://docs.oracle.com/en/database/oracle/oracle-database/12.2/cwadd/rapid-home-provisioning.html#GUID-CCEC5960-EDA4-4A3F-9643-0CA308EA49AA
NOTE:2126710.1 - RHP: Rapid Home Provisioning Server - Minimum Requirement
NOTE:2167541.1 - RHP (Rapid Home Provisioning): mnttest tool to test NFS 'export' and 'mount' functionalities
NOTE:2054804.1 - ODA (Oracle Database Appliance): How To Setup a Rapid Home Provisioning (RHP) Server and Client
Didn't find what you are looking for? Ask in Community...
Related
Products
Oracle Database Products > Oracle Database Suite > Oracle Database > Oracle Database - Enterprise Edition
Oracle Database Products > Oracle Database Suite > Oracle Database > Oracle Database - Enterprise Edition > Real Application Cluster
Oracle Cloud > Oracle Platform Cloud > Oracle Database Cloud Service > Oracle Database Cloud Schema Service
Oracle Cloud > Oracle Platform Cloud > Oracle Database Cloud Service > Oracle Database Exadata Express Cloud Service
Oracle Cloud > Oracle Infrastructure Cloud > Oracle Cloud at Customer > Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine)
Oracle Cloud > Oracle Platform Cloud > Oracle Cloud Infrastructure - Database Service > Oracle Cloud Infrastructure - Database Service
Oracle Cloud > Oracle Platform Cloud > Oracle Database Backup Service > Oracle Database Backup Service
Oracle Cloud > Oracle Platform Cloud > Oracle Database Cloud Exadata Service > Oracle Database Cloud Exadata Service
Oracle Cloud > Oracle Platform Cloud > Oracle Database Cloud Service > Oracle Database Cloud Service
Knowledge Categories
PLA-Support > Database > DB Foundation > ODA > DB: ODA_EST ( Primary )
KB Review > KB Review.Reviewed-Fixed
CMOS Migration > CMOS Migration.Large Document Valid
Document Attributes
Author: RCITTON.IT; Status: PUBLISHED(EXTERNAL)
Owner: RCITTON.IT Publisher: KCHAPMAN.UK
Alias: Content Type: TEXT/X-HTML
Distribution: EXTERNAL Visibility: EXTERNAL
Created By: RCITTON.IT Created: Jan 14, 2016
Modified By: DTHORP.US Modified: Jun 13, 2023
Reviewed By: KCHAPMAN.UK Reviewed: Nov 11, 2023
Source: AWIZ Exception: No
Priority: 3
11/11/23, 9:10 PM Document 2097026.1
Comments Time left:16:49:19
Edit Comment Type Status Priority From To Modified By Created Modified

My Oracle Support Feedback Customer Feedback REJECTED 3 CUSTFEED.WW OWNER Jul 13, 2023 Jul 14, 2023
-version parameter is needed if the client version is lower than RHPS Internal Feedback IMPLEMENTED 2 OWNER May 5, 2022 May 10, 2022
rhp command running for incorrect node Internal Feedback REJECTED 2 OWNER Mar 31, 2022 Apr 7, 2022
client version support for 12.2 + Internal Feedback REJECTED 2 OWNER Jun 17, 2020 Nov 30, 2020
My Oracle Support Feedback Customer Feedback REJECTED 3 CUSTFEED.WW OWNER Mar 26, 2018 Mar 27, 2018
Need to update the example. Internal Feedback REJECTED 2 OWNER Feb 26, 2018 Feb 28, 2018
Back to Top
Copyright (c) 2023, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

Document 2097026.1

Uploaded by

Copyright:

Available Formats

Document 2097026.1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Document 2097026.1

Uploaded by

Copyright:

Available Formats

11/11/23, 9:10 PM Document 2097026.

PowerView is Off Parmanto (Available) Profile (2) Help

Copyright (c) 2023, Oracle. All rights reserved. Oracle Confidential.

In this Document Was this document helpful?

RHP Server: Create client data file

Information Center: Data Warehousing [1487754.2]

An existing working copy can be promoted to a gold image.

A working copy is an instantiation of an Oracle database software home

11.2.0.* (Oracle Database 11g)

Using Rapid Home Provisioning

# $GRID_HOME/bin/srvctl status mgmtdb

# $GRID_HOME/bin/srvctl add gns -vip {<vip_name> | <ip>}

Creating a Rapid Home Provisioning Server

# service rpcbind status

# service nfs status

# service nfslock status

Note: on OL5, the "rpcbind" service is called "portmap"

RHP Server: Create the Rapid Home Provisioning Server resource

# srvctl stop rhpserver

Ignore a message similar to "Rapid Home Provisioning Server is not running".

# srvctl remove rhpserver

# $GRID_HOME/bin/srvctl add rhpserver -storage <rhp_acfs-storage_path> -diskgroup <disk_group_name>

Note: The storage path "/rhp_storage" is automatically created by srvctl

ALTER DISKGROUP data SET ATTRIBUTE 'compatible.advm' = '12.2';

You can check the status for rhp server doing:

# $GRID_HOME/bin/srvctl status rhpserver

[root@oda101 ~]# mount

RHP Server: Start the Rapid Home Provisioning Server resource

Issue the following command (as 'root' user):

# $GRID_HOME/bin/srvctl start rhpserver

RHP Server: HA-VIP setup

$ $GRID_HOME/bin/srvctl config havip

# $GRID_HOME/bin/srvctl add havip -id id -address {host_name | ip_address}

RHP Server: Create client data file

$GRID_HOME/bin/rhpctl add client -client <client_cluster_name> -toclientdata <path>

[grid@oda101 ~]$ ls –al /home/grid/stormcloud-cluster.xml

At this time you should configure the RHP Client.

RHP Client setup

The command “srvctl add rhpclient” has two optional arguments:

Scenarios to Use Rapid Home Provisioning

Adding Gold Images to the Rapid Home Provisioning Server

- Promote an existing workingcopy to a gold image using the following command:

rhpctl add image –image <image name> -workingcopy <workingcopy name>

Oracle Home Name Oracle Home version Home Location

$ $GRID_HOME/bin/rhpctl import image -image OraDb11204_home1 -path <DB_HOME_2> -imagetype ORACLEDBSOFTWARE

$ $GRID_HOME/bin/rhpctl import image -image OraDb12102_home1 -path <DB_HOME_3> -imagetype ORACLEDBSOFTWARE

Database Home provisioning

Database home provisioning (LOCAL)

-help [REMOTEPROVISIONING|STORAGETYPE|ADMINDB|POLICYDB|DBWITHPQPOOLS|DBTEMPLATE|PDB|GRIDHOMEPROV|SWONLYGRIDHOMEPROV|STANDALONEPROVISIONING] Typical options (context

-workingcopy <workingcopy_name> Name of the working copy to be created

-dbname <unique_db_name> Name of database (DB_UNIQUE_NAME) to be provisioned

-root Use root credentials to access the remote node

-asmclientdata <data_path> File that contains the ASM client data

[root@oda101 ~]# acfsutil snap info /rhp_storage/images/iOraDb11204_home1977401

Database home provisioning (NFS)

Switch to Managed Homes

Assume the following:

Name Type Storage HomeName HomeLocation Version

[grid@oda101 ~]$ rhpctl query workingcopy

---------------------------------------------------------------------------- Time left:16:49:19