Chatta subito con l'assistenza
Chat con il supporto

Stat 6.2 - 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

Patch Impact Analysis Process Requests

Before applying a patch to an environment, you can have the Oracle Agent perform an impact analysis to determine which objects in the target environment will be affected. After the Agent has processed your request, you can view the list of impacted objects in the Environment History tab as well as the Process Request tab of the CSR window.

If you want to view the AutoPatch log files and any error or warning messages generated by the Agent during processing, you can do so in the Process Request tab of the Oracle Applications Management Console or the CSR window.

If some reason the Agent fails to process your impact analysis request (as indicated on the Process Request tab), you can reschedule your request and try performing an impact analysis a second time. However, it is important to remember that Stat interacts with Oracle tools and these tools may fail for various reasons unrelated to Stat. Stat will report the failure, but you will need to refer to Oracle Support or Metalink to resolve the errors.

1
In the Process Type field select Patch Impact.
2
In the Environment field select the target environment of the patch.
3
In the Run Time field select either Immediate if you want the Agent to process the request right away or select Select Datetime if you want to schedule the request at some future date.
4
If you selected Select Datetime, browse for the date you want. You can also specify the time you want the request processed in terms of hour and minute.
5
(Optional) Deselect Ignore Restart File.
6
Click Save.

Patch Application Process Requests

To submit a patch application request, you must specify:

After the Agent has processed your request, you can view the list of objects affected by the patch in the Environment History tab as well as the Process Request tab of the CSR window.

If you want to view the AutoPatch log files and any error or warning messages generated by the Agent during processing, you can do so in the CSR Process Request tab in the Oracle Applications Management Console.

You can re-apply a patch to an Oracle Applications environment regardless if that patch was successfully applied the first time or not (as indicated on the Process Request tab). If unsuccessful, you can reschedule your request and try applying it a second time. If successful, Oracle's AutoPatch utility identifies the patch as having already been applied and asks Stat if it should continue processing. Stat always responds “Yes” to this prompt to allow the patch to be re-applied.

1
In the Environment field select the target environment of the patch.
2
In the Process Type field and select Apply Patch.
3
(Optional) If you are on Oracle Applications version AD.I, click in the Maintenance Mode field and select Normal. (This option does not apply to R12.2 environments.)
Starting with version AD.I, Oracle requires that environments be put into Maintenance Mode before changes (e.g., AutoPatch) can be performed. The Maintenance Mode dropdown list is enabled if your target environment is release AD.I or later. For most cases, the default value Maint should be used, in which case Stat automatically puts the environment in maintenance mode when applying the patch. If you select Normal for hot patches, the Patch Options column must include “options=hotpatch”. Otherwise, AutoPatch will fail since Stat does not put the environment in maintenance mode. For more information on Maintenance Mode, see your Oracle Applications documentation.
4
In the Run Time field select either Immediate if you want the Agent to process the request right away or select Select Datetime if you want to the request to be processed at some future date.
5
If you selected Select Datetime, browse for the date you want. You can also specify the time you want the request processed in terms of hour and minute.
6
(Optional) Deselect Ignore Restart File.
7
(Optional) Select Disable Patch Backout.
8
If patch application approvals are required for the target environment, in the Approval Option field select the action you want the Agent to take regarding these approval requirements.
Cancel if approvals are not met - The Agent cancels the patch application if it does not receive all the required approvals
Apply once approvals are met - The Agent applies the patch once all the required approvals are received
Apply regardless of approval status - The Agent applies the patch regardless of approval. This option is enabled only if you have the security rights to override patch approval requirements.
NOTE: The Approval Option field is disabled if you selected Immediate in the Run Time field.
The Patch Options and adop Options columns displays any AutoPatch or adop options that have been defined on the General tab of the New Oracle App Patch window. You can modify the default parameters before applying the patch or you can specify new ones. The syntax for the Autopatch and adop options are name=value pairs separated by spaces. Refer to your Oracle documentation for a list of valid AutoPatch and adop command line options.
If you want the Agent to apply the patch only if the preceding patch was applied successfully, select Prior patch completes successfully. If you want the Agent to apply the patch even if the preceding patch failed, select Regardless of prior patches status. This option does not apply to the first patch in the processing order.
14
Click Save.

Viewing Process Request Results

You can view the results of a process request in one of two ways:

Process Request Tab

The Process Request tab displays information regarding all the object management requests submitted to the Oracle Agent, including:

The Process Request tab in the CSR window displays the same information as the Process Request tab in the Management Console except for the following differences:

The Process Request tab in the CSR window is CSR-specific, meaning that it only displays information concerning process requests for patches and objects associated with the current CSR
The Process Request tab in the CSR window features an Impact Obj. button that lets you view the list of objects returned by an impact analysis or patch apply process request.
2
Click Impact Obj.

The Impacted Objects window lists all the objects that were either returned during an impact analysis request or were modified by a patch application request. The information includes the class, type, name, product and language of each object, its pre- and post-patch version number, application name, modification date for the record, and the name of the requestor. The Custom Object column indicates if the object has been customized, and the Indirect Impact column indicates if the object was used as the source of a new object.

If applicable, you can view the navigation paths that access an object (for example, the responsibilities and menus that access a form) by selecting the object and clicking Nav Path. Stat displays the navigation paths in the View Navigation Path window. Only active navigation paths associated with one or more active users are included.

In the Process Request tab, you can view the log files and messages generated by the Stat Oracle Agent while processing object management requests (including patch applications, backouts, and impact analysis as well as archiving and migrating objects). These log files include detailed information that pinpoint the source of warnings and errors generated during processing. For more information, see Viewing Log Files and Agent Messages .

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione