Oracle SQL Scripts for PeopleSoft
| t_lock.sql Updated 29.10.2006 | This script implements a DDL trigger to prevent accidental lost of database objects that are not managed by PeopleTools, but which are related to tables specified in PeopleTools. It checks for indexes, triggers, primary key constraints, materialized view logs, and materialized views. It also checks whether the table is partitioned, clustered, index organised, or global temporary. The script contains a test script that will check whether the trigger is working properly. See the PeopleSoft DBA Blog entry, DDL Triggers to prevent loss of database objects not managed by PeopleTools for a full description. |
| mvtrunc_lock.sql Updated 1.11.2006 | This script implements a DDL trigger to prevent TRUNCATE operations on tables with Materialized View logs.The script contains a test script that will check whether the trigger is working properly. See the PeopleSoft DBA Blog entry, 'Truncating a Table does not affect the Materialized View Log ' for a full description. |
| colaudit.sql Updated 28.3.2004 | This script performs a series of checks on the PeopleTools tables that are not done by PeopleSoft's DDDAUDIT and SYSAUDIT reports. In particular it report on differences in the definitions, number or position of columns in tables, indexes or views. The script also generates a project in Application Designer that holds all the objects that may need to be rebuilt. |
| request gpbuild.sql Updated 22.3.2004 | The presentation Configuring Global Payroll for Optimal Performance recommends physically partitioning Global Payroll result tables to match the logical streaming, and converting working storage tables to Oracle Global Temporary tables. Application Designer cannot generate the DDL for partitioned tables. This script will generate scripts that will rebuild payroll result tables with partitioning. This concept is explained in more detail in the document Configuring and Operating Streamed Processing in PeopleSoft Global Payroll, including a step-by-step guide on implementation. |
Monitoring Scripts
The following scripts have been developed by Go-Faster to provide remote performance monitoring. They are provided on this website without explanation or support.
| tuxmon Updated 22.3.2005 | The tuxmon script monitors the behaviour of a Tuxedo application server running on a Unix system. It collects metrics only (no person information) about the activity in a Tuxedo domain. The output can be emailed to a specified e-mail address. If you send the output to monitor@go-faster.co.uk I will provide a free analysis. NB: From PeopleTools 8.44, the data collected by Tuxmon can be obtained from the PeopleSoft Performance Monitor, and there is no point in using Tuxmon on these systems.. The scripts to receive and analyse the output are not available. latest updates: |
| tuxmon.nt Released 6.1.2005 | This is a primitive Windows version of the tuxmon script. It uses a simple batch script that can be run from the Windows scheduler. An awk program formats the output file. They can also be sent to monitor@go-faster.co.uk for analysis. |
| tkmailem | The tkmailem script is used to process and e-mail TKPROF output for batch processes that are set to trace by a trigger. |
Caveat: All the scripts available from this website are provided without warranty or support. SQL are designed to be run from SQL*Plus against a PeopleTools 8 database on Oracle. There is no guarantee that any of the content of this website is error free, rather that there are certainly errors and inconsistencies!
© Go-Faster Consultancy Ltd. 2007