Update Databases Using Fleet Maintenance

Fleet Maintenance Operations Using the UI

To begin performing updates using Fleet Maintenance
- From the Fleet Maintenance Hub, navigate to the Target Patch Compliance tile. In the table below locate a database to update and click on Update under the Target Compliance column. This will preselect the database target, and move you into the Targets screen.
- From the Fleet Maintenance Operator UI, in the Targets screen, select the databases you wish to perform the operations upon by check marking them. You can filter to find the databases by filtering via: Image, Target Type (Database Instance or Cluster Database), Operation (Update, Upgrade or Upgrade Non-CDB as Pluggable Database); or the Filter text box.
  Starting with Oracle Enterprise Manager 24ai Release 1 Update 2 (24.1.0.2), you can use Global Filters in the Fleet Maintenance Operator Wizard used for updates. Global Filters allow you to further filter a search by filtering by target family, target type, and with Enterprise Manager user defined properties. To use click on the filter icon, this will open the Filters slide-out. Set the filters you wish and click on Apply.
Once all databases you wish to perform Fleet Maintenance on are check marked, click Next.
Within the Operations screen you check mark the operation or operations to be performed under Maintenance Tasks:

Note:
You can also click on a link on each operation, this will also tell you what targets the operation is applicable to.
- Under Software Deployment: Enter the Destination Oracle Home, and enter the Home Name Prefix if your environment requires a custom Oracle Home name prefix, this allows for the ability to discover Oracle Homes with custom name post deployment. If the home name prefix is not specified, the default value will be used. This feature is available starting with Oracle Enterprise Manager 13.5 Release update 20 (13.5.0.20).
  Set a Start Schedule. The schedule you enter must reflect across all applicable selected targets. You can select for the operation to start Immediately or Later at a time of your choosing.
  
  Note:
  If you select multiple databases running on different homes from the same host, the Fleet Management UI will only submit deployment for one database. This is because the Oracle Home path needs to be unique per source Oracle Home.
- Migrate the Listener: Select a start time. Immediately/Auto the task will begin immediately or as soon as the previous task finishes. Later, enter a start time of your choosing that reflects the time usually taken for software deployment in your environment.
  
  Note:
  All times are set in the Management Server Time Zone. You cannot set a Maintenance Task to run immediately if there are preceding tasks.
- Update Database: Select a start time. Immediately/Auto the task will begin immediately or as soon as the previous task finishes. Later, enter a start time of your choosing that reflects the time usually taken for software deployment in your environment.
Starting with Oracle Enterprise Manager 24ai Release 1 Update 9 (24.1.0.9), Software Deployment, Migrate Listener, Update, and Upgrade operations are supported only for targets subscribed to images based on 19c or later. If a target is subscribed to an image earlier than 19c, Enterprise Manager skips that target and does not perform the operation.
Enter the Credentials for Normal Host, Privileged Host and Database Credentials. You can select whether to use a Named or Preferred credential. Preferred credentials need to be set at the Oracle Home and target database before you can selecting them in the UI. For more information on preferred credentials in Fleet Maintenance see: Preferred Credential Support for Fleet Maintenance.

Note:
For Windows deployments use Windows Security Credentials.
Under Options you can set the following:
- Work Directory: Enter the work directory where the files will be stored.
- Skip Cluster Verification Utility Checks: Select to skip the Prerequisite Checks and/or Cluster Verification Utility Check.
- Dispatch Location: Enter a read-only location to use pre-staged dispatcher and fleet scripts.
- Listener Options: Select whether or not to Force the listener.
  
  Note:
  This option is only available if Migrate Listener is selected.
- Ignore datapatch ORA errors: Optionally enter a comma-separated list of Oracle error codes to ignore during the datapatch step of a database update, for example, ORA-00001,ORA-00002. For Oracle RAC database updates, this field appears in the Update Cluster Database section. If you leave the field empty, the existing datapatch error-handling behavior is unchanged. Invalid values display a validation message below the field.
  This option applies to single-instance and Oracle RAC database updates performed using native Fleet Maintenance. It is not available for Oracle Fleet Patching and Provisioning (FPP) operations.
- Custom Scripts: Select the optional custom scripts you wish to run by clicking on Add, the Fleet Management UI is set to the default location for custom scripts. If your scripts are located in a different section Set the Stage, Script Location. Lastly select the check mark if you wish to Run as Root.
  For more information on custom scripts, see Custom Pre and Post Scripts for Fleet Operations
  
  Note:
  Custom scripts are also supported for Exadata Fleet Maintenance Deploy and Update operations. For the applicable script stages, execution hosts, and credential requirements, see Custom Pre and Post Scripts for Exadata Patching.
Once all options have been entered click Next.
In the Review screen, verify all options entered in the previous screen.
In this screen you can View JSON or Save JSON of the operations to be performed.

Click Validate to perform a Quick or Full validation of your Fleet Maintenance Operation before submitting. Validation results are reported on a per target basis, for a Full validation a Deployment Procedure is submitted for each target. Each target will have a link available to see in detail the results of the Validate Deployment Procedure.

Note:
If you encounter a Destination home not found error when performing a Quick validation you will need to perform a Runbook Session. Navigate to Enterprise, then Monitoring, then Runbook Session. Select Start Universal Runbook Session, and initiate the session labelled Fleet Maintenance Operation Failed: Home Deployment not recognized. This will help identify the root cause of this issue.
To start your Fleet Maintenance operation, click Submit.

Note:
Starting with Enterprise Manager 13.5 Release update 19 (13.5.0.19), before and after a UPDATE/ROLLBACK operation on single instance or RAC databases, the deployment procedure activity logs include the number of invalid objects found.

Data Guard Update Operations Using the UI

To begin performing Fleet Maintenance operations on Data Guard enabled targets, in the Targets screen, select the databases you wish to perform the operations upon by check marking them. Data Guard enabled databases will show an additional Role category in the table, with Primary and Physical Standby values assigned to each respective database.
You can filter to find the databases by filtering via: Image, Target Type, Operation, or the Filter text box.

Starting with Oracle Enterprise Manager 24ai Release 1 Update 2 (24.1.0.2), you can use Global Filters in the Fleet Maintenance Operator Wizard used for updates. Global Filters allow you to further filter a search by filtering by target family, target type, and with Enterprise Manager user defined Target Groups, and Target Properties. To use click on the filter icon, this will open the Filters slide-out. Set the filters you wish and click on Apply.

Note:
If you had pre-loaded Global Filters from the Fleet Maintenance Hub screen, these will be loaded into the Fleet Maintenance Operator Wizard.

Once all databases you wish to perform Fleet Maintenance on are check marked, click Next.

Note:
You can select only Primary or only Standby databases in a Fleet Maintenance session, but not both at the same time for the same session. For a Data Guard configuration, patch all standby databases before patching the primary database.
Within the Operations screen you check mark the operation or operations to be performed under Maintenance Tasks:

Note:
You can also click on a link on each operation, this will also tell you what targets the operation is applicable to.
1. Software Deployment: Enter the Destination Oracle Home and set a Start Schedule. The schedule you enter must reflect across all applicable selected targets. You can select for the operation to start Immediately or Later at a time of your choosing.
  
  Note:
  If you select multiple databases running on different homes from the same host, the Fleet Management UI will only submit deployment for one database. This is because the Oracle Home path needs to be unique per source Oracle Home.
2. Migrate Listener: Select a start time. Immediately/Auto the task will begin immediately or as soon as the previous task finishes. Later, enter a start time of your choosing that reflects the time usually taken for software deployment in your environment.
3. Update Database: Select a start time. Immediately/Auto the task will begin immediately or as soon as the previous task finishes. Later, enter a start time of your choosing that reflects the time usually taken for software deployment in your environment.
Note:
All times are set in the Management Server Time Zone. You cannot set a Maintenance Task to run immediately if there are preceding tasks.
Enter the Credentials for Normal Host, Privileged Host and Database Credentials. You can select whether to use a Named or Preferred credential. Preferred credentials need to be set at the Oracle Home and target database before you can selecting them in the UI. For more information on preferred credentials in Fleet Maintenance see: Preferred Credential Support for Fleet Maintenance.

Note:
For Windows deployments use Windows Security Credentials.
Under Options you can set the following:
- Work Directory: Enter the work directory where the files will be stored.
- Skip Cluster Verification Utility Checks: Select to skip the Prerequisite Checks and/or Cluster Verification Utility Check.
- Under Software Deployment:
  - Run CVU From Oracle Home: This will be set to default NO.
  - Custom CVU Component: Enter CVU component location in Software Library
  - Pre-staged Location for Root Scripts: Specify a read-only location to use pre-staged dispatcher as well as fleet scripts
  - Data Guard Options: You can select Standby Auto Deploy for automatic deployment of software on standby host.
- Migrate Listener allows you to set the Listener Options: Select whether or not to Force the listener.
  
  Note:
  This option is only available if Migrate Listener is selected.
- Update Database allows you to set the Data Guard Options with the following options:
  - Ignore Standby Prerequisite: Specify to disable verification check if the Standby is on the same image version where the Primary is being moved to.
  - Enable Data Guard: Specify if the standby is managed by Data Guard.
  - Enable FSFO: Enable Fast-Start Failover (FSFO). FSFO can be enabled when DG broker is on.
  - Startup Standby: Specify to startup the Standby databases after primary is patched. Used if you selected to keep the standby database down post patching. When selecting this, set the standby startup option: Open, Mount, No Mount, Read Only, Read Only With Apply.
- Custom Scripts: Select the optional custom scripts you wish to run by clicking on Add, the Fleet Management UI is set to the default location for custom scripts. If your scripts are located in a different section Set the Stage, Script Location. Lastly select the check mark if you wish to Run as Root.
Once all options have been entered click Next.
In the Review screen, verify all options entered in the previous screen.
In this screen you can View JSON or Save JSON of the operations to be performed.
Click on Validate to perform a Quick or Full validation of your Fleet Maintenance Operation before submitting. Validation results are reported on a per target basis, for a Full validation a Deployment Procedure is submitted for each target. Each target will have a link available to see in detail the results of the Validate Deployment Procedure.
To start your Fleet Maintenance operation, click Submit.

Data Guard Rolling Upgrade Operations Using the UI

Before performing a Data Guard rolling upgrade using Fleet Maintenance, review the About Rolling Upgrades and Prerequisites to Rolling Upgrades sections. The concepts and prerequisites described in these sections also apply to Data Guard rolling upgrades performed using Fleet Maintenance.

In the Targets screen, select the Data Guard configuration database systems you want to upgrade, and click Next.
In the Operations screen, select Rolling Upgrade. For Start, select Immediately/Auto to start immediately, or Later and specify a start time. Click Next.
Enter the credentials for Normal Host, Privileged Host, and Database Credentials. Select a Named or Preferred credential. If prompted, enter the Source Wallet Password.
Under Options, specify the following settings for the Data Guard rolling upgrade:
- Work Directory: Enter the directory where Fleet Maintenance stores the files.
- Skip Cluster Verification Utility (CVU) Checks: Select whether to skip the prerequisite checks and/or CVU checks.
- Recompile Invalid Objects: Specify whether to recompile invalid objects during the upgrade. Recompiling invalid objects increases the time required for the upgrade but can minimize latency caused by on-demand automatic recompilation at runtime.
- Degree of Recompile Parallelism: Specify the degree of parallelism for recompiling invalid objects. Parallel recompilation can reduce the time required. The degree of parallelism must not exceed the number of CPUs on the database host. This option applies only when Recompile Invalid Objects is set to Yes.
- Stop After First Switchover: Specify whether to stop the rolling upgrade procedure after the first switchover. This can avoid the downtime associated with the second switchover, especially when the primary and standby infrastructures are provisioned similarly to handle the production workload. If selected, the standby database that was in place before the rolling upgrade becomes the new primary database when the rolling upgrade completes.
- Swap Monitoring Templates: Specify whether to swap monitoring settings between the primary and standby databases after the switchover. Select this option only with Stop After First Switchover.
- Swap Scheduled Jobs: Specify whether to move transferable jobs between the primary and standby databases after the switchover. Only Backup, RMAN Script, and SQL Script jobs that use global named credentials or preferred credentials are transferred. Select this option only with Stop After First Switchover.
- Pause Before First Switchover: Specify whether to pause the rolling upgrade procedure before the first switchover. This gives you time to plan for the downtime and resume the workflow when appropriate. The default is No.
- Enable Debug Output: Specify whether to enable debug output in the rolling upgrade procedure.
- Upgrade Timezone: Specify whether to upgrade the time zone during the upgrade process.
Under Custom Scripts, click Add to specify optional scripts for the rolling upgrade.

Note:
For Data Guard rolling upgrades, only pre-upgrade and post-upgrade SQL scripts are supported.

Click Next.
In the Review screen, verify all options entered in the previous screens. Click Show JSON to view the operation details in JSON format, or Save JSONs to save the JSON files.
Click Validate to perform a Quick or Full validation of your Fleet Maintenance operation before submitting.
To start your Fleet Maintenance operation, click Submit.