The FPP Server is a repository for fours types of data:
• Gold images
• Working copies
• Client information
• Metadata related to users, roles, and permissions

An FPP server can use ASM to store the images as well as the file system. Let’s walk through the steps to set up an FPP server in a grid home, which assumes the grid infrastructure is installed with ASM.
First create a disk group in ASM for images using the configuration assistance or log into the ASM instance and use SQL to create the disk group:

$ $GRID_HOME/bin/asmca

Or do the following:
$ . oraenv +ASM
SQL> create diskgroup fppimage disk ‘/dev/oracleasm/disk/disk_fpp01’;

A mount point is needed on the nodes of the cluser:
$ mkdir -p /u03/fppstorage/images

Check to see whether the Grid Infrastructure Management Repository is configured:
$ srvctl status mgmtdb

If not configured and running, it can be in the grid home with the following:
$ mgmtca createGIMRContainer -storageDiskLocation fppimage

Create the FPP Server resource:
$ srvctl add rhpserver -storage /u03/fppstorage/images -diskgroup fppimage $ srvctl start rhpserver

The overview of steps for fleet patching and provisioning are as follows:

1. Create reference environments with the required set of patches.
2. Create gold images and set the version.
3. Subscribe database and grid homes to a gold image.
4. Deploy the image to a new Oracle home.
5. Switch targets from the old to the new Oracle home.

To create a gold image, you can either import or add an image with rhpctl commands. Here is an example:
$ rhpctl import -image DB23_1

The parameters would include the type of image, so if it is Oracle Database or grid, and you can create your own image types along with the built-in image types. By default the type of image is the Oracle Database, but other types would need to be specified using the parameter -imagetype.
The built-in base image types are as follows:
• ORACLEDBSOFTWARE
• ORACLEGISOFTWARE
• ORACLEGGSOFTWARE
• EXAPATCHSOFTWARE
• SOFTWARE

Provisioning the gold image is done with the same rhpctl command but using the workingcopy parameter. This is an example of how to do this on a local client:
$ rhpctl add workingcopy –workingcopy DB_HOME_231 -image DB23_1 -storagetype LOCAL

Or for client:
$ rhpctl add workingcopy -image DB23_1 -path /u01/app/oracle/ product/23.1.00/db23c -workingcopy DB_HOME_23c -client client_042 -oraclebase /u01/app/oracle

Note enterprise Manager software is another way to implement fleet patching and provisioning. it can assist in these steps and configuration. it provides information for the reference environment with the available patches.

By using the emcli command, you can create the gold image. there are requirements to set up the Fpp server and enterprise Manager, but you can see with this example some of the commands that help create and manage images.this creates a new version:
$ emcli db_software_maintenance -createSoftwareImage -input_file=”data:/home/user/input_file”

here is an example to get a list of images in production:
$ emcli db_software_maintenance -getImages

In creating images, you will have to apply the patches to sources and create another image with the patched version and verify the image.
Once the images have been added to the FPP Server, they can be queried:
$ rhpctl query image

Then get the specific details from one of the images:
$ rhpctl query image -image DB23_1