立即与支持人员聊天
与支持团队交流

Stat 7.0 - Web User Guide

Stat Web Queries CSRs Workflow Tasks CSR Logs Change Management Object Migration Process Requests CSR History CSR Migration Path Job Monitor Test Connect Reports

Re-archiving Objects

If for some reason the Stat Central Agent is unable to create an archive set without errors, rather than creating a second archive set, you can simply re-archive selected objects in the original archive set. When you re-archive objects, the Stat Central Agent deletes the original archive set and creates a new archive set containing only those objects you selected.

Although you can re-archive objects in any archive set, even those that were created without errors, you should only re-archive objects that were not successfully archived the first time. If you want to re-archive objects in an archive set that was created without errors, you should create an interim archive set.

To re-archive objects, in the Objects tab, select the objects you want to re-archive and click Re-Archive.

 

Object Migration

The previous chapter explained how to archive objects by creating archive sets. This chapter explains how to migrate archive sets between your Oracle Applications environments.

Migrating objects updates your environments with the most recent version of those objects, or, if necessary, lets you roll back your environments to earlier versions.

The Stat Web Client only supports migration of single archive sets.

Topics:

•
Choosing an archive set for migration
•
Running a migration (PeopleSoft)
•
Unsupported step types in Web Client
•
Unsupported step types in Web Client

Choosing an archive set for migration

Choosing an archive set for migration
1
Go to the Archive Sets tab.
2
Click Migrate.
3
In the pop-up shown, select the archive set and the target environment, and click Migrate.
4
You will be redirected to the migration window where you can configure all the necessary inputs needed for the actual migration.

Running a migration (EBS)

To run a migration:
1
Open the CSR window and do one of the following:
•
In the Migration Path tab, click and hold your cursor over the source environment for the archive set and drag and drop it in the target environment.
•
In the Archive Sets tab, click Archive Sets to display the Archive Sets table. Then drag and drop the archive set you want from the table to the target environment's tree node.
* 
IMPORTANT: Before you can migrate an archive set into an environment that requires migration approval, one or more authorized users must approve the migration.
2
Stat opens the Migration window.(Optional) If you want the Stat Central Agent to process the migration job at some later time, enter the date and time in the Migration Date field.
The field defaults to the current date and time. You can schedule the migration up to 90 days in the future.
3
(Optional) In the Description field, enter a unique description of the migration.
The field defaults to CSR ID+Archive ID.
4
(Optional) Select the Stop on Error option if you want the Stat Central Agent to terminate the migration at the first error it encounters.
System administrators may set this option to be selected or de-selected by default.
5
(Optional) De-select the E-mail Notification option if a business rule or personal rule triggered by a migration event has been defined for the service domain and you do not want Stat to send email notifications that may be triggered by the migration.
This option is selected by default and is displayed only if one or more Migration Notification business or personal rules have been defined for the service domain. Fore more information, see Defining Personal Rules .
6
(Optional) Select the Maintenance Mode option if you are on Oracle Applications version AD.I and want Stat to put the environment in Maintenance Mode when migrating objects.
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.(This option does not apply to R12.2 environments.)
7
Select the archive set you want to migrate.
The window displays a list of archive sets that you can migrate from the selected environment. If you initiated the migration from the Archive Sets tab, the list displays only the archive set that you dragged and dropped onto the target environment.
By default, all the objects in the archive set are selected for the migration. However, with the appropriate security rights, you can exclude either all the file objects or all the database objects from the migration. You can also exclude individual objects.
8
(Optional) De-select the class of objects (file objects, setup, or schema objects) you do not want to migrate.
9
(Optional) In the Migrate column, de-select the individual objects you do not want to migrate.
* 
NOTE: If an Oracle Apps file object type is flagged as a database script, the Stat Oracle Agent executes these objects using sqlplus during a migration. The Oracle agent only looks at the return code from sqlplus to determine if the migration was successful or not. The following statement should be included with all scripts to instruct sqlplus to return a non-zero return code if errors are encountered:
SET VERIFY OFF
WHENEVER SQLERROR EXIT FAILURE ROLLBACK;
WHENEVER OSERROR EXIT FAILURE ROLLBACK;
If you are migrating to a distribution environment, the window displays the list of active target environments. By default, each environment in the distribution list is selected as a target. However, with the appropriate security rights, you can exclude certain environments from the migration.
10
(Optional) If migrating to a distribution environment, de-select any environment in the list of active target environments you want to exclude from the migration.
11
If the archive set contains file objects and the target environment is Development, select one of the following options in the Migrate file to field:
•
Development Env – Select if you want to place the file objects in the source file locations of the Development environment
•
Working – Select if you want to place the file objects in the developers’ working directories. Only the file objects assigned to each developer get copied into their working directories.
•
Dev & Working – Select if you want to place the file objects in both the source file locations and the working directories. If the archive set does not contain any file objects or the target environment is not Development, this option is dithered with a value of “NA.”
12
If the target environment is version R12.2, select the file system to which you want to migrate file objects in the Edition field.
Options include Run, Patch, or Both.
* 
NOTE: R12.2 application tier file system has 2 copies of all files. A “Run File System” where all the services are currently running from, and a “Patch File System” where all patches are applied in a patch cycle. A patch cycle starts when the prepare phase of adop is run and the “Run File System” is copied to the “Patch File System.”

Stat archives file objects from the current Run Edition.The Edition field is only displayed if the target environment is R12.2 or higher.

13
Click Migrate.
At this point, Stat may prompt you to select and order the pre and post migration steps (if any) that have been defined for the target environment or for the objects or object types in the archive set.
14
Select pre and post migration steps, as necessary.
For more information, see Validation in PeopleSoft migrations .
15
After selecting the pre-migration steps, click the Migrate button.
Stat opens the CSR Migrations Console, which shows that the migration job has been submitted to the Stat Central Agent. The Agent either begins processing the migration immediately, or if you scheduled the migration, at the date and time you specified. For more information, see Migration Console .
16
If you are only migrating file objects, Stat copies the file objects into the target environment.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级