Chat now with support
Chat with Support

Stat 6.0 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department 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: Stat Web Services Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

PeopleSoft on Oracle

1
Locate the StageORA855.sql script.
[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

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.

Mainframe

1
Locate the StageDB2-OS390-855.sql script.
[DATABASENAME1] Replace with the name of the database (the name used on the system that connects to the database)
[TABLETBSPC1] Replace with tablespace for the new table. Usually use an existing tablespace, so DB2 utilities (that run at the tablespace level) do not have to be modified for the new tablespace (example: image copy).
[DATABASENAME2] Replace with the name of the database (for example PSPTDMOX)
[CREATORID] Replace with the creator/owner id. Requires the [USERID] to be able to set current sqlid to this [CREATORID] secondary authorization RACF group. Would need to connect [USERID] to the RACF group [CREATORID].
[STOGRPNAME] Replace with the Stogroup name for the index. Requires the grant “GRANT USE OF STOGROUP [STOGRPNAME] TO [CREATORID]”
Related Documents