サポートと今すぐチャット
サポートとのチャット

Stat 6.3 - User Guide

Introduction to Stat Connecting to Stat Change/Service Requests Stat Consoles Tasks and Time Entries Stat Projects Search Engines Reports and Graphs Personal Rules Object Tools and Wizards Change Management for PeopleSoft
Object Management (PeopleSoft) Object Archives (PeopleSoft) Object Migrations (PeopleSoft)
Change Management for Oracle Applications
Object Management (Oracle Applications) Patch Management Object Archives (Oracle Applications) Object Migrations (Oracle Applications)
Change Management for Generic Applications
Object Management (Generic Applications) Object Archives (Generic Applications) Object Migrations (Generic Applications)
Appendix: Troubleshooting Chart Appendix: Migration Options Appendix: User-Specific Parameters Appendix: Supported PeopleSoft Proprietary Objects Appendix: Stat Reports

Environment History Tab

The Environment History tab displays a record of all the patch application, patch backout, and impact analysis requests that are either pending or have been completed in each active environment.

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 .

Available options include Completed, Completed with Warnings, and Completed with Errors.
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).

There are many reasons why AutoPatch may fail to process a driver file, some of which are trivial and can be disregarded. However, because patches with driver files that failed to process may be treated differently by other functions within Stat (such as environment compare), you can manually change the status of a driver file if the reasons it failed to process (as indicated in the AutoPatch log file) are insignificant.

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 .

Available options include Completed, Completed with Warnings, and Completed with Errors.
3
In the Required Explanation field, describe the reason why you are changing the status in sufficient detail. Then click Save.

Rescheduling Requests

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.
Stat opens the Schedule Request window. The Process Type and Environment fields display in read-only format the same values as the original request.

Changing Process Event Statuses

A process request may fail for several reasons, some minor and others critical. Stat does not distinguish between minor and critical process event errors. In either case, the event receives a Complete with Errors process status. However, because certain functions within Stat (such as environment compare) treat failed process requests differently than requests that were processed successfully or with warnings, you can manually change the status of a process request event that failed for minor or insignificant errors so that it will be treated as having been processed successfully. After changing a status, you must explain the reason why you making the change. This explanation is then written to the Agent log file for auditing purposes.

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 .
Available options include Completed, Completed with Warnings, and Completed with Errors.
3
In the Required Explanation field, describe the reason why you are changing the status in sufficient detail. Then click Save.

Backing Out Patches

When a patch is applied to an environment, an archive of all impacted objects is automatically taken from the target environment. If after applying a patch to an environment you decide that you want to return the impacted file objects and schema objects to their original, ‘pre-patch’ state, you can use Stat’s Patch Backout feature.

With Patch Backout, you can restore file objects and the following schema object types: tables, views, indexes, packages, and sequences. However, some changes may not be recovered, while others may be impossible to recover due to transactional activity during or after the patch was applied. Also, new schema objects inserted into an environment by way of a patch may not be deleted.

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.
The Maintenance Mode field is disabled if you are on an earlier version than AD.I. For more information on Maintenance Mode, see your Oracle Applications documentation.
4
Click Save.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択