Oracle Fleet Patching and Provisioning Local Mode

About Oracle Fleet Patching and Provisioning Local Mode

Oracle Fleet Patching and Provisioning Local Mode is enabled by default with Oracle Grid Infrastructure and provides local-cluster patching for Oracle Grid Infrastructure and Oracle AI Database without requiring a Java container, separate server, or additional setup. It supports clustered Oracle Database 11.2.0.4, 12.1.0.2, 12.2.0.1, and later releases, while standalone environments support only Oracle Database 18c and later database-home patching. Patching uses deployed source and destination homes with the rhpctl move gihome or rhpctl move database commands, and configuring a central Oracle FPP Server requires removing the Local Mode configuration.

Performing Patching Using Oracle FPP Local Mode

Patching with Oracle FPP Local Mode consists of deploying new Grid Infrastructure and database homes, switching to them with rhpctl move gihome and rhpctl move database, and optionally rolling back by reversing the Grid Infrastructure home move. Only one patching operation can run at a time, and the command must be initiated from a single node; completion propagates automatically to other nodes. If the initial command fails, it must be rerun from the same node where it began.

Using Oracle Update Advisor in Oracle FPP Local Mode

Oracle Update Advisor in FPP Local Mode allows administrators to register a user, evaluate an Oracle home against an update policy, receive patch recommendations, generate a patched image, monitor the evaluation request, and download the resulting gold image. The downloaded image can then be deployed and used for patching according to the Local Mode procedure. With Oracle Restart, Local Mode supports patching the Oracle AI Database home but not the Oracle Grid Infrastructure home.

Storing User-Action Scripts in OCR for Oracle FPP Local Mode

Starting with Oracle Grid Infrastructure 26ai, user-action script locations for Oracle FPP Local Mode can be stored in the Oracle Cluster Registry using the rhphelper command. This avoids specifying the script location for every Grid Infrastructure or Oracle AI Database patch operation, and the stored value is readable by both the grid and oracle users. The ualoc parameter can optionally override the OCR-defined location for an individual patch operation, while an empty location resets the stored value.

Switching from Oracle FPP Local Mode to Oracle FPP Central Server

Oracle FPP Local Mode starts automatically when a patching command is invoked and its dependent resources are configured during startup. To switch to Oracle FPP Central Server mode, stop and remove the local rhpserver resource with srvctl, then follow the central-server creation procedure to deploy the Oracle FPP Server for managing clients and rhpclient-less targets.
Read More: Switching from Oracle FPP Local Mode to Oracle FPP Central Server