Stat 6.1 - User Guide

Migration History Window

The Migration History window shows additional information about a migration, including the migration status of the individual objects, approval statuses, and log reports. To open the Migration History window, do one of the following:

•

In the Migration Console, double-click a migration.

•

In the Migration History Wizard, select a migration and click Details.

•

Double-click an environment, either in the Migration Path tab or Object Management tab of the Change Management/ Version Control window.


	NOTE: When you open the Migration History window by double-clicking an environment, the window shows information regarding all the migrations that have targeted that environment.

The top portion of the Migration History window displays much of the same general information as the main console window, but with additional information, such as:

•

Submit Date— The date and time the user ran the migration

•

Schedule Date — In the case of scheduled migrations, the date and time the migration was scheduled

•

Maintenance — For migrations to Oracle Apps environments, indicates whether Maintenance Mode was enabled or not.

•

Migration Exit Option — Indicates whether Stat is configured to stop the migration if any errors are encountered

•

Edition — For migrations to Oracle Apps R12.2 environments or higher, indicates the file system to which file objects were migrated. Options include Run, Patch, or Both.

The bottom portion of the Migration History window displays the migration status of each object contained in the archive set, migration approval statuses, as well as the log files.


	NOTE: In the case of migrations to distributed environments, the Objects tab displays the migration status of each object to each environment.

In the Migration History window:

•

If you are the user who ran the migration, or a user with appropriate user rights, you can change the status of a migration that has not yet been processed from Submitted to Completed or Canceled. If you change the status to Completed, however, the migration is assigned the status Completed with Errors since the Stat Central Agent had not yet migrated all the objects.

•

To view the status of any pre or post migration steps that were triggered by the migration, click Pre Migr Steps or Post Migr Steps. This opens the respective Migration Steps window. From here you can run steps and mark them as complete if they haven’t been already.

•

To view migration approval statuses, select the Approvals tab, which shows who approved the migration and when.

•

(PeopleSoft) To view the audit flags and other PeopleSoft project settings, click the Audit Flags button. This opens the Upgrade Options window in read-only format which shows whether these properties were set to be copied into the target environment during the migration or whether the settings as defined in the target environment were retained.

•

Use the refresh button to update the status of migrations. Use the PreMigr Steps or the PostMigr Steps button to run any Pre/Post Migration Steps.

•

The Log tab displays a list all the Stat-generated migration logs, including (for PeopleSoft) the PeopleSoft project copy log. Double-click a log to open it.

Patch Application History

(Oracle Applications only) If patches have been applied to the selected environment, the Migration History window features an additional Patch Application History tab, which is divided into two sections. The top section displays information concerning each patch that has been applied to the selected environment. When you select a patch, the bottom section of the window shows information about each object included in the patch file. From here you can also access information about patch application approvals and the driver files contained in the patch.

In the Patch Application History tab, all the patches applied to the selected environment appear in descending order with the most recently applied patch set appearing first.

The Patch Application History tab displays the following information:


Column	Description
Patch Name	The ID number that Oracle Support assigns the patch for tracking purposes.
Apply ID	A unique ID number assigned to each patch application request.
Process Order	If the patch was included in a multiple patch application request, the order in which it was scheduled to be applied. The default order number is 1.
Process Status	Shows if AutoPatch encountered an error when processing a patch. Possible statuses include Completed, Completed with Warnings, and Completed with Errors (Pending requests have a status of Pending/New, Sent to Agent, Received by Agent, or In Process. The status Not Processed means AutoPatch failed the process event before processing the driver).
Date Applied	The time and date the patch was applied to the selected environment.
Applied By	The user who applied the patch.
Process Type	The type of patch application request. options include Apply Patch, Roll Back, and Patch Impact.

Impacted Objects Tab

When you select a patch application in the top portion of the Patch Application History tab, the Impacted Objects tab lists all the objects (if any) that were modified during a patch application request. The information includes the class, type, name, navigation path, its pre- and post-patch version number, and application name.

If applicable, you can view the navigation paths that access an object (for example, the responsibilities and menus that access a form) by selecting the object and clicking Navigational Path. Stat displays the navigation paths in the View Navigation Path window. Only active navigation paths associated with one or more active users are included.

Drivers Tab

The Drivers tab displays the driver files for each platform and language targeted by the patch. The Process Order column displays the position of the file in the processing order. The Process Status column shows if AutoPatch encountered an error when processing a driver file. Possible statuses include Completed, Completed with Warnings, and Completed with Errors (Pending requests have a status of Pending/New, Sent to Agent, Received by Agent, or In Process. The status Not Processed means AutoPatch failed the process event before processing the driver).

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

Stat 6.1 - User Guide

Migration History Window

Patch Application History

Impacted Objects Tab

Drivers Tab