サポートと今すぐチャット
サポートとのチャット

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

Creating Archive Sets (Oracle Applications)

As you make your changes to objects, you should periodically make interim archive sets. This lets you save your work at that point in time. When all your changes are completed and approved, you should make a final archive set. The procedure for both is the same.

To create an archive set:
1
In the Archive Sets tab of the CSR window, click New.
This opens the Archive Set window.
In the Archive Set window you enter basic information about an archive set. From here you define the archive type and source environment and add a description and comments. This window also provides you with read only information, such as number of objects and the time and date the archive set was created.
* 
TIP: You can re-size this window as needed by clicking and holding an edge of the window and dragging to size you want.
2
In the Type field select the type of archive set you want to create.
Options include Interim and Final. Base sets are automatically created by Stat.
* 
NOTE: You can create unlimited number of interim archive sets, but only one final archive set.
3
In the Environment field select the environment containing the objects you want to include in the archive set.
This environment should be the one in which you made your changes. The default environment for interim archive sets is Development.
* 
NOTE: If the CSR contains a reserved object for the selected environment, you cannot create a final set. If the CSR contains an unlocked object for the selected environment, you can create a final archive set but Stat displays a warning message.
4
In the Description field, enter a short description of the changes you made to the objects.
This entry helps identify the archive set elsewhere in Stat.
5
If you are adding file objects to the archive set, do one of the following in the Files From field:
•
Select Environment if the source environment is Development and you want to take the file archives from the environment’s source file locations
•
Select Working if the source environment is Development and you want to take the file archives from the assigned user’s working directories. Or select No if you want to take the archives from the source file locations of Development.
•
Select VCM if you have associated the CSR with a version control management record and you want to take the file archives from the VCM repository. After selecting this option, a VCM-specific field is displayed (Revision for SVN and P4, Tag/Branch for CVS and Git, Label for PVCS, and Version for TFS). In this field you can specify the particular version of the objects you want to add from the VCM repository. Your system administrator may have configured a default value, but you can override it either by entering the version you want manually or by clicking the control button and selecting the version from the dropdown list. If left blank, Stat adds the most recent version of the objects in the repository.
* 
NOTE: When you save the archive set, Stat retrieves the objects from VCM repository. Your system administrator can configure Stat to archive the objects themselves or pointer to those objects.
6
(Optional) If you want to include the archive set in a mass migration based on application release label, select the release label you want in the Release­­ field.
7
(Optional) Enter comments about the archive set.
Comments can include a longer description of the changes or any other helpful information.
8
Click on the Objects tab and click Add....
Stat opens the Select Objects window, which displays a list of the objects contained in the base archive set.
* 
NOTE: When creating a final archive set, Stat automatically adds all the objects in the base archive set and does not open the Select Objects window.
To sort the rows in the Select Objects window, click a column heading to have the rows sorted based on that column.
9
Select the objects you want to add to the archive set.
An interim archive set can contain one, some, or all the objects in the CSR.
10
If you have performed previous migrations or deleted objects on the CSR, check the existence of each object by selecting it and clicking Check Existence.
Stat goes out to the source environment or file locations and looks for the object. If it finds the object it displays the value Yes in the corresponding Exists field. If the object does not exist, Stat displays the value No. Objects that do not exist in the source environment cannot be included in the archive set.
11
Click OK.
This returns you to the Archive Sets tab in the CSR window, which shows your new archive set at the bottom of the Archive Set table. The Status column will display the value In Process until the Stat Central Agent finishes archiving all the objects.
* 
NOTE: Archiving objects is an optional function of Stat. If your system administrator sets up Stat to create archive sets, object archiving occurs automatically.

Archive Set Object Information

To see the details of your archive set, double-click on it in the Archive Set table. This re-opens the archive set window. The Details tab should look familiar since this is the tab you filled out when you created the archive set. The next tab, Objects, now contains all of the object information for the archive set.

* 
NOTE: After adding objects to an archive set, the Migration Flags tab is added to the Archive Set Window. For more information, see Deleting Objects .

The Objects tab displays the following information:

Migr Order

For schema objects, file objects, and setup objects only, indicates the order in which the object will be migrated relative to the other objects in the archive set. Objects assigned a lower number are migrated before objects assigned higher numbers.

* 
NOTE: The default migration order is based on object type and is defined in the Object Type Maintenance table. You can override the default order by specifying a higher or lower value for one or more objects. You can change the migration order values manually, or you can use the Default Order and Reorder buttons, which are described below.
Class

Indicates the class of object. Object classes include data and file.

Type

The object type.

Object

The object name.

Version

A version number internal to Stat. It indicates the number of times the object has been modified/archived in Stat for a given environment.

Status

Reflects the current status of the object. Possible statuses include:

•
Archived – Indicates Stat finished archiving the object
•
Archive Pending – Indicates Stat is in the process of archiving the object
•
Wait Lock – Indicates Stat is waiting for Stat to issue the objects in this CSR a lock. You can archive only locked objects.
•
Delete Pending – Indicates Stat is in the process of deleting the objects
•
Re-archive Pending – Indicates Stat is in the process of archiving the object again
Errors

Indicates the number of errors found. See the Logs window for further details.

Warning

Indicates the number of warnings found. See Logs window for further details.

Source Information

If the object is a data object, this field shows the number of tables and rows in Stat used to complete the archive. If it is a file object, the field shows the exact file location of the archive source in the archive set.

Object Count

This information is displayed at the bottom of the window. It shows the total number of objects in the archive set and how many of these have been archived.

Generation Schema

For any Oracle Apps file type that has been marked as a database script (including SQL Scripts and SPL/SQL, PKB, and PKH file object types as well as custom object types marked as database scripts), this drop-down list displays the list of products that are present in Stat for the source environment. If a value is selected in this column, the object is generated on the target environment using this schema. If the value is blank, the default APPS schema is used.

Buttons

The Objects tab features the following short cut buttons:

•
Add – Adds selected objects to the archive set. Press this button and Stat displays a list of the objects.
•
Delete – Deletes all of the objects in the selected archive set. You cannot delete objects from a base or final archive set.
•
Re-Archive – Instructs Stat to re-archive the objects
•
Refresh – Refreshes the current display
•
Print – Prints the contents of the window
•
Export – Exports the contents of the window
* 
NOTE: Once an archive set has been migrated, you cannot add or delete objects from it. You should create a new archive set instead.
•
Default Order – For schema objects, file objects, and setup objects only, restores the migration order of selected objects to the default order as defined in the Object Type Maintenance table
•
Reorder – For schema objects, file objects, and setup objects only, changes the migration order of selected objects starting with the numerical value specified in the field positioned above the button and in the order in which they are listed in the Objects tab. This provides a convenient way to change the migration order of multiple objects simultaneously. For example, assuming 5 as the starting value, the first selected object is assigned the value 5, the next selected object is assigned 6, and so on.
•
View – For file, schema, and setup object types only, displays the definition of the selected object in a separate window.
•
Download – Allows users to download the selected file or schema object from archive.

Copying Archive Sets

When you copy an archive set, the copy retains the migration order set on the source archive set.

To copy an archive set:
1
In the Archive Sets table, select the archive set you want to copy and click Copy.
* 
NOTE: Only archive sets with a complete-type status can be copied.
This opens the Archive Set window where you can edit the properties of the copied archive set as needed, including the archive type and source environment.
When copying archive sets, be aware of the following:
•
You can select a different source environment, but if the objects don't exist in the new source, you have to add the missing objects if you want to include them in the copy.
•
When you save a copy as a final archive set, the number of objects in the archive set must equal the number of objects in the base archive set. If not, Stat prompts you to add the objects when you try to save the archive set.
2
Add a description of the archive set, and (optionally) edit the properties of the archive set as needed.
3
Click OK.

Deleting Objects

Stat lets you delete unwanted objects from selected Oracle Applications environments along a migration path. After adding the unwanted objects to an archive set, you can mark them for deletion. When you migrate an archive set containing objects marked for deletion to an environment, Stat deletes them from that environment. However, you can always recover deleted objects since they remain archived in the Stat Repository.

To mark objects for deletion:
1
Add the objects to the archive set.
2
When the Archive Set has completed, open the Migration Flags tab of the archive set.
3
In the Action field, change the setting to Delete.
4
Click OK.

If you decide that you do not want to delete an object marked for deletion before you migrate it, go back to the Migration Flags tab and in the Action field change the setting to Copy. Stat is now configured to migrate the object as it normally would by placing a copy of the object in the target environment rather than deleting it.

* 
IMPORTANT: When you migrate an object marked for deletion, the object is deleted from that environment and cannot be included in any later archive sets taken from that environment. Because of this, it is recommended that you create an interim archive set of all of the objects that are marked for deletion before you migrate them. You can then migrate the interim archive set to each environment in which you want to delete the objects.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択