Chat now with support
Chat mit Support

Stat 6.3 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department Maintenance Issue Tracking Maintenance Country Maintenance Customer Maintenance Object Type Maintenance PeopleSoft Environment Connection Maintenance Pre/Post Migration Steps Parameters Oracle Applications Configuration Oracle Applications Connection Maintenance Generic Application Connection Maintenance Schema Object Parameters Maintenance Data Object Maintenance PeopleSoft Search Configurations Stat Report Definition Maintenance Version Control Management Connection Maintenance
Service Domain-Specific Maintenance Configuring the Stat Central Agent Email Configuration Object Security Appendix: Sample Service Domain Configuration Appendix: User Class Rights Appendix: Creating a Staging Database Appendix: Database Tuning Appendix: Oracle Applications File Type Directory Appendix: Ports and Firewalls Appendix: REST Web Services API Appendix: SOAP-Based Web Services API Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

Appendix: Creating a Staging Database

Staging databases are used when migrating archive sets from your Stat database to a PeopleSoft database. A staging database is essentially a mini-PeopleSoft database with no application data and minimal tools data. Once created it should be maintained and tuned the same as other PeopleSoft databases in your environment.

Depending on the volume of objects moved or number of PeopleSoft tools versions you are supporting, you may decide to have multiple staging databases. This section describes how to create a staging database in Stat.

•
For PS version 8.x and higher – The staging database can either be a PeopleSoft demo (DEMO) or system (SYS) database. For detailed instructions on creating this database, please see your PeopleSoft Installation and Administration Guide. Financial databases in particular have a large number of tables used for sorting data. These can be dropped from the staging database.

Once you have created your AUD, Demo, or System database, execute the appropriate script

•
If running on Oracle, execute StageORA855.sql
•
If running on SQL Server, execute StageMSS855.sql
•
If running on DB2 execute StageDB2-ZOS-855.sql (for mainframe), or StageDB2-UNIX-855.sql (for Aix/Unix)

These scripts complete the creation of a staging database. It is recommended that you create at least 2 staging databases. You may need to alter this script to match your platform.

* 
NOTE: Be aware of the following:
•
For each staging database you define in Stat, make sure the Reload Last Project at Startup option is deselected for that database in PeopleSoft App Designer. Stat may have difficulty auto-migrating objects from the staging database if this option is selected.
•
When migrating archive sets, the base language of the staging database must be the same as the base language of the environment that the archive set came from (i.e., the source). The base language option is specified in the PeopleSoft Environment Connection Maintenance table. For more information, see PeopleSoft Environment Connection Maintenance .

PeopleSoft on Oracle

1
Locate the StageORA855.sql script.
2
Replace the following variables:
•
[OWNER/PWD@DATABASENAME] Replace with the correct values for the PeopleSoft schema owner/password and staging database.
•
[SPOOLPT] Replace with the directory for the session log.
•
[PTAPP] Replace with the tablespace for the staging table
•
[PSINDEX] Replace with the tablespace for the staging table indexes
3
Run the modified script via Sql*Plusor Toad in the PeopleSoft staging database as the PeopleSoft schema owner

PeopleSoft on SQL Server

1
Locate the StageMSS855.sql script.
2
Find and replace the variable [DATABASENAME] with the name of the database.
3
Using Enterprise Manager, go into SQL Server Analyzer from Tools on the menu bar. Log in as sa with SYSTEM-level access and open the modified scripts. After running each script, copy the output of the script results to a file and save the file for review.

PeopleSoft on DB2

Execute the script corresponding to your DB2 platform.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen