Chat now with support
Chat with Support

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

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.

To run the archive Set Synchronization Wizard:
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.
3
In the left side of the window, select the environments you want to run the wizard against. Hold down the <Shift> or <Ctrl> key to make multiple selections.
* 
NOTE: You cannot run the Archive Set Synchronization Wizard for a distributed environment. Archive sets contained in a distributed environment are not identified by the wizard. Also, the wizard does not display archive sets located in your working directory.
4
In the right side of the window, select the object type(s) whose archive set IDs you want the wizard to compare. Hold down the <Shift> or <Ctrl> key to make multiple selections.
5
Click Next>.
The wizard searches the environments for archive sets containing the selected objects. In the next window, the wizard displays a list of objects with differing archive set IDs.
6
To print or export this list click the appropriate button
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.
In the next window, you select certain migration parameters, including the source and target environment and the objects you want to migrate.
8
In the Source of Synchronization field, select the environment that contains the object versions you want to migrate.
The wizard displays a list of the out of sync objects contained in the selected environment.
9
Select the objects you want to migrate. Hold down the <Shift> or <Ctrl> key to make multiple selections.
10
In the Target of Synchronization field, select the environment to which you want to migrate the selected objects.
11
Click Migrate.
The wizard opens a migration window that closely resembles the Mass Migration window. From here you can synchronize your environments by migrating the selected objects into the target environment. For detailed instructions on performing a mass migration, see the “Object Migrations” section in the appropriate change management chapter.

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.

To run the Archive Set Purge Wizard:
1
Select Object Management | Archive Purge Wizard.
The wizard prompts you to specify the module, service domain, and additional CSR information about the archive set you want to purge.
2
In the Module field, select PeopleSoft, Oracle Applications, or  Generic Applications, depending on the change management module you are using.
* 
NOTE: You can set a default value to be displayed in the Module field. To do this, select User Options | Stat Options. Then in the Stat User Options window, select the value you want in the Default Module field.
3
In the Service Domain field, select the service domain from which you want to purge the archive set.
4
(Optional), Specify additional search criteria:
•
Enter the date that the archive set was created on or before. You can manually enter the date or click the Browse button (...) to access a calendar.
•
Select the environment from which the archive set was migrated. To disregard the source environment, select Any.
•
Select the CSR type of the archive set. To disregard the type, select Any.
•
Select the current status of the associated CSR. To disregard the status, select Any.
•
Select the current status of the archive set. To disregard the archive set status, select Any.
5
Select each archive set type you want to purge. Options include Base, Interim, and Final.
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>.
In the next window, the wizard displays a list of archive sets that match your search criteria.
7
Select the archive sets you want to purge. To select all the archive sets in the list, click Select All.
* 
NOTE: To open the CSR to which an archive set is associated, double-click on it. To print or export this list, click the appropriate button.
8
Click Next>.
In the next window, the wizard tells you that it has flagged the selected archive sets for purging, which is performed by the Stat Central Agent.
9
Click Process Purge.
The wizard processes the purge and reports its progress in a meter bar.
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.

To run the Undocumented Patch Tool:
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.
Stat queries the selected environment and returns any undocumented patches it finds:
•
For PeopleSoft environments, the tool identifies undocumented patches as well as undocumented incidents. An undocumented incident may indicate that a patch has been applied to a PeopleSoft environment but its project definition has since been removed, in which case Stat cannot identify the patch directly by its project name. You can document a patch identified by an incident ID by adding the incident to a CSR, but you must first specify the project name of the patch that you want to associate the incident with.
•
For Oracle Applications, it displays the Patch Type and Patch Name and also indicates whether the patch is currently uploaded to the Stat Repository.
* 
NOTE: For Oracle Applications, a patch is considered undocumented for a particular environment if there is no history of that patch being applied to the selected environment in Stat. When you apply a patch associated with a CSR to an environment, Stat records the history and documents the patch. However, if the patch has been applied to an environment before it was uploaded into Stat and associated with a CSR, it is still considered undocumented. To have such a patch documented in Stat, the patch must be added to a CSR with the Undocumented Patch Tool, not through the Objects tab of a CSR.
4
Do one of the following:
•
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.
* 
NOTE: Before adding the patch definition to a CSR, be aware of the following:

Workflows can contain status rules that do not allow users to add or lock objects while the CSR is in a certain status. When this is the case, you will be unable to add the patch definition until the CSR status changes to one that allows objects to be added and locked.

For PeopleSoft, you can use the Undocumented Patch Tool to add patch definitions to a CSR, but you cannot use the tool to add the objects contained in a patch to a CSR and then apply that patch to an environment. To do this, you must add the objects contained in a patch manually or with the Project Read Wizard. For more information, see Object Management (PeopleSoft) .

For Oracle Applications, you can use the Undocumented Patch Tool to add patch definitions to a CSR, but you cannot use the tool to upload patch zip files to the Stat Repository. For this reason, you cannot schedule a patch application or impact analysis request for a patch that has been associated to a CSR via the Undocumented Patch Tool unless its corresponding patch zip file has been uploaded to the Stat Repository. For more information, see Patch Management .
5
(Optional) Repeat step 4 to add more CSRs.
Do this if the wizard identified more than one undocumented patch and you want to add the patches to different CSRs.
6
In the Undocumented Patches section, select the patches you want to add to a CSR. Then in the Change/Service Requests section, select the CSR you want to add the patches to.
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.
9
When finished, click Close.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating