Chat now with support
Chat with Support

Stat 6.1 - 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

Documenting Environment Refresh Events

Documenting an environment refresh in Stat entails specifying the source and target environments and the time frame in which the refresh occurred or is scheduled to occur. Specifying a time frame is done in terms of start and completion dates. If you are using a backup of an environment as the source of the refresh, you must also specify the date that the backup of the source environment was taken.

1
Click New in the Environment Refresh tab, or in the case of an existing refresh event record, select the record and click Edit.
3
In the Source Database field, select the environment that is the source for the refresh.
The source environment must be the same application version as the target environment. Also, if you select the same environment as the target environment, you must also select the Refresh From Backup check box, meaning that the source of the refresh is a backed up version of the target environment.
4
(Optional) Select Refresh From Backup if you are using a backed up version of an environment as the source for the refresh.
In the Actual Start Date field, specify the date and time the environment refresh began or is scheduled to begin. Then in Actual Date Completed field, specify the date and time the environment refresh was completed or is scheduled to be complete. You can enter the date, hour, and minute manually or you can click the Browse button in either field and use the Calendar tool. Remember that you can specify an actual start date without specifying an actual complete date, but you cannot specify an actual complete date without first specifying an actual start date. Also, the actual complete date must be later than the time specified in the Actual Start Date field.
In the Scheduled Start Date field, specify the date and time the environment refresh is scheduled to begin. Then in Scheduled End Date field, specify the date and time the environment refresh is estimated to be complete. You can enter the date, hour, and minute manually or you can click the Browse button in either field and use the Calendar tool. Remember that you cannot specify a scheduled start date without also specifying a scheduled end date, and that the scheduled end date must be later than the scheduled start date.
6
In the Description field, briefly describe the refresh event.
The status of the event changes to In Process. After about a minute, the status changes to Agent in Process. The Cancel button on the edit screen is enabled once the status is either Agent in Process or Waiting for Agent.

Actual Dates, Scheduled Dates, and Backup Dates

When you document an environment refresh event in Stat, you have the option of specifying the date, hour, and minute the refresh event started or is scheduled to start, as well as the date, hour, and minute the refresh event completed or is schedule to complete. You can specify this time frame in terms of either actual dates or scheduled dates. In addition if you are using a backup of an environment as the source for the refresh, you must also specify the date, hour, and minute that the backup of the source environment was taken.

You specify the time frame using actual dates if the environment has already been refreshed and you want to document the refresh event after the fact, or if you know that the environment will be refreshed at some specific time in the future. When you specify a future actual start date, Stat locks the target environment and prevents users from working within that environment beginning at the time specified in the Actual Start Date field. At this point, users will receive an error message if they attempt any activity within the target environment. The target environment remains locked until the time specified in the Actual Complete Date field, if any, has elapsed. When you first document a refresh event, you can specify an actual start date without specifying an actual complete date. Once the refresh has been completed, you can then edit the refresh record and specify an actual complete date, which removes the lock on the target environment. The actual complete date must be later than the time specified in the Actual Start Date field. Also, you cannot specify an actual complete date without first specifying an actual start date.

The Stat Central Agent does not process a refresh event until the time specified in the Actual Complete Date field has elapsed. If you are documenting an environment refresh event that has already occurred and specified the actual completion date, the Stat Central Agent processes the request immediately after you save.

You specify the time frame using scheduled dates when there are tentative plans to refresh the environment at some future time. When you use scheduled dates, users can still work within the target environment during the scheduled refresh event but will receive a warning message stating that the environment may be in the process of being refreshed. At any time before or after the refresh event, you can edit the refresh record and change the scheduled dates to actual dates.

As with actual dates, the scheduled end date must be later than the time specified in the Scheduled Start Date field. Unlike actual dates, however, scheduled dates require that you specify both a start and an end date.

If you are using as the source of the refresh a backup of an environment, you need to specify the date and time when that backup of the environment was taken. This information allows Stat to refresh the target environment with the history of the source environment up to the date and time of the backup.

Canceling Environment Refresh Records

If you have not specified an actual completion date, at any time you can remove a refresh event record by selecting it on the Environment Refresh tab and clicking Delete. If you have specified an actual completion date, or if the completion date has elapsed and you want to undo the update of the Stat Repository, select the record in the Environment Refresh tab and click Edit. Then in the Environment Refresh window, click Cancel Request. When you cancel a request after the completion date has elapsed, the definition of the target environment in the Stat Repository is returned to its original state before the Stat Central Agent processed the refresh request.

State-Based and Activity-Based Reports

Updating the Stat Repository by documenting environment refresh events allows you to run state-based reports. A state-based report takes into account changes made to an environment due to a refresh event. It shows the objects and archive sets that exist in an environment at a particular moment in time. This is in contrast to activity-based reports that show the history of activities that have occurred within an environment, such as migrations and upgrades. Stat supports both types of reports for your environments, even those that have been refreshed. If an environment has been refreshed, however, an activity-based report may not accurately reflect the state of the environment as it exists after being refreshed. State-based reporting of environment refresh events is supported in the Migration History Wizard, the Oracle Apps Patch Level Compare feature, and the Stat Report Library.

To illustrate the differences between state and activity-based reporting, suppose you migrated an archive set into your Test environment and then later refreshed that environment with another environment named Production. A state-based report run after the refresh event would accurately show that the archive set no longer exists in Test, since this data would have been overwritten when Test was refreshed with Production. An activity-based report, however, would show that the archive set had been migrated into Test, which would be accurate in an activity-based sense but would not take into account the fact that after the migration the environment had been refreshed, thereby creating the false impression that the archive set still existed in Test.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating