지금 지원 담당자와 채팅
지원 담당자와 채팅

Stat 6.3 - Install Notes

Installing Stat
Prepare for installation Unpack the 6.3.0 installer Install the Stat database Create a staging database (PeopleSoft Only) Install the Stat Client Configure the Stat database Update the System Maintenance table Install the Stat Central Agent Install the Stat Oracle Agent (Oracle E- Business Suite only) Configure the SYSTEM user account Update the PS Object Mover Instructions (PeopleSoft Only) Implement Stat

NMSSv630-3.sql

1
Locate the NMSSv630-3.sql script.
2
Find and replace the bracketed variables with the appropriate values.
•
Replace [DATABASENAME] with the name of the database (the name used on the system that connects to the database).

Execute the scripts

1
Using SQL Query Analyzer or Toad® for MSS, load and execute the scripts in order.
2
Copy the output of the script results to a file and save the file for review.
3
Execute NMSSv630-1.sql.
4
Execute NMSSv630-2.sql.
5
Execute NMSSv630-3.sql.
6
Review and save the script output to validate that the scripts ran without error.

Create a staging database (PeopleSoft Only)

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.

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 tables 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 StageORA.sql.
•
If running on SQL Server®, execute StageMSS.sql.
•
If running on DB2® execute StageDB2-ZOS.sql (for mainframe), or StageDB2-UNIX.sql (for AIX®/UNIX®).

These scripts complete the creation of a staging database. It is recommended that you create at least two 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 the Stat System Administration Guide, Chapter 4, General Maintenance Tables.

PeopleSoft on Oracle

1
Locate the StageORA.sql script in the scripts\Oracle\Staging folder.
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*Plus or Toad® in the PeopleSoft staging database as the PeopleSoft schema owner
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택