Creating a Fleet Patching and Provisioning Server

The Fleet Patching and Provisioning Server uses a repository that you create in an Oracle ACFS file system in which you store all the software homes that you want to make available to clients and targets.

Note:

When you install Oracle Grid Infrastructure, the Oracle Fleet Patching and Provisioning Server is configured, by default, in the local mode to support the local switch home capability. If you must configure the general Oracle Fleet Patching and Provisioning Server product, then you must remove the current local-mode Oracle Fleet Patching and Provisioning Server.

Use the Oracle ASM configuration assistant (ASMCA) to create an Oracle ASM disk group on the Fleet Patching and Provisioning Server to store software.
```
$ Grid_home/bin/asmca
```
Because this disk group is used to store software, Oracle recommends a minimum of 100 GB for this disk group.

Note:

You must set Oracle ASM Dynamic Volume Manager (Oracle ADVM) compatibility settings for this disk group to 19.0.
Provide a mount path that exists on all nodes of the cluster. The Fleet Patching and Provisioning Server uses this path to mount gold images.
```
$ mkdir -p storage_path/images
```
Check if Grid Infrastructure Management Repository (GIMR) is configured on your cluster.
```
$ srvctl status mgmtdb 
Database is enabled
Instance -MGMTDB is running on node myhost01
```
If GIMR is not configured on your cluster, then as the grid user, add a GIMR to your cluster.
1. For Oracle Database 19c Release Update (19.6) or earlier releases:
```
$ $ORACLE_HOME/bin/mgmtca createGIMRContainer [-storageDiskGroup disk_group_name]
```
2. For Oracle Database 19c Release Update (19.7) or later releases:
```
$ $ORACLE_HOME/bin/mgmtca createGIMRContainer [-storageDiskLocation disk_location]
```

As the root user, add the Grid Naming Service Virtual IP Address (GNS VIP) without zone delegation.

# srvctl add gns -vip myhost-gnsvip3
# srvctl start gns
# srvctl status gns
GNS is running on node myhost01.
GNS is enabled on node myhost01.

Remove any existing local automaton from your cluster.
```
# srvctl stop rhpserver
# srvctl remove rhpserver
```

Create the Fleet Patching and Provisioning Server resource.

# Grid_home/bin/srvctl add rhpserver -storage storage_path
    -diskgroup disk_group_name

Start the Fleet Patching and Provisioning Server.
```
$ Grid_home/bin/srvctl start rhpserver
```

After you start the Fleet Patching and Provisioning Server, use the Fleet Patching and Provisioning Control (RHPCTL) utility to further manage Fleet Patching and Provisioning.