Scheduling a Data Fix Deployment Using Packager

Learn how to schedule a Data fix (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 Data Fix Execution is down.

To initiate Data fix activity:
  1. In the dashboard, click the hamburger menu ( three horizontal lines) at the top-left corner.
  2. In the navigation pane, under Data Fix, 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 Data Fix 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 on the RFC Type box, so the RFC Type and RFC Sub Type are autopopulated.
    3. In the Selected File Names field, click the plus icon.
    4. In the Select Files from the list below screen, select all Data fix that you want to include in the RFC, and then click Done.

      The Selected File Name box at the top of the list displays all the selected Data fix files.

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

      In the Initiate Data Fix page, the Selected File Names field is automatically populated with the file names, while the Summary field is automatically populated with the number of files 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 asking you to acknowledge that you accept 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. Click Customer Note to add an action plan or any other relevant information you want included in the RFC.
    9. Select the Hot Backup check box to enable/disable the Hot backup for Non Prod instances. For Production instances, this check box is automatically selected and cannot be deselected.

      This Provision of Hot backup selection is only available for the ACE Data Fix option.

      Also, you can configure the Hot backup option as part of one time setup. Under SSP Preferences à General Preferences, you can select ProdBackupOption as Y or N (Default is Y).

      If you select Y while creating RFC, Hot backup option is auto selected and greyed out for Prod instances. Similarly, Hot backup option is not auto selected and allows you to select the backup option for Non-Prod instance (Existing Mechanism).

      If you select N while creating RFC, Hotback up option is auto selected, but editable where you can unselect the Hot backup option for Prod instances. Similarly, Hot backup option is not auto selected and allows you to select the backup option for Non-Prod instance.

    10. Click Submit.

      The Schedule Execution screen opens.

    11. If you click Not Now, you are returned to the listings in the Initiate Data Fix page.
    12. If you click Yes, the RFC will be scheduled for execution in 15 minutes.
    13. 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 RFCs are listed in descending order of the run completion date.

    If you click the RFC link, you are directed to the MOS RFC Page where you can view all the updates.

    Additionally, for Dynamic Data fix files with Input parameters, a new section is updated in the RFC (Summary of Actions) is displayed. This Summary of Actions includes a list of Dynamic Data fix files in order of execution along with input values passed by user during file upload, which helps you to validate the sequence of file execution along with input data.