1 |
In the CSR window, select the Objects tab. |
2 |
4 |
Click Add Object. |
5 |
Select File | Save, or click the Save toolbar button. |
1 |
Select the Patch Approvals tab. Then click My Patch Approvals. |
• |
When you click All Patch Approvals, the tab displays all the patches that are awaiting approvals from other users. With proper security rights, you can make patch approvals for other users. |
2 |
Click in the Status column for each patch that you want to approve and select Approved. If you do not approve the patch, select Rejected. |
3 |
Click Save. |
c |
Click Save. |
You can also approve patches in the Approval List for Target Environment window.
1 |
2 |
In the approval list, double-click your name and in the pop-up menu select Approve if you approve the patch. If you do not approve the patch, select Reject. |
5 |
NOTE: With proper security rights, you can make approvals for other users. You can also unapprove all approvals by clicking Unapprove All. This allows you to deselect Ready to Migrate for the target environment. When you override another user’s approval, Stat records you as the approver, not the user originally assigned to make the approval. |
If you want to notify users about patches that are still pending their approval, you can email a message predefined by system administrators. In the tree list of approvers, select the node representing the user or class that you want to notify and click Email. An email job request is sent to the Stat Central Agent, which processes the request and sends an email to the user you selected or to each member of the selected class. A “@” sign is displayed for that approver node in the Envelope field of the Approval List tab.
System administrators can also configure the Stat Central Agent to include links in the reminder message that the recipient can click to approve or reject the patch application. This sends an email back to the Stat Central Agent, which processes the response email and changes the approval status to Approve or Reject, depending on which link the approver selected.
NOTE: When an approval status is changed by responding to a reminder message, the Update Date field in the Approval List window will be automatically populated and the Update By field will display the value, Via Email. |
Approval notification reminder messages can also be sent for workflow status transfers and migrations. For more information, see the book Stat System Administration, Chapter 7, “Email Configuration”.
If there is at least one active R12.2 environment or higher (meaning that there is an “AD” record in the list of imported products with code level of “C” or higher), a Patch Cycle button is displayed on the Patch Inventory tab on the Oracle Apps Management Console window. For these environments, patching is done on the Patch Edition of the environment. A utility called adop is used to manage patch cycle phases, apply patches, and run impact analyses. The Patch Cycle button is used to schedule any phase of a patch cycle but cannot be used to schedule Apply Patch or Patch Impact requests (which are scheduled the same way as other environments through the Schedule button.)
In the Oracle Apps Management Console, both the Patch Cycle button and the Schedule button open the Schedule Request window. The Patch Cycle button is only displayed if there is at least one active R12.2 or higher environment.
In the Schedule Request window, the Environment field lists all active environments. If you select a R12.2 environment, the Process Type field includes the patch cycle options prepare, finalize, cutover, cleanup, and status. Depending on whether the window was opened from the Patch Cycle button or the Schedule button, The Process Type field displays additional options:
• |
If opened from the Patch Cycle button, the Process Type field displays additional phases including Abort, fs_clone, and actualize_all. |
• |
If opened from the Schedule button, the Process Type field displays the Apply patch and Impact Patch options, as well as the patch cycle options prepare, finalize, cutover, cleanup, and status. |
The window displays different input fields based on the option selected in the Process Type field. The Dependent Event fields allows scheduling the patch cycle request as a dependent event. In the adop options field, you can overwrite any adop parameters specified in the New Patch window.
NOTE: The Maintenance Mode option is not supported for R12.2 and higher and is not displayed if the environment is R12.2 or higher. |
For a multi-node instance, there are 2 ways to apply the patch to all nodes.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center