Oracle Cloud Infrastructure Documentation

Scheduling a Custom Patch Deployment Using Packager

Learn how to schedule a custom patch (CEMLI Patch or ACE Data Fix) deployment using Packager. The ACE Data Fix option can be used to promote data fixes that do not require manual intervention or input parameters during execution.

Note

You must run a test deployment of each new RFC in a non-production environment before attempting to deploy the RFC in a production environment.

You must use MOS, rather than Packager, to modify the RFC in the following situations:

  • The Packager scheduling operation failed for some reason - for example, a Web service failure or application integration issue. This results in the creation, but not scheduling, of the RFC.

  • Oracle Automated CEMLI Execution is down.

To initiate CEMLI activity:
  1. In the dashboard, click the hamburger menu (three horizontal lines) at the top-left corner.
  2. In the navigation pane, under CEMLI, click Executions.

    All the existing executions are displayed.

  3. To refresh the list, click the refresh icon.
  4. To search for an execution, type a few letters of the search criteria in the search text box, and press Enter.

    You can search by entering a few letters of your search criteria. This is a free text search.

  5. Click Initiate CEMLI Activity.
  6. In the Initiate CEMLI page, set the following:
    1. From the Target list, select the Environment where the patch will be deployed. This list is populated with all the environments associated with the Support Identifier (SI).
    2. Click the RFC Type box, so the RFC Type and RFC Sub Type are autopopulated.
    3. In the Selected Patch Numbers field, click the plus icon.
    4. In the Select Patch from the list below screen, select all patches that you want to include in the RFC, and then click Done.

      The Selected Patch Numbers box at the top of the list displays all the selected patches.

    5. To search for a patch to include, enter a search criteria in the free text search box at the top.

      In the Initiate CEMLI page, the Selected Patch Numbers field is automatically populated with the numbers of selected patches. The Summary field is automatically populated with the number of patches to be applied.

    6. (Production RFCs only) Click Search RFCs.

      The Search and Select Existing RFC dialog box opens, allowing you to select the number of an RFC that was already successfully deployed on a non-production instance.

      If you do not provide this information and want to directly deploy a change to a production environment, the Risk Statement dialog box opens, and asks you to acknowledge that you are deploying untested code directly to a production instance.

    7. Select the Accept Risk check box to acknowledge your acceptance of the risk of applying CEMLIs and read the risk statement before the RFC can be created.
    8. Select the Auto Skip check box to complete the RFC despite any custom code failure during patch application by automatically skipping the failed adworker.
    9. Select the Auto Stop check box to stop RFC execution if there is any custom code failures during patch application, and terminate the execution.
    10. Select the Bounce Options at the host level or instance level. Select the values from the list corresponding to the Bounce services that need to be restarted.

      (Optional) If you want to delete the data in the Apache cache module, leave the Clear Apache Cache check box selected (default). Also for EBS 12.2 and above, if you want to bounce Managed Server, leave the Managed Server check box selected (default for EBS 12.2 and above). As a new feature, All the apps components can be bounced for all MTs by selecting All Apps option through the Bounce Services list.

      The Bounce field is automatically filled in with data on the host and service that need to be restarted. If any service needs to be restarted after the patch is applied, the estimated time listed in the Estimated Time to Apply Change field is automatically increased by an hour.

    11. Click Customer Note to add an action plan or any other relevant information you want included in the RFC.
    12. Click Submit.

      The Schedule Execution screen opens.

    13. If you click Not Now, you are returned to the listings in the Bounce page.
    14. If you click Yes, the RFC is scheduled for execution in 15 minutes.
    15. If you click Pick Future, you are taken to the Details page.

      The RFC is created and displayed in the Executions page.

  7. To view details of an RFC, click that RFC from the list.

    All non-production RFCs are listed in descending order of the run completion date.