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

Merging Patches

Stat’s patch merging feature serves as an interface with Oracle’s Merge Patch utility, which lets you to merge several Oracle Applications patches into a single patch. After creating a merged patch, you can then perform an impact analysis against it or apply it to an environment. This saves you time especially when upgrading an environment to a certain patch level, for example, when the Test environment has been certified for several patches and the Production environment needs be upgraded with all of those patches at the same time.

Stat reporting also properly reports patch history for merged patches. When applying a merged patch, Stat recognizes each of the member patches as being applied. This information is then added to Oracle’s patch history table, which records the Stat name of the merged patch instead of default value, “merged.”

In the Patch Number field, enter an ID number for the merged patch.
(Optional) De-select the Merge non-US drivers in one option if you do not want to merge each non-US language driver into one.
In the Merge Options field, enter any additional options for merging patches.
In the Environment field select the environment where you want the merge to take place.
In the Environment Server field select the server of the environment.
In the Working Directory field, enter the directory where you want the merged files to be copied.
In the Description field enter a description of the merged patch.
Click Send Request.

After the Oracle Agent processes the merge patch request, you can view the log files generated by Oracle’s Merge Patch utility in the Process Request tab.

Comparing Patches

The Environment Patch Level Compare Report generates a state-based report that identifies differences in patch levels across multiple environments. This helps you keep environments in sync and identify why an issue is occurring one environment and not another.

If you want to compare patches from a particular date, select Show patches as of. Then browse for the date you want. Patch activity before the selected date will not be considered in the comparison.
(Optional) select Grid Compare if you want the results of the comparison displayed in a grid format.
Click Next.
The Results window displays the results of the comparison differently depending on whether or not you selected the Grid Compare option. In either case, the Results window is state-based, meaning it includes patches that were applied to environments due to environment refresh events. In addition, any patch applications that were deleted because of refresh events are excluded. For more information on state-based reporting, see Change/Service Requests .
Click Export List... if you want to export the compare results to a file.
Click Back if you want to compare different environments or use different comparison settings.

Setting Up Maintenance Steps

Sometimes the instructions for an Oracle patch require that you perform maintenance steps before or after you apply the patch to an environment. These steps may include running a particular command from the adadmin utility or running a script against the target environment. Stat provides a number of predefined maintenance steps that you can schedule before or after the Oracle Agent processes a patch application request. These predefined steps are displayed in the Maintenance Steps tab.

When scheduling maintenance steps and patch application requests, you can enforce that steps are performed as scheduled by specifying dependent events. A dependent event is an event that has to be completed before the current event is submitted to the Oracle Agent. For example, if a certain maintenance step should be run after a patch has been applied to an environment, you can make that patch application request a dependent event for the maintenance step. This way, the maintenance step cannot be executed until after the Oracle Agent has first processed the patch application request.

Editing Maintenance Steps

You can modify the default parameters of predefined maintenance steps. These include both general adadmin parameters as well as command-specific parameters (if any).

Ignore Restart - Selecting this option configures the Oracle Agent to ignore the restart files if previous adadmin session failed
Batch Size - Default value is set to 1000
Workers - Number of workers used to run an adadmin session. Recommended number is between 4 to 8 workers.
Products - Enter all to run the step for all products, or enter a space separated list of products
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating