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

Rapid Recovery Window

In addition to migrating archive sets in a CSR, Stat also assists with object recovery. This is done in the Rapid Recovery window. In this window you can migrate an archive set to any environment, not just those environments on the CSR’s original migration path. You can also recover an archive set from a closed CSR where there are no locks on the objects.

Since you can migrate to environments not on the CSR's migration path, any security right having to do with a migration path does not apply to the Rapid Recovery window, such as the security right that allows a user to migrate to the Base environment.

The Rapid Recovery window should only be used in emergency situations since it overrides several CSR migration rules, including migration approvals, workflow status, and object locks. Because overriding object locks creates the risk of overwriting another user’s work, access to the Rapid Recovery window is controlled by its own security right and should be restricted.

When you use the Rapid Recovery window to migrate an archive set to an environment that is not on the original migration path, the migration is documented in the Migration History window but not the CSR where the archive set originated. On the other hand, if you do recover to an environment on the original migration path, the migration is documented in the CSR as it would be normally.

1
Select Migration Mgmt | Rapid Recovery.
3
(Optional) In the Description field, enter a unique description of the migration.
4
In the Target field, select the migration’s target environment.
5
(Optional) Select the Stop on Error option if you want the Stat Central Agent to terminate the migration at the first error it encounters.
7
The Maintenance Mode field is disabled if you are on an earlier version than AD.I. For more information on Maintenance Mode, see your Oracle Applications documentation.
8
Click the Browse button (...) next to the Select CSR field.
14
Click Migrate>.

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 Mgmt | 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 Mgmt | 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 Mgmt | 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.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating