Chat now with support
Chat with Support

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

The Oracle Apps Management Console

Quest® Stat® provides comprehensive patch support for Oracle® Applications. After downloading the patches you need from Metalink, the Oracle web support service, you can use the Stat Oracle Applications Management Console to manage and keep record of these patches, associate them with a CSR, and apply them to your Oracle Applications environments.

The Oracle Applications Management Console displays a record of each patch that has been uploaded into the Stat Repository. From here you can upload new patches, edit the Stat attributes associated with the patches, merge two or more patches into a single patch, and schedule the execution of particular maintenance steps before or after a patch is applied to an environment. To open the Oracle Applications Management Console, select Consoles | OraApps Patch Console.

The Patch Inventory tab displays information in a read-only format. To edit a patch, select it and click Edit. This opens the Edit Oracle App Patch window where you can deactivate the selected patch or modify its definition.

Active

Indicates if the patch is active in the Stat Repository. Only active patches can be associated with a CSR and applied to an environment or merged.

Patch Type

The type of patch.

Patch Name

The ID number that Oracle Support assigns the patch for tracking purposes.

Description

A user-defined description of the patch.

Tar/SR

The Internet service or technical assistance request number that Oracle Support assigns the issue.

In CSR

Indicates if the patch is associated with a CSR.

Merged

Indicates if the patch is a merged patch.

Merged Member

Indicates if the patch has been used to create a merged patch.

Product Family

The Oracle Applications application family targeted by the patch.

Product

The specific Oracle Applications application targeted by the patch.

Version

The Oracle Applications version number for the patch (11i is currently the only option).

Last Update

The date and time the patch record was updated in Stat

Update Userid

The ID of the user who last modified the patch record in Stat.

Member Patches

If the selected patch is a merged patch, this field displays the ID numbers of the merged member patches.

Associated CSRs

Displays the CSR numbers of the CSRs the patch is associated with, if any.

Uploading Patches

Stat's patch import utility enables you to upload Oracle® Applications patches to the Quest® Stat® Repository. When you upload a patch, Stat automatically unzips the zip file downloaded from Metalink and reads the contents of the Readme file. From this point forward, the zip file is managed within Stat. The Readme file and other information within the zip file is used by Stat to populate several fields in the Patch Inventory tab with default values. You can complete the definition of the patch by specifying additional patch values as needed.

1
Click New.
5
(Optional) Click View in the Readme column.
6
Click OK or Apply.
7
(Optional) Click Delete Content if for whatever reason you want to remove the patch file from the Stat Repository.
You may want to delete a patch file if, for example, you have already applied it to an environment and want to free up space in the Stat Repository, or you have uploaded it in error. Clicking Delete Content only removes the patch zip file from the Stat Repository. The record of it being uploaded or applied to an environment remains in the Stat patch history.
8
To add another patch zip file for this patch, click Upload and repeat the upload process.

Downloading Patches

You can download any Oracle Applications patch that has been uploaded to the Stat Repository. By downloading patches from the Stat Repository instead of Metalink, you can save network bandwidth and also avoid problems where the password to download a patch from Metalink is set to expire soon.

1
Click Edit.

Defining Patches

After you upload a patch and save it to the Stat Repository, Stat populates the New Oracle App Patch window with the values it has read in the patch zip file, including prerequisites and drivers. However, you can specify additional information as needed. This is done on the General tab.

The General tab allows you to edit many of the same values you can view from the Patch Inventory tab on the Oracle Management Console. On the General tab you can also specify AutoPatch options which are additional default parameters passed to the AutoPatch command line during the patch apply process (users can override these parameters at runtime). The syntax for Autopatch options is name=value pairs separated by spaces. Also, an adop Options field is displayed for R12.2 patches. Here you can specify adop options which are additional default parameters passed to the adop utility during the Patch Apply process (users can override these parameters at runtime). The syntax for adop options is name=value pairs separated by spaces.Refer to your Oracle documentation for a list of valid AutoPatch command line options and valid adop parameters.

If system administrators have designated an Oracle Applications environment as the default environment, whenever you upload and save a patch file, a process request is automatically sent out to determine if any other patches should be applied before you apply the patch that was just uploaded. The results are displayed in the Prerequisites tab.

The Oracle version the default environment is running on determines the number of tab-pages displayed for patch prerequisites. If the default environment is an 11i instance, only the Prerequisites (UMS) tab is displayed. If the default environment is a 12R instance, a second tab is displayed, Prerequisites. The Prerequisites (UMS) is for backward compatibility only and will be removed in a future release.

If a default environment has not been designated, or if you want to run the request for an environment other than the default, select it in the list of active Oracle Apps environments and click Get Prerequisite. The request is sent to the Stat Oracle Agent. After the request has been processed, you can view the results by clicking Refresh. Any prerequisites found by the agent are appended to the list.

You can also manually add and delete patch records from the prerequisites list. To add a prerequisite patch, click New. Then in the Dependent Patch field, enter the ID of the Prerequisite patch. Optionally, specify additional information such as Platform and Language. To delete a patch prerequisite record, select it and click Delete.

If you try to apply a patch to an environment before any patches listed in the Prerequisites tab have been applied, you will receive a warning message. Autopatch may fail the patch application process if you continue with the request.

When you upload a patch, Stat reads the contents of the patch zip file and determines what driver files it must process and in what order. In the Drivers tab you can override the default processing order of driver files. This includes configuring Stat to skip a specified driver file.

The Drivers tab displays driver files for each platform and language targeted by the patch, which is determined by the patch zip files you have uploaded for this patch. The Order column displays the position of the file in the processing order. To change the processing order of a driver file, enter a different number in Order column for that file. To skip a driver file, enter “-1” in the Order column. When finished, click OK or Apply.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating