If any of the environments displayed in the Environment History tab have been refreshed, you can view the information in the tab in either a state-based or activity-based format. A state-based report takes into account changes made to an environment due to a refresh event. It shows the impact analyses and patches that have been applied to an environment at a particular moment in time. This is in contrast to activity-based reports that show all the impact analyses and patches that have been applied to an environment, even those that have been overwritten due to a refresh event. For more information on environment refresh events and state-based and activity-based reporting, see Change/Service Requests .
The Environment History tab also features an Impacted Objs. button, which functions the same way as the Impacted Analysis button described in the section, Process Request Tab .
To switch the view between patch application, backout, or impact analysis requests, click Patch Apply or Impact Analysis. Patch backout requests are displayed with patch application requests. To switch between state-based and activity-based reporting, select the corresponding check box.
In the Environment History tab, the Process Status column shows if AutoPatch encountered an error when processing a patch. Possible statuses include Completed, Completed with Warnings, and Completed with Errors (Pending requests have a status of Pending/New, Sent to Agent, Received by Agent, or In Process. The status Not Processed means AutoPatch failed the process event before processing the driver). There are many reasons why AutoPatch may fail to process a patch, some of which are trivial and can be disregarded. However, because failed patches are treated differently by other functions within Stat (such as environment compare), you can manually change the status of a patch if you determine the reasons it failed are insignificant (as indicated in the AutoPatch log file). You may also want to assign a patch that completed successfully an error-type status. This feature works in conjunction with manually changing the status of process events and patch driver files. To properly change the status of a patch, users must also change the status of the process event and associated driver files, in addition to the patch itself. For more information, see Changing Process Event Statuses and Viewing Patch Approvals and Patch Drivers .
1 |
3 |
In the Required Explanation field, describe the reason why you are changing the status in sufficient detail. Then click Save. |
You can view driver files or approval information concerning a patch application or backout request by right-clicking it and in the pop-up menu selecting either View Patch Approvals or View Patch Drivers. The Patch Approvals window shows the name of each user that has approved the patch, if any, and the date when the approval was made. The Patch Drivers window shows the driver files that were processed when AutoPatch executed the patch application request.
In the Patch Drivers window, the Process Status column shows if AutoPatch encountered an error when processing a driver file. Possible statuses include Completed, Completed with Warnings, and Completed with Errors (Pending requests have a status of Pending/New, Sent to Agent, Received by Agent, or In Process. The status Not Processed means AutoPatch failed the process event before processing the driver).
You may also want to assign a patch that completed successfully an error-type status. This feature works in conjunction with manually changing the status of process events and patches. To properly change the status of a driver file, users must also change the status of the process event and the patch, in addition to the driver files. For more information, see Changing Patch Process Statuses and Changing Process Event Statuses .
1 |
3 |
In the Required Explanation field, describe the reason why you are changing the status in sufficient detail. Then click Save. |
If the Stat Central Agent is for some reason unable to process your patch application or impact analysis request (for example, because the server that hosts the target environment is down), you can reschedule the request and have the Agent process it a second time. You can initiate a reschedule request from the Process Request tab of either the Oracle Applications Management Console or the CSR window.
2 |
Click Reschedule. |
NOTE: Changing the status of a patch-related event does not change the status of the patch itself or its associated driver files. An Apply Patch or Patch Impact event may include multiple patches, in which case changing the event to Completed does not change the associated patches or drivers to Completed. This is because the event may have failed for a reason other than a patch or driver failing. To properly change the status of a process event, you must also change the status of the patch and its associated driver files, in addition to the event. For more information, see Changing Patch Process Statuses and Viewing Patch Approvals and Patch Drivers . |
1 |
3 |
In the Required Explanation field, describe the reason why you are changing the status in sufficient detail. Then click Save. |
1 |
2 |
In the Environment field select the environment that you want to back the last applied patch out of. |
3 |
(Optional) If you are on Oracle Applications version AD.I and want Stat to put the environment in Maintenance Mode when the backing out the patch, select Maint in the Maintenance Mode field. If you do not want the environment put in maintenance mode, select Normal. |
4 |
Click Save. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center