Chat now with support
Chat with Support

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

Release Recovery Window

Like the Mass Migration window, the Release Recovery window allows you to mass migrate archive sets based on application release labels. Unlike the Mass Migration window, however, mass migrations conducted in the Release Recovery window override workflow rules, approval requirements, and object locks. This can be an effective way of preserving crucial object definitions during an emergency when time is a factor. Due to its ability to circumvent security measures, access to the Release Recovery window is controlled by specific user class rights and should be restricted to development managers.

To open the Release Recovery window, select Migration Management | Release Recovery. The procedure for mass migrating archive sets based on application release labels in the Release Recovery window is exactly the same as it is in the Mass Migration window, except in the Release Recovery window you can mass migrate any eligible archive set to any environment you want, regardless of workflow rules, pending approvals, or object locks that may exist in other environments (but not, however, regardless of your environment access permissions, as specified for your user account in the User Maintenance window). For more information on mass migrating archive sets, see the “Object Migrations” section in the appropriate change management chapter.

Archive Set Synchronization Wizard

The Archive Set Synchronization Wizard helps you ensure that your environments contain the same versions of objects. After searching selected environments and identifying objects with differing archive set IDs, the wizard gives you the option of migrating the object versions you want from the source environment to a target environment that you select. This way, you can update your environments with the most recent version of objects, or, if necessary, you can use the wizard to roll back your environments to earlier versions.

1
Select Object Management | Archive Set Sync Wizard.
2
In the Select Module field, select your change management module.
If you select PeopleSoft, in the PS Version field, select the version number of your PeopleSoft environments.
NOTE: You can set default values to be displayed in the Module and PS Versions fields. To do this, select User Options | Stat Options. Then in the Stat User Options window, select the values you want in the Default Module and Default PS Version fields.
5
Click Next>.
7
Click Finish if you want to exit the wizard, or click Next> if you want to synchronize your environments by migrating selected versions of objects from one environment to another.
8
In the Source of Synchronization field, select the environment that contains the object versions you want to migrate.
10
In the Target of Synchronization field, select the environment to which you want to migrate the selected objects.
11
Click Migrate.

Archive Set Purge Wizard

The Archive Set Purge Wizard allows you to free up space in your Stat Repository by permanently purging it of unnecessary archive sets. Be careful when using this wizard, since you cannot recover purged archive sets. Access to this wizard is controlled by your user class rights.

1
Select Object Management | Archive Purge Wizard.
2
In the Module field, select PeopleSoft, Oracle Applications, or  Generic Applications, depending on the change management module you are using.
3
In the Service Domain field, select the service domain from which you want to purge the archive set.
For Oracle Applications, you can also select a fourth type, Patch. A patch archive is automatically created by Stat whenever a patch is applied to an environment. This archive contains all the objects impacted by the patch in the target environment and is used for patch backout purposes. You can use the Archive Purge Wizard to remove these archives from the Stat Repository.
6
Click Next>.
8
Click Next>.
9
Click Process Purge.
10
Click Finish.

The archive is purged the next time it is processed by the Stat Central Agent. Remember that a purged archive cannot be recovered.

Undocumented Patch Tool

The Undocumented Patch Tool searches selected PeopleSoft or Oracle Applications environments and identifies any patches that are not documented in the Stat Repository (meaning not associated with a CSR). If it finds any undocumented patches, you can add this information to either a new or an existing CSR.

1
Select Object Management | Undocumented Patches.
2
In the Module field, select the change management module you are using.
Options include PeopleSoft and Oracle Applications.
3
In the Environment field and from the list of active environments select the one in which you want to search for undocumented patches.
If you want to add a patch to an existing CSR, click Lookup CSRs. This opens the Search CSR Engine. Use the Search CSR Engine to locate the CSR(s) that you want to add the undocumented patch to. You can select multiple CSRs if the wizard returns multiple undocumented patches and you want to add different patches to different CSRs. Stat displays an error message if you select a CSR that does not support patches. After selecting the CSR(s) you want, close the Search Engine. For more information, see The Search CSR Engine .
If you want to add a patch to a new CSR, click New CSR.... Then follow the instructions for creating a new CSR described in Chapter 3, “Change/Service Requests.” Make sure to create a CSR that supports patches. After creating the CSR, close the CSR window.
7
(Optional) For PeopleSoft, if you want to document a patch by adding an undocumented incident to a CSR, select the incident and click Add>>. Then specify the project name of the patch that you want to associate with the incident.
8
Click Add>>. Stat adds the patches to the selected CSR.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating