1 |
Locate the StageORA855.sql script. |
• |
[OWNER/PWD@DATABASENAME] Replace with the correct values for the PeopleSoft schema owner/password and staging database. |
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. |
Execute the script corresponding to your DB2 platform.
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]” |
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center