Update Databases Using Fleet Maintenance

You can now perform Migrate, Deploy and Update operations from the User Interface page using a simple intuitive process that guides you through setting up and performing Fleet Maintenance to your Oracle Database targets.

Note:

For DST Fleet Maintenance patching see MOS Note 2725653.12725653.1

1. 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.

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

2. 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.
3. 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.
4. 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.
   • 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 custon scripts see: Custom Pre and Post Scripts for Fleet Operations

   Once all options have been entered click Next.
5. 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.
6. To start your Fleet Maintenance operation, click Submit.

Data Guard Update Operations Using the UI

1. 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.

   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.
2. 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.
3. 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.
4. 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 sandby 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.
5. 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.
6. To start your Fleet Maintenance operation, click Submit.