PeopleSoft Enterprise Performance on Oracle 10g Database

7/27/2011

PeopleSoft Red Paper

PEOPLESOFT 8 BATCH PERFORMANCE ON ORACLE 9I DATABASE 7/27/2011
Reference Number: Product(s): Release(s): Revision Number:

PeopleSoft 8 Batch Performance on Oracle 9i Database

All Enterprise products PeopleSoft 8.x, 9.x

Contains:
√ PeopleSoft Performance Tips √ Database Tuning Tips √ SQL Query Tuning Tips √ Use of Database Features √ Capturing Traces

© Copyright © 2006 Oracle, Inc. All rights reserved.

i

7/27/2011

PeopleSoft Red Paper

Table of Contents
Table of Contents ....................................................................................................................................................ii Chapter 1 - Introduction...........................................................................................................................................1 Structure of this Red Paper Related Materials 1 1

Chapter 2 - Generating Statistics...........................................................................................................................2 Manually Gathering Table Statistics 2 Sample DBMS_STATS Command:............................................................................................................................................3 Generating Statistics for Data dictionary tables 3 Generating System Statistics ......................................................................................................................................................4 Statistics at Runtime for Temporary Tables 4 Example.......................................................................................................................................................................................4 Turning off %UpdateStats...........................................................................................................................................................5 Modify %UpdateStats to use Analyze command:......................................................................................................................5 Tuning off Dynamic Sampling:...................................................................................................................................................9 Histograms 9 What are Histograms? .................................................................................................................................................................9 Candidate Columns for Histograms Within PeopleSoft Applications.....................................................................................10 Creating Histograms..................................................................................................................................................................10 Viewing Histograms..................................................................................................................................................................10 Chapter 3 - Dedicated Temporary Tables.............................................................................................................11 What are Dedicated Temp Tables? 11 Performance Tips for Dedicated Temp Tables.........................................................................................................................11 Application Engine Performance with Dedicated Temporary Tables 11 How do temp tables work in Application Engine?...................................................................................................................12 Test case explaining temp table behavior.................................................................................................................................12 Creating PeopleSoft Temporary Tables as Oracle Global Temp Tables (GTT) 14 What are Global Temporary Tables?........................................................................................................................................14 Can GTTs be used in place of Dedicated Temp Tables?.........................................................................................................14 Chapter 4 - Tablespace Selection..........................................................................................................................14 Locally Managed Tablespaces 15 Advantages of Locally Managed...............................................................................................................................................15 Space Management....................................................................................................................................................................15 Locally Managed - AUTO ALLOCATE..................................................................................................................................15 Locally Managed - UNIFORM EXTENT ................................................................................................................................15 Temporary Tablespaces 15 Tempfile based...........................................................................................................................................................................16 UNDO Management 16 Automatic Undo Management...................................................................................................................................................16 Chapter 5 - Maintaining Indexes ...........................................................................................................................17 Index Tips Rebuilding of Indexes Function Based Indexes
© Copyright © 2006 Oracle, Inc. All rights reserved.

17 17 18 ii

7/27/2011

PeopleSoft Red Paper

Chapter 6 - Cursor Sharing....................................................................................................................................20 Use of Bind Variables 20 Application Engine - Reuse Flag...............................................................................................................................................20 SQR/COBOL - CURSOR_SHARING 23 Pros and Cons of CURSOR_SHARING...................................................................................................................................24 Chapter 7 - Batch Server Selection.......................................................................................................................26 Scenario 1: Process Scheduler And Database Server on Different Boxes Scenario 2: Process Scheduler and Database Server on one BOX What is the recommended scenario? 26 26 27

Chapter 8 - Capturing Traces................................................................................................................................28 Online Performance Issues 28 Configuration Settings for Tracing an Online Process.............................................................................................................28 Application Engine Performance Issues 30 Configuration Settings for Tracing an AE Process on the Application Engine.......................................................................30 Configuration Settings for Tracing an AE Process on the Database........................................................................................31 COBOL Performance Issues SQR Reports Performance Issues ORACLE Performance Issues Generating Explain Plan for SQL Using “sqltexplain.sql” 33 33 33 34

Automatic Workload Repository (AWR) 34 Generating a HTML or Text AWR Report:..............................................................................................................................35 AWR report analysis:.................................................................................................................................................................35 Appendix A – Sample script to gather statistics on tables................................................................................40 Appendix B – Validation and Feedback................................................................................................................45 Customer Validation Field Validation 45 45

Appendix C - References.......................................................................................................................................46 Appendix D – Revision History.............................................................................................................................47 Authors.......................................................................................................................................................................................47 Reviewers ..................................................................................................................................................................................47 Revision History........................................................................................................................................................................47

© Copyright © 2006 Oracle, Inc. All rights reserved.

iii

7/27/2011

PeopleSoft Red Paper

Chapter 1 - Introduction
This Red Paper is a practical guide for technical users, database administrators, and programmers who implement, maintain, or develop applications for a PeopleSoft system. In this Red Paper, we discuss guidelines on how to improve the performance of PeopleSoft applications in the Oracle 10g environment. Much of the information contained in this document originated within the PeopleSoft Benchmarks and Global Support Center and is therefore based on "real-life" problems encountered in the field. The issues that appear in this document are the problems that prove to be the most common or troublesome.

STRUCTURE OF THIS RED PAPER
This Red Paper provides guidance to get the best performance of PeopleSoft in the Oracle database environment. Keep in mind that PeopleSoft updates this document as needed so that it reflects the most current feedback we receive from the field. Therefore, the structure, headings, content, and length of this document is likely to vary with each posted version. To see if the document has been updated since you last downloaded it, compare the date of your version to the date of the version posted on Customer Connection.

RELATED MATERIALS
This paper is not a general introduction to environment tuning and we assume that our readers are experienced IT professionals, with a good understanding of PeopleSoft’s Internet Architecture and Oracle database. To take full advantage of the information covered in this document, we recommend that you have a basic understanding of system administration, basic Internet architecture, relational database concepts/SQL, and how to use PeopleSoft applications. This document is not intended to replace the documentation delivered with the PeopleTools 8 or 8.4 PeopleBooks. We recommend that before you read this document, you read the PeopleSoft application related information in the PeopleBooks to ensure that you have a well-rounded understanding of PeopleSoft batch process technology. Note: Much of the information in this document eventually gets incorporated into subsequent versions of the PeopleBooks. Many of the fundamental concepts related to performance tuning in PeopleSoft PeopleBooks: • PeopleSoft Installation Guide - Oracle Tuning chapter

Additionally, we recommend that you read the Oracle 10g database administration and performance tuning guides.

© Copyright © 2006 Oracle, Inc. All rights reserved.

1

query performance depends greatly on appropriate table and index statistics.7/27/2011 PeopleSoft Red Paper Chapter 2 . For example.Generating Statistics When using Oracle's Cost Based Optimizer (CBO). you need new statistics on the average row length. time and window of each organization. ANALYZE will be de-supported in future releases of Oracle. You can determine whether this job exists by viewing the DBA_SCHEDULER_JOBS view. New statistics should be gathered after a schema object's data or structure are modified in ways that make the previous statistics inaccurate. Cursor invalidation could cause severe performance degradation. A sample script to provide this functionality is listed in the Appendix. that are considered “stale” or “missing” by the database. It is also recommended that only tables and indexes. It is not recommended that statistics be gathered on objects during peak operational hours. business rules. Maintenance of these statistics is critical to optimal database and query performance. the “temporary” object statistics are not updated with improper values. After updating data in a table. It is recommended to disable this job after initial execution. statement is listed below. All rights reserved. 2 . Only “non-temporary” PeopleSoft tables and indexes are recommended to have their statistics updated.You should use DBMS_STATS package to update statistics. At database creation. END. MANUALLY GATHERING TABLE STATISTICS The DBMS_STATS package provides the ability to generate statistics in parallel by specifying the degree of parallelism.DISABLE('GATHER_STATS_JOB'). the over all time needed to regenerate statistics on a nightly/weekly/monthly basis is reduced. To disable the GATHER_STATS_JOB execute the following SQL*Plus command: BEGIN DBMS_SCHEDULER. Inc. Oracle 10g Scheduler contains a default nightly job which attempts to maintain these vital statistics. collect new statistics on the number of rows. and re-generate statistics on them which is not desirable as many will not contain data. The ability to generate statistics in parallel significantly reduces the time needed to refresh object statistics. Note: The use of procedures within DBMS_STATS is recommended exclusively. SELECT * FROM DBA_SCHEDULER_JOBS WHERE JOB_NAME = 'GATHER_STATS_JOB'. after loading a significant number of rows into a table. By re-generating statistics only on “stale” or “missing” objects. have their statistics re-generated. The default “GATHER_STATS_JOB” will pick up the “temporary” tables. A sample SQL Since this job does not/cannot take into account the requirements for PeopleSoft. It is advisable to gather statistics periodically for objects where the statistics become stale over time because of changing data volumes or changes in column value. By generating statistics only on the “non-temporary” tables and indexes. You need to work with your DBA to come up with a strategy to do that. it is not recommended to allow this job to run after it has initially executed. / The reasoning for this recommendation is because PeopleSoft Application Engine (AE) programs use many “standard” Oracle tables as PeopleSoft “temporary” tables. © Copyright © 2006 Oracle. It is not possible to recommend a single command line on how to update statistics nor the frequency on when to update statistics since this is dependent on many factors like data distribution.

REPEAT : Collects histograms only on columns that already have histograms.DEGREE . Values between “5%” and “20%” tend to provide the best balance between speed and calculation accuracy. The default value for “ESTIMATE_PERCENT” is “DBMS_STATS. With the “CASCADE” parameter set to “TRUE. Inc.ESTIMATE_PERCENT . The default setting for “CASCADE” is “FALSE”. Oracle will automatically determine which columns require histograms and the number of buckets (size) of each histogram.AUTO_SAMPLE_SIZE =>'FOR ALL COLUMNS SIZE AUTO' => 5 => TRUE ).7/27/2011 PeopleSoft Red Paper Sample DBMS_STATS Command: EXECUTE DBMS_STATS. © Copyright © 2006 Oracle. Note: Specifying “NULL” for “ESTIMATE_PERCENT” will provide the same functionality as ANALYZE’s “COMPUTE”.PARTNAME .GATHER_TABLE_STATS( OWNNAME . this level of statistics may not be sufficient for the optimizer's needs if the data within the column is skewed.GATHER_DICTIONARY_STATS( estimate_percent DBMS_STATS. This note includes a set of notes which help DBA through examples to move updating statistics from ANALYZE to DBMS_STATS.options => => 5 => TRUE => 'GATHER AUTO' ). Using a value of “100” is not the same as “COMPUTE”. However.AUTO_SAMPLE_SIZE” and is the recommended value only if the data composition is unknown. 3 . GENERATING STATISTICS FOR DATA DICTIONARY TABLES It is recommended to generate statistics on dictionary tables after initial database is loaded with data and also whenever database size has increased considerably.” the associated indexes will also be analyzed. Data distribution is also gathered when using DBMS_STATS.CASCADE => 'ORAVOL' => 'PS_CUSTOMER' => NULL => DBMS_STATS. The default value is “For All Columns Size Auto”. An example of this command is as follows: EXECUTE DBMS_STATS.degree . The size_clause is defined as size_clause:= SIZE {integer | REPEAT | AUTO | SKEWONLY} • • • integer : Number of histogram buckets: Range [1 to 254]. The most basic information about the data distribution is the maximum value and minimum value of the column within a table.TABNAME . Execute tests to find the appropriate value. “AUTO_SAMPLE_SIZE” can perform slowly for large tables. AUTO : Determines the columns to collect histograms based on data distribution and the workload of the columns.cascade . With the “METHOD_OPT” parameter set to “For All Columns Size Auto”. • SKEWONLY : Determines the columns to collect histograms based on the data distribution of the columns. The index statistics cannot make use of this flag and does not run in parallel.METHOD_OPT . All rights reserved. Note: It is strongly recommended to read Note 237293. Note: Specifying the DEGREE will only help run gather table statistics (Partitioned or Non-Partitioned) in parallel.1 of Oracle Metalink. Sometimes.AUTO_SAMPLE_SIZE .

3.48 will issue the Oracle database command: DBMS_STATS. Doing so would update statistics on the temporary table prior to the table’s use in following SQL statements. Use the supplied script (DDLORA. Keeping the statistics up to-date for these tables is somewhat challenging. Beginning with PeopleSoft 8. or dedicated temporary tables in the batch processes. at runtime. the AE will ignore the %UpdateStats command after any uncommitted changes. A temporary table’s life cycle is as follows: 1. 4 . For example: © Copyright © 2006 Oracle. Due to the implicit commit feature that Oracle uses when performing DDL (Statistics gathering is considered DDL). These temporary tables will have few or no rows in the beginning of the process. if the programmer has requested. Note: User must have DBA privileges or GATHER_SYSTEM_STATISTICS role to update dictionary or system statistics. STATISTICS AT RUNTIME FOR TEMPORARY TABLES PeopleSoft uses shared and. an AE program can use the meta-SQL “%UpdateStats” after rows are populated into a temporary table. method_opt=> 'FOR ALL COLUMNS SIZE 1'. the ESTIMATE_PERCENT parameter was set to “1”. EXECUTE DBMS_STATS. Note: To reduce the increased overhead of DBMS_STATS at runtime (when compared to ANALYZE with estimate).DMS) to change the default setting or to add a required SAMPLE ROWS/PERCENT for the ESTIMATE clause. Inc.GATHER_TABLE_STATS (ownname=> [DBNAME]. estimate_percent=>1. All rights reserved.7/27/2011 PeopleSoft Red Paper Generating System Statistics When Oracle gathers system statistics. All rows are truncated (if dedicated) or deleted (if shared) at the beginning of an AE execution automatically. Note: PeopleSoft stores the default syntax for the gather stats command in a table PSDDLMODEL. it analyzes system activity in a specified time period (workload statistics) or simulates a workload (no workload statistics). 2. At the end of the process. these tables will again have few or no rows. Allowing the implicit commit may affect the restart capability of the program. All rows are truncated (if dedicated) or deleted (if shared) at the end of an AE execution. It is highly recommended that system statistics be gathered. Rows are populated. Note: Commit is required prior to executing the %UpdateStats statement.cascade=>TRUE). Example Command in SQL Step of an Application Engine program: %UpdateStats(%Table(INTFC_BI_HTMP)) This meta-SQL starting with Peopletools 8. This is not performed automatically.GATHER_SYSTEM_STATS procedure. tabname=>[TBNAME]. The statistics are collected using the DBMS_STATS.GATHER_SYSTEM_STATS (gathering_mode => 'NOWORKLOAD').

17. method_opt=> 'FOR ALL INDEXED COLUMNS SIZE 1'.7/27/2011 PeopleSoft Red Paper Let’s assume.5 InsBalT. Having the update statistics at the runtime incurs some overhead. CREATE OR REPLACE PACKAGE PSSTATS AS © Copyright © 2006 Oracle. 1. If you find any temporary table that was not updated during the run time. tabname=>[TBNAME]. estimate_percent=>5.2. Edit the DDLORA.18 .. 5 .0. tabname=>[TBNAME].0. If this feature is to be turned off.. Turning off %UpdateStats Note: Due to this change affecting the entire process scheduler.cascade=>TRUE). then plan to use a manual method of updating the statistics. estimate_percent=>80.UpdStat. 4.UpdStat) (SQL) RECSTATS PS_JCF_BAL_TAO4 LOW /  Row(s) affected: 1 C o m p i l e Total SQL Statement E x e c u t e 2 Count Time 19..cascade=>TRUE). you can review your AE trace. it is highly not recommended to turn this feature off.$long DBMS_STATS..GATHER_TABLE_STATS (ownname=> [DBNAME].$long DBMS_STATS.S Count Time 2 0.. Inc....0. All rights reserved. The second one is used for the HIGH option of %UpdateStats. Make sure the temporary table statistics have been handled as shown above. method_opt=> 'FOR ALL INDEXED COLUMNS SIZE 1'. // 2. check the process scheduler documentation.2.0. we want to change the ESTIMATE_PERCENT option of LOW option to be 5% and HIGH option to be 80%. // 5.0 Once you confirm that using DBMS_STATS to update statistics is causing a lot of overhead when compared to “Analyze with estimate” when using %Updatestats.5 0 F e t c h Count Time 0. Run the modified DDLORA.DMS delivered script: The first occurrence of the DBMS_STATS is used for the LOW option of %UpdateStats. and look for statements that used the “RECSTATS” command: -.GATHER_TABLE_STATS (ownname=> [DBNAME].0 Time 19. you can revert %Updatestats to use the Analyze command by doing the followings: Step 1: Create PSSTATS package as follows: Login SQLPLUS as PeopleSoft Dbowner to create the following PSSTATS package.DMS through DataMover. Modify %UpdateStats to use Analyze command: If you suspect that DBMS_STATS is causing performance degradation of your AE process.InsBalT.(GL_JEHDR.44.

END PSSTATS.7/27/2011 PeopleSoft Red Paper PROCEDURE ANALYZE_TABLE (tab_name VARCHAR2. Inc. EXECUTE IMMEDIATE command_text. BEGIN if stats_mode <> 'HIGH' then command_text := 'ANALYZE TABLE '||tab_name||' ESTIMATE STATISTICS'. All rights reserved. stats_mode varchar2). / CREATE OR REPLACE PACKAGE BODY PSSTATS AS PROCEDURE ANALYZE_TABLE (tab_name IN VARCHAR2. end if. 6 .1) Navigate to DDL Model Defaults Navigation: PeopleTools -> Utilities -> Administration -> DDL Model Defaults Click the “Search” button and then choose “Oracle” Platform. / Step 2: Modify SQL#4 and SQL#5 DDL Model Defaults for Oracle Platform. 2. else command_text := 'ANALYZE TABLE '||tab_name||' COMPUTE STATISTICS'. stats_mode varchar2) IS command_text VARCHAR2(2000). END PSSTATS. © Copyright © 2006 Oracle. END ANALYZE_TABLE.

Inc. Copy “Model SQL” from PIA page to text file so that you can revert back to using DBMS_STATS in the future if you so choose. 2. All rights reserved.3) Replace SQL#4 (out of 5) for Oracle Platform.2) Choose SQL #4 (out of 5) for Oracle Platform. © Copyright © 2006 Oracle. 7 .7/27/2011 PeopleSoft Red Paper 2.

stats_mode=>'HIGH').4) Choose SQL #5 (out of 5) for Oracle Platform.analyze_table(tab_name=>[TBNAME].7/27/2011 psstats. © Copyright © 2006 Oracle. Copy “Model SQL” from PIA page to text file so that you can revert back to using DBMS_STATS in the future if you so choose.analyze_table(tab_name=>[TBNAME]. psstats.5) Replace SQL#5 (out of 5) for Oracle Platform.stats_mode=>'LOW'). PeopleSoft Red Paper 2. All rights reserved. Inc. 2. 8 .

CBO uses data within the histograms to get accurate estimates of the distribution of column data. How does Dynamic Sampling work? Oracle determines at compile time whether a query would benefit from dynamic sampling. This feature is controlled by the initialization parameter named OPTIMIZER_DYNAMIC_SAMPLING. It is not recommended to use Analyze to update statistics during regular database maintenance window. Since most of PeopleSoft programs use %UpdateStats to manage statistics of our temporary tables so we recommend to turn this parameter off by setting the following: OPTIMIZER_DYNAMIC_SAMPLING = 0 HISTOGRAMS What are Histograms? Histograms provide improved selectivity estimates in the presence of data skew. © Copyright © 2006 Oracle. a recursive SQL statement is issued to scan a small random sample of the table's blocks. so that all column values in a band fall within the same range.7/27/2011 PeopleSoft Red Paper This change will affect any PeopleSoft programs that use %UpdateStats. and to apply the relevant single table predicates to estimate predicate selectivities. and DataMover import scripts with option “Set statistics on” (On is the default value). in some cases. to estimate table cardinality. Note: Due to this change affecting all the programs using %UpdateStats. Inc. If so. A histogram partitions the values of the column into bands. The sample cardinality can also be used. resulting in optimal execution plans with non-uniform data distributions. it is highly recommended to do regression test throughly before implementing in Production. 9 . All rights reserved. Any column and index statistics are also collected on the fly. Tuning off Dynamic Sampling: Dynamic Sampling was introduced in Oracle 9i.

Column is used in the where clause but contains a bind variable instead of a literal. 3. the automatic creation of histograms is deactivated. In general. Note: If any other value for “METHOD_OPT” is provided (ex. ORD_STATUS are likely candidates that benefit from histograms. 2. the “SIZE AUTO” value instructs the “DBMS_STATS” procedure that only columns benefiting from histograms are to be generated. So. Based on column usage within runtime SQL “where clauses” and the amount of data skew within the column. Please refer to Oracle documentation for more details. Inc. Histograms. Have a highly skewed data distribution. histograms should be created on: 1.7/27/2011 PeopleSoft Red Paper Oracle uses height-balanced histograms or frequency based histograms based on the number of distinct values and the number of bands. are static and only change when new statistics are generated with the “SIZE” option within the DBMS_STATS procedures. the use of BP is not recommended. the CBO can make fairly accurate estimates about the cost of executing a particular statement without the use of histograms. Column is unique. For uniformly distributed data. there are maintenance and storage costs for using them. All rights reserved. 10 . Histograms are persistent objects. Column is not used in WHERE clauses of queries. “… SIZE 1” or “… SIZE REPEAT”). Candidate Columns for Histograms Within PeopleSoft Applications Histograms can affect performance and should be used only when they substantially improve query plans. Creating Histograms Creation of specific column histograms is no longer needed as long as “DBMS_STATS” procedures are used with the “METHOD_OPT” parameter containing “SIZE AUTO”. But. Columns that are frequently used in WHERE clauses of queries. Viewing Histograms Information about whether a table contains histograms can be displayed using the following dictionary views: • • • USER_HISTOGRAMS ALL_HISTOGRAMS DBA_HISTOGRAMS The number of bands within a column’s histogram can be displayed using the following dictionary views: • • USER_TAB_COLUMNS ALL_TAB_COLUMNS • DBA_TAB_COLUMNS © Copyright © 2006 Oracle. like all other optimizer statistics. Note: “Bind Peeking” (BP) was designed to “fix” the last bullet point above. Columns such as PROCESS_INSTANCE. Literal value is provided instead of using a bind variable for the given column in the where clause. due to additional issues BP causes. Histograms are not useful for columns with the following characteristics: • • • • Column data is uniformly distributed.

11 . APPLICATION ENGINE PERFORMANCE WITH DEDICATED TEMPORARY TABLES © Copyright © 2006 Oracle. And the required number of instances is also specified for each AE program.7/27/2011 PeopleSoft Red Paper Chapter 3 . Performance Tips for Dedicated Temp Tables If issues are found with parallel truncates on dedicated tempory tables. Inc. This may lessen the contention during parallel truncates. then the additional processes will be abandoned or the base temp tables will be used depending on the Runtime radio button selection in the above window. When implemented on Oracle databases. Required temp tables are linked to the AE program in the program property window. create seperate tablespace for the these tables with a block size that is greater (if possible) than the current standard tablespace block size. These are regular Oracle tables but flagged as temporary in the PeopleSoft dictionary tables. All rights reserved.Dedicated Temporary Tables WHAT ARE DEDICATED TEMP TABLES? Batch processes written in Application Engine use PeopleSoft designated temporary tables (also called as “Dedicated Temporary Tables”) for better processing. PeopleSoft designated temporary tables are built using Oracle tables. If the number of programs run are more than the specified count (10 in this example). Here is the property window for the AE program Bill Finalization (BIIF0001): The instance count specified here is the limit on the number of a temp table's instances that can be used when multiple instances of the program are run. This technique minimizes potential locking issues and improves processing time. configure the initialization parameters of the database to include a seperate buffer cache for this new block size. Then.

Tools Properties AE Properties Setup the Instance Count to the required value. Choosing the Continue for the runtime option will use the base temp table if there are no temp table instances available at the time of run. that means that the program will not be called from online. Temp table settings Setup the Temp Tble Instance (online) as per the requirement. © Copyright © 2006 Oracle. the appropriate temp table instance will be used during the runtime. All rights reserved. unless you are using EPM. Number of temp table instances Number of Temp Tables (Online) = 3 Number of Temp Tables (AE Program) = 3 Scenario 1: ‘Batch Only’ option is not selected Total number of temp table instances created for each temp table associated to the AE program = Base Temp Table + Number of Temp Tables (Online) + Number of Temp Tables (AE Program) = 1+3+3 = 7 Scenario 2: ‘Batch Only’ option is selected Total number of temp table instances created for each temp table associated to the AE program = Base Temp Table + Number of Temp Tables (AE Program) = 1+3 = 4 In this example we will be looking at Scenario 2. Test case explaining temp table behavior Here is the sample scenario that explains the temp table usage. 12 . This should be equivalent to the number of concurrent streams you are planning to run. Inc.7/27/2011 PeopleSoft Red Paper How do temp tables work in Application Engine? Based on the number of temp tables that are associated to an application engine program and the number of instances setup for the program. Temp Tble Instance (Total) will be same as the online number. You don’t need to change this setting unless you are advised to do so. PROCESS PROCESS 4 5 If the Batch Only option is selected.

temp table instance 1 will be used. 3. Recommendations 1. When the user tries to run the 4th.2. Always setup an adequate number of temp table instances to achieve good performance. Number of concurrent executions The number of concurrent executions in this example is 6. So. and 6th streams. 3. Max API Aware value should be larger than or equal to the total of Max Concurrent value set of all the process types.7/27/2011 PeopleSoft Red Paper Temp table AE PROCESS AE PROCESS STREAM 4 AE PROCESS STREAM 5 STREAM 6 TAB1_TAO TAB2_TAO TAB3_TAO TAB4_TAO Not advisable AE PROCESS STREAM 1 TAB1_TAO1 TAB2_TAO1 TAB3_TAO1 TAB4_TAO1 AE PROCESS STREAM 2 TAB1_TAO2 TAB2_TAO2 TAB3_TAO2 TAB4_TAO2 AE PROCESS STREAM 3 TAB1_TAO3 TAB2_TAO3 TAB3_TAO3 TAB4_TAO3 allocation When the program runs for the first time. 13 . As multiple streams use the same base temp table. setup a temp table instance even if you are planning to run only one process at a time. there could be a possibility of contention. To overcome the drawbacks described above. 1. Frequent deletes and inserts could cause fragmentation for the base temp tables. Drawbacks Use of base temp tables for any AE process is not recommended due to the following reasons. Setup required value for the process scheduler server in the max concurrent field. where as the number of available temp table instances are just 3. the program will not find an available temp table instance and will use the base temp table. © Copyright © 2006 Oracle. AE Program issues a delete for the base temp tables while it truncates the temp table instances. Runtime table statistics on the base temp tables are ignored. The subsequent parallel streams will use the rest of the instances in sequence. 2. The final three are using the base temp tables. the first three concurrent streams will use the instance counts 1. 4. Inc.5th. the first three processes are using the temp table instance. 2. In this example. All rights reserved. and 3.

Can GTTs be used in place of Dedicated Temp Tables? As of now PeopleSoft does not provide a script or utility to create the GTTs. These tables are session specific.Tablespace Selection © Copyright © 2006 Oracle. 14 . there is no direct method to specify the dedicated temp tables as GTTs. Setup required number of PSAESERV processes on the process scheduler server. Chapter 4 . The max instance should reflect the max concurrency set for process type . Table data is deleted once the session is closed or the transaction is committed. it gives the option to preserve or delete the rows after the commit. Settings for Application Engine Tuxedo Server . Inc. Also. During the table creation time.7/27/2011 PeopleSoft Red Paper 4. Creating PeopleSoft temporary tables as GTTs is not recommended. [PSAESRV] .------------------------------------------------------------------------. Instances of a global temporary table will be created at the runtime in the user's temporary tablespace. CREATING PEOPLESOFT TEMPORARY TABLES AS ORACLE GLOBAL TEMP TABLES (GTT) What are Global Temporary Tables? Oracle8i introduced Global Temporary Tables (GTT). there is no way to restart the program. in the Server Definition page in Process Scheduler Manager Max Instances =12 5. All rights reserved. which can be used as temporary processing tables for any batch process. Important caution while using the GTTs is Application Engine's ability to restart: Since GTTs lose the data when the session ends. defined with a generic process type of Application Engine as defined . Use of DTTs is recommended even when the process is running in single stream.========================================================================= .========================================================================= .

LOCALLY MANAGED TABLESPACES Locally Managed Tablespaces (LMT) are the default starting in Oracle 9i. Locally Managed . Space Management • • • • Free extents recorded in bitmap (so some part of the tablespace is set aside for bitmap) Each bit corresponds to a block or group of blocks Bit value indicates free or unused Common views used are DBA_EXTENTS and DBA_FREE_SPACE Locally Managed . the size of each extent would be fixed to the specified size. In order to use different block sizes in a database. CREATE TABLESPACE TS_PERM_LOC_UNI size 100M datafile '/perm/ora/ts_perm_loc_uni. 15 .dbf' EXTENT MANAGEMENT LOCAL AUTO ALLOCATE.AUTO ALLOCATE With this option. Advantages of Locally Managed • • • • • Reduced recursive space management Reduced contention on data dictionary tables and space management latches No coalescing required No rollback generated for space allocation and de-allocation activities. Make sure to specify appropriate size to avoid the table creation with more number of extents. Fragmentations is reduced but not completely eliminated. The creation of dictionary managed tablespaces is scheduled for de-support by Oracle. Having the consistent extent size eliminates wastage of tablespace as "holes". CREATE TABLESPACE TS_PERM_LOC_AUTO size 100M datafile '/perm/ora/ts_perm_loc_auto. You can use the BLOCKSIZE clause to specify a non-database default block size for the tablespace. and the integer you specify in this clause must correspond with the setting of one DB_nK_CACHE_SIZE parameter setting. Uniform extent gives best predictability and consistency.UNIFORM EXTENT With this option. medium. This is the preferable method if the tablespace holds the objects with various sizes. It will be easier for the DBA to do capacity planning but proper planning should be done to determine the optimum extent size. TEMPORARY TABLESPACES © Copyright © 2006 Oracle. Planning to create different category tablespaces such as small.dbf' EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K.7/27/2011 PeopleSoft Red Paper PeopleSoft's supplied create scripts will create only Locally Managed tablespaces. and large with different uniform extent sizes and placing the tables in an appropriate tablespace depending on its size may give optimal performance. With this option. the extent size is managed by Oracle depending on the object size. All rights reserved. you must have the DB_CACHE_SIZE and at least one DB_nK_CACHE_SIZE parameter set. extent size allocation is performed by Oracle. Inc. Object storage clause specification is not required (and is ignored) with these tablespaces. Extent management is done within the datafile/tempfile using the bitmaps.

It flags as an error when the tablespace assigned is not a true Oracle temporary tablespace. The ONLY way to have automatic undo management requires you specify an undo tablespace. Oracle server handles the creation and allocation of space among the undo segments automatically. In this type of tablespace. DEFAULT TEMPORARY TABLESPACE TEMPTS1 ……… UNDO TABLESPACE UNDOTS DATAFILE '/data4/oradata/INVDB/undo/undots01. You need to specify the UNDO_TABLESPACE initialization parameter to tell oracle which tablespace to use for undo and then create that tablespace while creating the database. All rights reserved. a regular tablespace cannot be assigned as the temporary tablespace. Inc. UNDO MANAGEMENT Automatic Undo Management This is the preferred method of undo management and is the default when creating a new 10g database.7/27/2011 PeopleSoft Red Paper Every database user should be assigned a default temporary tablespace(s) to handle the data sorts.dbf' EXTENT MANAGEMENT LOCAL LOGFILE …. The sort segment created for each instance is reused. 16 . CREATE TEMPORARY TABLESPACE TS_TEMP_LOC_UNI size 100M tempfile '/temp/ora/ts_temp_loc_uni. This will give better extent management and space management than the datafile based ones. convert the database to use automatic UNDO management instead of rollback segments. All processes performing sorts reuse existing sort extents of the sort segment. If a database is up-graded from 9i.dbf' EXTENT MANAGEMENT LOCAL UNIFORM SIZE 500K. Automatic undo management lets you allocate undo space in a single undo tablespace. This should be a preferred method for any Temporary Tablespace. Tempfile based Oracle introduced this new type that uses tempfile instead of datafile. only the Locally Managed with UNIFORM EXTENT management is allowed. © Copyright © 2006 Oracle. Advantages : • • • Space management (extent allocation and de-allocation) is locally managed. You cannot specify nonstandard block sizes for a temporary tablespace. rather than allocating a segment (and potentially many extents) for each sort. Example : CREATE DATABASE INVDB … DATAFILE '/data3/oradata/INVDB/system/system01. In Oracle 10g.dbf' SIZE 1024M SIZE 5048M. instead of distributing undo space in a set of statically allocated rollback segments.

2 inclusive. Dated 20-OCT-2005: This note is labeled for version 8i only.1 before using this script. 3. Note: If a very very large index is evaluated. pros and cons for selecting it and index rebuilding.3 to 10. Dated 20-OCT-2005: This note is labeled for versions 7. 4. This decision causes the deleted blocks to linger within the index until it is rebuilt. © Copyright © 2006 Oracle. This note provides a script that may be used to determine whether an index may be a candidate for rebuilding. As of this writing. Examine the available indexes and remove any of the unused indexes to boost the performance of Insert/Update/Delete DML. Please read note 77574. Three metalink notes were found that might provide a little insight as to when to rebuild or coalesce an index.  Note 77574.Maintaining Indexes PeopleSoft supplied indexes are generic in nature.7/27/2011 PeopleSoft Red Paper Chapter 5 . 2. Consider adding additional indexes depending on your processing/performance needs. All rights reserved. Note about use of “Index Skip Scan” access method: “Index Skip Scan” is not a recommended access method as it can be very slow when accessing a large index.1. Typically this can happen when a large number of rows have been deleted from the table.1 “Script: Lists All Indexes that Benefit from a Rebuild”. Dated 06-MAY-2005: This note is labeled for versions 7. Perform thorough system analysis prior to deleting any index. For runtime performance reasons. an index not used within a batch process may be useful with an online page. a threshold of “5 or more” levels may be too shallow. Within the index. but physically they still linger within until the index is rebuilt. Index deletion could severely impact other program’s performance. Oracle has consciously decided to not coalesce near-empty blocks or re-balance physical index blocks. these deleted/empty blocks must still be read.1 “Guidelines on When to Rebuild a B-Tree Index”.Coalescing Indexes”. REBUILDING OF INDEXES It is recommended that an index should be rebuilt when a performance issue is found where a SQL execution plan is accessing an index either by a “range scan” or “full index scan” and a significant number of logical IOs (and may be physical IOs) are witnessed for a relatively small number of rows returned by the scan. It uses the suggested values from note 77574.0 to 9i inclusive. Note 122008.   17 . During “Range Scan” and “Full Index Scan”. May indirectly be usable for version 10. Sometimes.1 and provides a good basis for determining whether an index should be rebuilt. INDEX TIPS 1. Inc. Review the index recommendation document supplied by the product to see if any of the suggestions apply to your installation. Depending on the customer's business needs and data composition. This note is referenced by note 122008. all the rows are logically deleted. Note 99618. but does provide the describing what “index coalescing” is.x. little information about index rebuilding criteria seems to be available pertaining specifically to 10g.1 “ORACLE8i . causing the performance degradation. Run the Oracle trace/TKPROF report for a process and check the access paths to determine the usage of indexes. The reverse may also be true. The following few tips will assist the DBA to manage indexes efficiently. index requirements may vary.

To find the real column name. gives no rows.NAME1 FROM PS_CUSTOMER WHERE NAME1 LIKE 'ADVENTURE%'. and provides the correct output.48. SQL> SETID CUST_ID NAME1 ----. All rights reserved.----------------SHARE 1008 Adventure 54 Query does not use the PS0CUSTOMER index so it takes a long time to return.CUST_ID.CUST_ID. In such cases. SQL> SETID CUST_ID NAME1 ----. Inc.NAME1 FROM PS_CUSTOMER WHERE UPPER(NAME1) LIKE 'ADVENTURE%'. SELECT SETID. it will show something like SYS_NC00033$ which is a system-generated column name. If data is stored in mixed case such as the above example. EFFDT DESC) TABLESPACE PSINDEX STORAGE (INITIAL 45056 NEXT 100000 MAXEXTENTS UNLIMITED PCTINCREASE 0) PCTFREE 10 PARALLEL NOLOGGING When you select the descending column name from DBA_IND_COLUMNS. 18 . © Copyright © 2006 Oracle.CUST_ID. you have to go look in COLUMN_EXPRESSION of DBA_IND_EXPRESSIONS.----------------SHARE 1008 Adventure 54 Query uses the PSFCUSTOMER index. SQL> No rows selected Query uses index PS0CUSTOMER and returns the result faster.--------------.--------------. the use of function-based indexes is helpful. Starting with PeopleTools 8. returns the query faster.----------------SHARE 1008 Adventure 54 Query uses index PS0CUSTOMER and returns the result faster. These indexes are considered as Function-based indexes in Oracle. SELECT SETID. SQL> SETID CUST_ID NAME1 ----. PeopleSoft generates indexes with DESCENDING column. It is recommended that customer support be contacted prior to a functional index creation.NAME1 FROM PS_CUSTOMER WHERE UPPER(NAME1) LIKE 'ADVENTURE%'. Here is an example: CREATE UNIQUE INDEX PS_GL_ACCOUNT_TBL ON PS_GL_ACCOUNT_TBL (SETID.NAME1 FROM PS_CUSTOMER WHERE NAME1 LIKE 'Adventure%'. the only way to get the result using a consistent case filter is by using the function “UPPER. But. CREATE INDEX ON PSFCUSTOMER ON PS_CUSTOMER (UPPER(NAME1)).” SELECT SETID.CUST_ID. Note: Please review the documentation pertaining to function based indexes prior to their creation. such as an arithmetic expression or an expression containing a package function.7/27/2011 PeopleSoft Red Paper FUNCTION BASED INDEXES A function-based index is an index on an expression. ACCOUNT. But. Test case: Table PS_CUSTOMER has an index PS0CUSTOMER with NAME1 as leading column: SELECT SETID.--------------. the data returned is correct.

column_name from dba_indexes a. All rights reserved.peoplesoft.dba_ind_columns b where b.b.column_position from dba_ind_expressions where index_name='PS_GL_ACCOUNT_TBL'.index_name order by column_position. Because of multiple Bugs (# 4939157 and 5092688) which cause wrong results or core dump from queries using functional indexes. We suggested that you go to the following link http://www4.column_expression.com/psdb. select index_name.7/27/2011 PeopleSoft Red Paper select a.index_name=b. Inc.index_name.index_type. 19 .index_name='PS_GL_ACCOUNT_TBL' and a.nsf/0/33440EC2DE7C886788257051005AEB72?OpenDocument to check the availability of patches and apply them accordingly to fix the problem and remove the following initialization parameter: _disable_function_based_index=TRUE © Copyright © 2006 Oracle. PeopleSoft had recommended to disable the functional indexes causing sql(s) that were relying on these indexes to perform in an inefficient manner.a.

That means. Relying on Oracle trace output to identify the SQL that are hard parsed due to literal instead of bind variables is somewhat difficult. The following is an example of of the AE trace(128): SQL Statement BL6100.10000001 UPDATE PS_PC_RATE_RUN_TAO SET RESOURCE_ID = %Sql(PC_COM_LIT_CHAR.0 Total Time 2. it is recommended that the Reuse Flag be set to “Yes” for all program steps.7/27/2011 PeopleSoft Red Paper Chapter 6 . When the statement is passed to the database it sends the statement with literal values. and COBOL have been rewritten to address this issue. etc. The only way to tell the application engine program to send the bind variables is by specifying the Re-Used flag for that statement that needs to use the bind variable. USE OF BIND VARIABLES The number of hard parses can be reduced to ‘one. it has to be parsed fully.%NEXT(LAST_RESOURCE_ID).10000001. but these variables are just PeopleSoft specific.S C o m p i l e Count Time 252 0.1. the database looks for an exact match of the SQL statement while parsing. This is referred to as a hard parse and is very expensive in both in terms of CPU used and in the number of latch gets performed. The following section gives some guidelines to follow to use the bind variables. 20 . Hard parsing happens when the Oracle server parses a query and cannot find an exact match for the query in the library cache. As Oracle deals with bind variables efficiently.5 F e t c h Count Time 0 0. Setting the CURSOR_SHARING value at the instance level is not recommended in a PeopleSoft environment.BL6100. there are some steps in AE processes that are not using bind variables.’ per multiple executes of the same SQL statement by coding the statement with bind variables instead of literals. such statements can typically be made to use bind variables.6 E x e c u t e Count Time 252 1. All rights reserved. The number of hard parses can be identified in a PeopleSoft Application Engine trace (128). Oracle introduced this new parameter CURSOR_SHARING as of Oracle8i. check the statement syntactically and semantically. Oracle has to allocate memory for the statement from the shared pool. This occurs due to inefficient sharing of SQL statements and can be improved by using bind variables instead of literal in queries.1 In Oracle Trace output such statements are shown as individual statements and each statement parses once. This happens when certain kinds of statements cannot handle bind variables in some platforms.20. By default its values is set to EXACT. Application Engine . If any customizations are performed. Example: Statement in PC_PRICING. In some situations.Cursor Sharing When a SQL statement that does not exist in the shared pool is executed.20) WHERE PROCESS_INSTANCE = %ProcessInstance © Copyright © 2006 Oracle. Inc.Reuse Flag PeopleSoft Application Engine programs use bind variables in the SQL statements. SQR. Some times hard parsing causes excessive CPU usage. Most of the PeopleSoft programs written in Application Engine.

(PC_PRICING. 21 .---------..---------0.16. All rights reserved.46..01 0.10000001.00 0.---------.5 F e t c h Count 0 Time 0.---------0.1 Oracle Trace Output ******************************************************************************** UPDATE PS_PC_RATE_RUN_TAO SET RESOURCE_ID = 10000561 WHERE PROCESS_INSTANCE = 419 AND BUSINESS_UNIT = 'US004' AND PROJECT_ID = 'PRICINGA1021' AND ACTIVITY_ID = 'ACTIVITYA2042' AND RESOURCE_ID = 'VUS004VA10210124050' AND LINE_NO = 1 call count ------.-----total 2 cpu elapsed disk query current -------.S Count 252 Time 0..-----Parse 1 Execute 1 Fetch 0 ------.01 0.00 0.Row(s) affected: 1 C o m p i l e Total SQL Statement BL6100.---------.. Inc.10000001) (SQL) UPDATE PS_PC_RATE_RUN_TAO SET RESOURCE_ID = 10000498 WHERE PROCESS_INSTANCE = 419 AND BUSINESS_UNIT = 'US004' AND PROJECT_ID = 'PRICINGA1' AND ACTIVITY_ID = 'ACTIVITYA1' AND RESOURCE_ID = 'VUS004VA10114050' AND LINE_NO = 1 / -.---------.7/27/2011 AND AND AND AND AND BUSINESS_UNIT = %Bind(BUSINESS_UNIT) PROJECT_ID = %Bind(PROJECT_ID) ACTIVITY_ID = %Bind(ACTIVITY_ID) RESOURCE_ID = %Bind(RESOURCE_ID) LINE_NO = %Bind(LINE_NO) PeopleSoft Red Paper Statement without Re-Use flag: AE Trace -.00 .6 E x e c u t e Count 252 Time 1.0 Time 2..00 0 0 0 -------.BL6100.00 0 0 0 0.01 0 2 5 rows ---------0 1 0 ---------1 Misses in library cache during parse: 1 Optimizer goal: CHOOSE Parsing user id: 21 (PROJ84) Rows ------1 2 Rows ------0 1 Row Source Operation --------------------------------------------------UPDATE PS_PC_RATE_RUN_TAO INDEX RANGE SCAN (object id 16735) Execution Plan --------------------------------------------------UPDATE STATEMENT GOAL: CHOOSE UPDATE OF 'PS_PC_RATE_RUN_TAO' © Copyright © 2006 Oracle.---------.---------.01 0 2 5 0.

---------.10000001.0 Time 0.22 0.---------.---------.---------.22 0 509 1284 rows ---------0 252 0 ---------252 Misses in library cache during parse: 1 Optimizer goal: CHOOSE Parsing user id: 21 (PROJ84) Rows Row Source Operation © Copyright © 2006 Oracle.4 F e t c h Count 0 Time 0.(PC_PRICING.22 0.S Count 1 Time 0.7/27/2011 2 PeopleSoft Red Paper INDEX GOAL: ANALYZED (RANGE SCAN) OF 'PS_PC_RATE_RUN_TAO' (UNIQUE) ******************************************************************************** You will see 252 different sqls in the tkprof similar to the one above.00 0..Bind variables: -1) 10000751 -2) US004 -3) PRICINGA1 -4) ACTIVITYA1 -5) VUS004VA10114050 -6) 1 -.57.-----total 253 cpu elapsed disk query current -------.---------0.-----Parse 1 Execute 252 Fetch 0 ------.10000001) (SQL) UPDATE PS_PC_RATE_RUN_TAO SET RESOURCE_ID = :1 WHERE PROCESS_INSTANCE = 420 AND BUSINESS_UNIT = :2 AND PROJECT_ID = :3 AND ACTIVITY_ID = :4 AND RESOURCE_ID = :5 AND LINE_NO = :6 / -.---------.00 0 0 0 -------.00 0 0 0 0..00 0..---------0.0 E x e c u t e Count 252 Time 0.4 Oracle Trace Output ******************************************************************************** UPDATE PS_PC_RATE_RUN_TAO SET RESOURCE_ID = :1 WHERE PROCESS_INSTANCE = 420 AND BUSINESS_UNIT = :2 AND PROJECT_ID = :3 AND ACTIVITY_ID = :4 AND RESOURCE_ID = :5 AND LINE_NO = :6 call count ------.22 0 509 1284 0.BL6100..Row(s) affected: 1 C o m p i l e Total SQL Statement BL6100. Inc..57 . Statement with Re-Use flag: AE Trace -. All rights reserved. 22 .---------.16.

580 total executes.BUSINESS_UNIT = 'US008' AND PZI.RUNSTATUS = 7 AND OLD. If you find any programs that are not using bind variables and are not able to modify the code. 23 . Setting the value at the session level is more appropriate. END. Session Level (using trigger): Following sample trigger code can be used to implement the session level option.SET_TRACE_INS6000 BEFORE UPDATE OF RUNSTATUS ON MYDB. This statement gets executed for every combination of BUSINESS_UNIT and INV_ITEM_ID. If you are not willing to change the application program then implementing the session level command though a trigger to give you more flexibility. All rights reserved. FROM PS_PHYSICAL_INV PI. / Note: Make sure to give ALTER SESSION privilege to MYDB to make this trigger work.. the database looks for a similar statement excluding the literal values that are passed to the SQL statement.035 unique combinations of BUSINESS_UNIT and INV_ITEM_ID and about 19. CREATE OR REPLACE TRIGGER MYDB. Example: Sql Statement issued from SQR/COBOL program: SELECT ………. Every hard parse has some amount of performance overhead. PS_STOR_LOC_INV SLI WHERE………….PRCSNAME = 'INS6000' ) BEGIN EXECUTE IMMEDIATE 'ALTER SESSION SET CURSOR_SHARING=FORCE'. As per the data composition used in this benchmark there were about 13.INV_ITEM_ID = 'PI000021' AND ………. then adding the ALTER SESSION command at the beginning of the program should be a better option. Oracle replaces the literal values with the system bind variables and treats them as single statement and parses once. © Copyright © 2006 Oracle.) ORDER BY …. NOT EXISTS (SELECT 'X' FROM PS_PICKZON_INV_VW PZI WHERE PZI. then the CURSOR_SHARING option FORCE is useful.PSPRCSRQST FOR EACH ROW WHEN ( NEW.RUNSTATUS != 7 AND NEW.7/27/2011 ------252 504 Rows ------0 252 504 --------------------------------------------------UPDATE PS_PC_RATE_RUN_TAO INDEX RANGE SCAN (object id 16735) PeopleSoft Red Paper Execution Plan --------------------------------------------------UPDATE STATEMENT GOAL: CHOOSE UPDATE OF 'PS_PC_RATE_RUN_TAO' INDEX GOAL: ANALYZED (RANGE SCAN) OF 'PS_PC_RATE_RUN_TAO' (UNIQUE) ******************************************************************************** SQR/COBOL .CURSOR_SHARING Most of the SQR and COBOL programs are written to use bind variables. Inc. With this setting.. If you identify the program (SQR/COBOL) that is not using the bind variables and need to force them to use the binds at the database level. Minimizing them will boost the performance.PRCSTYPE = 'SQR REPORT' AND NEW. Above statement uses a literal values in the where clause there by causing a hard parse for each execute.

11 1757 242929 371000 47.---------.---------. PS_STOR_LOC_INV SLI WHERE ………….69 0 0 0 44.BUSINESS_UNIT = :SYS_B_10 AND PZI. NOT EXISTS (SELECT :SYS_B_09 FROM PS_PICKZON_INV_VW PZI WHERE PZI.) ORDER BY ….47 43.---------104.---------.---------.---------rows ---------- © Copyright © 2006 Oracle..57 1 97241 0 -------.54 0 1074 0 51.85 47.---------98.---------.-----total 115894 cpu elapsed disk query current -------.---------5.---------..---------.02 2784 1439571 235104 -------.---------.35 5.22 2957 1670933 568642 rows ---------0 78376 189454 ---------267830 Misses in library cache during parse: 64 Misses in library cache during execute: 1 OVERALL TOTALS FOR ALL RECURSIVE STATEMENTS call count ------.---------197.---------.93 102.---------.27 99.---------.08 4784 1699104 606446 rows ---------0 78376 189454 ---------267830 Misses in library cache during parse: 13190 Misses in library cache during execute: 1 OVERALL TOTALS FOR ALL RECURSIVE STATEMENTS call count ------.7/27/2011 Oracle TKPROF Output with CURSOR_SHARING=FORCE PeopleSoft Red Paper SELECT ……… FROM PS_PHYSICAL_INV PI.. All rights reserved.---------.---------.22 0 5577 235 2.---------. Inc.09 50.---------.21 9. 24 .06 0 49 1 2.INV_ITEM_ID = :SYS_B_11 AND …….---------10.44 2.---------.---------.43 3027 1455101 235446 -------.02 43.---------.85 1 102867 236 rows ---------0 229 47621 ---------47850 Misses in library cache during parse: 65 Over all statistics with bind variables: OVERALL TOTALS FOR ALL NON-RECURSIVE STATEMENTS call ------Parse Execute Fetch ------total count -----26389 404647 517618 -----948654 cpu elapsed disk query current -------.---------15.---------. Over all statistics with no bind variables: OVERALL TOTALS FOR ALL NON-RECURSIVE STATEMENTS call ------Parse Execute Fetch ------total count -----26389 404647 517618 -----948654 cpu elapsed disk query current -------.-----Parse 27118 Execute 33788 Fetch 54988 ------.21 197.44 15.---------.---------. Pros and Cons of CURSOR_SHARING By setting the above parameter at the session level the over all processing time reduced significantly.42 2.-----cpu elapsed disk query current -------.51 173 231362 333538 45.

---------.01 0 1333 0 -------.00 0.08 0.55 0. Original Timing 197 Sec Time with CURSOR_SHARING option 102 Sec %Gain 48% © Copyright © 2006 Oracle.47 0. 25 .-----total 1380 0.7/27/2011 Parse 356 Execute 357 Fetch 667 ------. All rights reserved.10 0 0 0 0. Inc. it can be seen that the number of library cache misses decreased with the use of bind variables.48 0 5568 228 0.59 0 6901 228 PeopleSoft Red Paper 0 228 552 ---------780 Misses in library cache during parse: 1 From the above trace statistics.---------0.---------.---------.

As the batch process may involve extensive SQL processing.Batch Server Selection Process Scheduler executes PeopleSoft batch processes. 26 . SCENARIO 2: PROCESS SCHEDULER AND DATABASE SERVER ON ONE BOX Scenario 2 SERVER2 Database Server / BatchServer Oracle DB Use Local Connection Process Scheduler Running the Process Scheduler on the database server will eliminate the TCP/IP overhead and improve the processing time. Inc. As per the PeopleSoft architecture. Have a dedicated network connection between the batch server and the database to minimize the overhead. SCENARIO 1: PROCESS SCHEDULER AND DATABASE SERVER ON DIFFERENT BOXES Scenario 1 SERVER1 Process Scheduler Batch Server TCP/IP SERVER2 Oracle DB Database Server Running the Process Scheduler on a box other than the database server will use a TCP/IP connection to connect to the database. The impact is more evident in a process where excessive row-by-row processing is done. For the processes where majority of SQL statements are of set based.7/27/2011 PeopleSoft Red Paper Chapter 7 . © Copyright © 2006 Oracle. All rights reserved. process scheduler (Batch Server) can be setup to run from database server or any other server. the impact due to TCP/IP overhead may not be that big. this TCP/IP can be a big overhead and may impact processing times. At the same time it does use the additional server memory.

27 . All the Report jobs can be run using scenario 1. it may not be possible to run the extensive batch processes on the database server due to the limited availability of server resources. WHAT IS THE RECOMMENDED SCENARIO? Considering the performance impact due to TCP/IP for the row-by-row processing. Inc.cfg" to use the direct connection instead of TCP/IP UseLocalOracleDB=1 This kind of setup is useful for the programs that do excessive row-by-row processing. All the CRITICAL jobs can be run using scenario 2.7/27/2011 PeopleSoft Red Paper Set the following value in the process scheduler configuration file "psprcs. Make fair judgment depending on your environment and usage. the scenario 2 is recommended where the connection overhead is eliminated. You could setup both scenarios in your environment and use a specific scenario depending on the time of the run and the complexity of the process. © Copyright © 2006 Oracle. All rights reserved. At the same time.

Row Fetch (indicates that it occurred. stop tracing) after capturing the needed trace files.All other API calls except ssb .SQL statements . not data) . SQL Tracing Bitfield . The trace file will be written in the corresponding application server log directory on the machine where this application server is running.tracesql within the directory: /data2/ora/pt84803b/appserv/ORAVOL/LOGS Configuration Settings for Tracing an Online Process When setting the values for “TraceSQL” and “TracePC” within the application server’s configuration file. ----------------.------------------------------------------------------------------------.7/27/2011 PeopleSoft Red Paper Chapter 8 .us. 1 .Capturing Traces People Tools provides tracing facilities to capture online as wells as batch program flows. Sample snippet from psappsrv.SQL statement variables . These recommends are typical but specific scenarios may require additional settings to capture needed details.com.k. Note: Running a production environment with any of theses settings may cause significant performance degradation due to the overhead introduced by tracing.SQL statement variables © Copyright © 2006 Oracle. Inc. the sum of the options requested become the values in which “TraceSQL” and “TracePC” is set. ONLINE PERFORMANCE ISSUES To debug performance issues within online pages. The following minimum settings are recommended within application server’s configuration file. it is important to capture trace files for SQL and PeopleCode events. Example for tracing SQL (TraceSQL): The following options are requested to be traced: 1 2 4 8 + 16 ==== 31 . commit and rollback . Oracle DBMS also provides utilities to capture traces for details on SQL execution during a database session.SQL connect. disconnect. Make sure to reset the values back to “zero” (a. The following is basic recommendations that can assist in capturing various traces in order to identify performance issues. 2 .The value “TraceSQL” is to be set.oracle. . All rights reserved. “31” is the recommended value when tracing with “TraceSQL”. Bit Type of tracing . 28 . “1984” is teh recommended value when tracing with “TracePC”.a.SQL statements . Please refer to documentation for complete discussion.cfg . An example name for the file might be: VP1_dhcp-psft-F-2nd-west-10-138-222-59.

1 . 32 . 64 .Sybase Bind information . 256 .Sybase Fetch information . not data) .Row Fetch (indicates that it occurred.All other API calls except ssb . Dynamic change allowed for TracePC and TracePCMask TracePC=1984 TracePCMask=4095 Note: It is extremely difficult to perform on-line tracing at the database level (especially on a production environment). .Mapcore information . You can also turn on the tracing for a user session by doing the followings: Login using your PIA URL appended with “&trace=y”: For example: PIA URL: http://pbnt0020:4090/psp/ps/?cmd=login Log on using the following: http://pbnt0020:4090/psp/ps/?cmd=login&trace=y You can set your trace settings from the page below before log in: © Copyright © 2006 Oracle. contact customer support for more assistance.SQL connect.Show stack .Show fetched values . Dynamic change allowed for TraceSql and TraceSqlMask TraceSql=31 TraceSqlMask=12319 . All rights reserved. Bit Type of tracing . ----------------. a single web server session could use many different database connections. 4 .Database API specific calls .------------------------------------------------------------------------. 29 . commit and rollback .Show parameter values .7/27/2011 PeopleSoft Red Paper . 16 . 1024 . to be selected).Manager information .Trace start of programs .Trace external function calls . 128 . 8 .Trace entire program . Inc. 256 . PeopleCode Tracing Bitfield . 64 . and as database connections are used.Show assignments to variables . 4096 . 2 . 2048 .Trace each statement in program . 8192 . 512 .COBOL statement timings .Trace internal function calls . 16 .Show function return value . 4 . 8 . 128 . disconnect.Set Select Buffers (identifies the attributes of columns .List the program . . If tracing at the application server level is not adequate. This is mainly due to on-line sessions sharing of the database connections. 512 .

128 .Trace STEP execution sequence to AET file . Inc. ----------------. All rights reserved. 1 . 16 .not yet allocated . . 64 .Timings Report to AET file © Copyright © 2006 Oracle.cfg . 4 . 8 . Bit Type of tracing .AET The calculation for the “TraceAE” value is the same as for “TraceSQL” explained above.7/27/2011 PeopleSoft Red Paper APPLICATION ENGINE PERFORMANCE ISSUES Configuration Settings for Tracing an AE Process on the Application Engine When tracing is enabled for AE programs.Trace Application SQL statements to AET file . the trace directory created for “FS_BP” process might be “AE_FS_BP_7233” containing file named “AE_FS_BP_7233. “135” is the recommended value when tracing with “TraceAE”.------------------------------------------------------------------------.Trace Dedicated Temp Table Allocation to AET file . the process scheduler will create a subdirectory under “process scheduler/log/output” directory for each AE process. 32 . 2 .not yet allocated .not yet allocated . Sample snippet from psprcs. As an example.not yet allocated . 30 . AE Tracing Bitfield .

Trace external function calls . 4 . disconnect.------------------------------------------------------------------------. 256 . 4096 TraceAE= 135 PeopleSoft Red Paper Method/BuiltIn detail instead of summary in AET Timings Report not yet allocated Timings Report to tables DB optimizer trace to file DB optimizer trace to tables If tracing PeopleCode steps with an AE program is necessary. 64 . 256 . 2048 .Show function return value .COBOL statement timings . not data) .SQL Informational Trace .All other API calls except ssb . but is helpful when trying to debug procedural issues. 2 .Database API specific calls .SQL statements . 512 . Sample snippet from psprcs. 2048 . the following settings are needed within the process scheduler configuration file to capture both SQL and PeopleCode events during an execution PeopleCode tracing is not generally necessary. A raw SQL trace file generated by this setting will be created within the “UDUMP” directory on the database server. 1024 . © Copyright © 2006 Oracle. Setting value in AE trace section of process scheduler configuration file. 256 .Show assignments to variables . 1 .Show fetched values .Trace Evaluator instructions (not recommended) .Set Select Buffers (identifies the attributes of columns . . 8 . Inc.Trace internal function calls . Dynamic change allowed for TracePC TracePC=1984 Configuration Settings for Tracing an AE Process on the Database There are two ways to generate a database trace file for AE process: 1. Please remember to restore original configuration values after completing the trace. 16 .Trace start of programs . 64 . SQL Tracing Bitfield . . PeopleCode Tracing Bitfield .SQL statement variables . “1984” is the recommended value when tracing with “TracePC”. 128 .cfg . All rights reserved. Dynamic change allowed for TraceSql and TraceSqlMask TraceSQL=31 . 512 . Bit Type of tracing .Show stack . 1024 . 16 . 1 .Sybase Fetch information .Sybase Bind information . ----------------. 32 .Trace each statement in program (recommended) .7/27/2011 . 512 .SQL connect.Show parameter values . 8 .List Evaluator program (not recommended) . commit and rollback . “31” is the recommended value when tracing with “TraceSQL”. 2 . 4 .Row Fetch (indicates that it occurred. 31 . ----------------. 128 . Bit Type of tracing . 1024 . to be selected).

4 . 2.PSPRCSRQST FOR EACH ROW WHEN ( NEW. 32 . Generally Level 12 trace is useful to identify SQL performance problems and this captures wait and bind information for all SQL. If this information is needed. EXECUTE IMMEDIATE 'ALTER SESSION SET EVENTS = ''10046 TRACE NAME CONTEXT FOREVER. Bit Type of tracing . Inc.SET_TRACE_POCALC BEFORE UPDATE OF RUNSTATUS ON MYDB.DB optimizer trace to tables TraceAE=2183 Note: This setting does not provide wait events and bind variable information.DB optimizer trace to file . / Modify the trigger creation command with the proper values for database name.prcsname = 'PO_PO_CALC' ) BEGIN EXECUTE IMMEDIATE 'ALTER SESSION SET TIMED_STATISTICS = TRUE'. CREATE OR REPLACE TRIGGER MYDB. A trigger is created to start SQL tracing on the database side for an AE process with customized trace settings. AE Tracing Bitfield .Trace Application SQL statements to AET file .------------------------------------------------------------------------. . 1 . 1024 . The raw trace will be used as input to the “tkprof” database utility to generate a formatted trace report. LEVEL 12'''. All rights reserved.not yet allocated . 4096 .not yet allocated .Timings Report to tables . use the second method. 128 . and tracefile identifier. For example.prcstype = 'Application Engine' AND NEW. 8 . 16 . © Copyright © 2006 Oracle. to generate trace for an AE process PO_PO_CALC the following trigger needs to be created. process name. EXECUTE IMMEDIATE 'ALTER SESSION SET TRACEFILE_IDENTIFIER = ''POCALC'''.cfg . Sample snippet from psprcs.not yet allocated .Trace STEP execution sequence to AET file .Method/BuiltIn detail instead of summary in AET Timings Report . “2183” is the recommended value when using this method.Trace Dedicated Temp Table Allocation to AET file . 32 .Timings Report to AET file .7/27/2011 PeopleSoft Red Paper The raw trace file will contain details of each SQL statement that was executed on the database including its runtime execution plan. 2 . END. 2048 .runstatus = 7 AND OLD.not yet allocated . MYDB is the database name and SET_TRACE_POCALC is the trigger name. The calculation for the “TraceAE” value is the same as for “TraceSQL” explained above.not yet allocated . 256 . EXECUTE IMMEDIATE 'ALTER SESSION SET MAX_DUMP_FILE_SIZE = UNLIMITED'. 512 .runstatus != 7 AND NEW. 64 . ----------------.

commit and rollback .fchela.SET_TRACE_INS6000 BEFORE UPDATE OF RUNSTATUS ON MYDB. LEVEL 12'''. EXECUTE IMMEDIATE 'ALTER SESSION SET TRACEFILE_IDENTIFIER = ''INS6000'''.SQL statement variables .prcstype = 'SQR REPORT' AND NEW. COBOL PERFORMANCE ISSUES The following settings are needed within the process scheduler’s configuration file to capture summary report information for a COBOL process. 32 . END. along with database SQL trace.All other API calls except ssb .SQL statements . CREATE OR REPLACE TRIGGER MYDB.execpu. Inc. disconnect. execute the program “tkprof” with following sort options: tkprof <trace_input_file> <rpt_output_file> sys=no explain=<user_id>/<password> sort=exeela. The following is an example trigger creation command for one a SQR report.SQL connect. 4 . PeopleSoft Red Paper Once the raw database trace is captured. 128 . All rights reserved. This report. . 512 .prscpu.Row Fetch (indicates that it occurred. EXECUTE IMMEDIATE 'ALTER SESSION SET MAX_DUMP_FILE_SIZE = UNLIMITED'.runstatus = 7 AND OLD. not data) .COBOL statement timings . 8 . 33 . 16 . 1 .Sybase Bind information . 256 . 64 . 1024 .prcsname = 'INS6000' ) BEGIN EXECUTE IMMEDIATE 'ALTER SESSION SET TIMED_STATISTICS = TRUE'. . EXECUTE IMMEDIATE 'ALTER SESSION SET EVENTS = ''10046 TRACE NAME CONTEXT FOREVER. SQL Tracing Bitfield .Sybase Fetch information . Bit Type of tracing . to be selected). ----------------.SQL Informational Trace .Database API specific calls . will help to debug performance issues. Dynamic change allowed for TraceSql and TraceSqlMask TraceSQL=128 SQR REPORTS PERFORMANCE ISSUES Creating a trigger is the only way to generate SQL trace file for SQR reports.fchcpu Note: Enabling tracing at the database instance level is never recommended.Set Select Buffers (identifies the attributes of columns . 2 .runstatus != 7 AND NEW. / ORACLE PERFORMANCE ISSUES © Copyright © 2006 Oracle.PSPRCSRQST FOR EACH ROW WHEN ( NEW.7/27/2011 Note: Drop or disable the trigger once the trace is captured.

commit wait etc. This information is very useful for solving performance issues and finding the database load at any point in time in the past. AWR automatically generates snapshots of the performance data once every hour (by default) and collects the statistics in the workload repository. © Copyright © 2006 Oracle. Session history details showing top SQL taking time and resource. If the system has an average of more than 10 active concurrent sessions. 3. Network and Memory. AUTOMATIC WORKLOAD REPOSITORY (AWR) Oracle 10g provides an automatic database performance monitoring tool called AWR.ora. 2. 34 .ora or spfile. Disk.peoplesoft. Note: You can use RDA (Remote Diagnostic Agent) to collect the above informations. History of the snapshots is retained for 7 days (by default) and usually does not occupy more than 300 MB within the SYSAUX tablespace.com/psdb.1 in Oracle Metalink GENERATING EXPLAIN PLAN FOR SQL USING “SQLTEXPLAIN. replacing the manual “STATSPACK” method in earlier versions. Confirm that our required minimum patches are installed: • Generate a Patch Inventory list: a. 2.7/27/2011 PeopleSoft Red Paper The followings are needed when reporting Performance issues in Oracle database to PeopleSoft Global Support Center: 1. sqltexplain utility is very useful and recommended. Operating system metrics of CPU . Network wait. Database initialization parameter “STATISTICS_LEVEL” must be set to “TYPICAL” or “ALL” (“TYPICAL” is the default) and the parameter “TIMED_STATISTICS” must be set to “TRUE” to allow the database to populate the workload repository properly. please refer to Note:414970. Send us a copy of your init. It is highly recommended to keep this AWR running with default frequency. more room may be needed. For instructions how to run RDA. Change directory to : cd $ORACLE_HOME/Opatch c. Issue the following command: opatch lsinventory • Logon to Customer Connection to make sure that all required minimum Patches are being applied. Log on to DB server b. RDBMS & Third Party Product Patches Required for Installation” Select the Tools Release that you are on. lock wait. The details of this utility are provided in Oracle Meta Link Note 215187.nsf/0/33440EC2DE7C886788257051005AEB72?OpenDocument Search for “Required Operating System.1. Note: We also document initialization paramaters that could impact performance in here.SQL” For enhanced Explain Plan and diagnostic info for one SQL statement. Wait events such as Disk I/O wait. The various metrics collected by AWR include: 1. Use this link to do so: http://www4. Inc. All rights reserved.

Typically. With such a list one can quickly identify the main areas to focus on. The AWR report will be generated. it is less likely that investigating Wait Events will produce significant savings in response time. © Copyright © 2006 Oracle. Run the awrrpt. it is recommended to compare the time taken by the top 5 timed events and direct the tuning effort to the biggest consumers. END.Therefore. Enter value for num_days: 2 4.sql 2. this is not necessary. Enter a output report name or accept the default name: Enter value for report_name: Using the report name awrrpt_1_150_160 6.CREATE_SNAPSHOT (). In situations where CPU usage is much more significant than Wait Time. Inc. Example of manually creating a snapshot via SQL*Plus: BEGIN DBMS_WORKLOAD_REPOSITORY. Enter the beginning and ending snapshot ID for the AWR report. A list displaying the snapshot id and time the snapshot was generated will display. Enter value for report_type: html 3. If there is need to diagnose a particularly specific issue. The response time analysis consists of finding out where time is being spent in a database. / AWR report analysis: Most of the time.7/27/2011 PeopleSoft Red Paper Generating a HTML or Text AWR Report: To generate an HTML or text AWR report: 1. the database tuning activity is triggered by users complaining about response time of a transaction or a Batch job. 35 . specify whether a HTML or a text report is wanted. Enter value for begin_snap : Enter value for end_snap: 5. Specify the number of previous day’s snapshots are to be listed. The response time of a given transaction in the database always consists of the following two parts: Response Time = Service Time + Wait Time Where “Service Time” is CPU consumption by the database. a snapshot can be manually created just prior and then again just after executing a questionable program. First. All rights reserved. and “Wait time” is the sum of all the Wait events in the database.sql script from within SQL*Plus and logged in with a user having the DBA role: @$ORACLE_HOME/rdbms/admin/awrrpt. The most important part of the AWR report is the Top 5 Timed Events section.

All rights reserved.658 8. high physical Reads.65 31.. Time Model Statistics Statistic Name DB CPU sql execute elapsed time parse time elapsed hard parse elapsed time failed parse elapsed time connection management call elapsed time hard parse (sharing criteria) elapsed time PL/SQL execution elapsed time sequence load elapsed time repeated bind elapsed time DB time background elapsed time background cpu time Time (s) 114. 59% of the total DB CPU is spent in sql execute elapsed time.79 0.33 8.7/27/2011 PeopleSoft Red Paper For example: Top 5 Timed Events Event CPU time db file sequential read db file scattered read log file parallel write control file sequential read 4.2% of the processing time being spent in CPU.5 User I/O 1.284 Waits Time(s) 114 26 12 9 9 12 5 1 0 Avg Wait(ms) % Total Call Time 75.67 3.37 0.00 134.12 0.16 0. one needs to look at the Time Model Statistics section.20 59.19 92.00 From the above.336 28.67 % of DB Time 75.4 System I/O 1.40 1. 36 . the system is CPU bound with 75.02 66.883 10.07 0.. High Parse.71 2.01 0.2 13.01 0.59 0.) SQL STATISTICS: © Copyright © 2006 Oracle.3 System I/O Wait Class After a glance at the above.92 11. one will need to look at the Sql Statistics section to look for problem sql’s (such as sql that have high Gets.4 User I/O 8.02 0. To drill further into the details of the CPU consumption.05 0. Inc.54 1.

It occurred on single block read for index data or table data accessed through an index. D then we can export the table data in order by B.336 28. SQL Ordered by Parse Calls: These SQLs experienced a high number of reparsing operations. SQL Ordered by CPU Time: Includes SQL statements that consumed significant CPU time during its processing.00 0. if the table has columns A. we can access the same table data by visiting fewer index blocks (and doing fewer physical I/Os). c.74 1.547 10. rebuilding the index will compact its contents into fewer blocks. SQL Ordered by Sharable Memory: Includes SQL statements cursors which consumed a large amount of SGA shared pool memory.284 6.00 0. By creating a more selective index. B. Find the Top SQL statements with Physical Reads in SQL ordered by Reads section. If this wait event is high then tune it as followed: 1.02 1. To get the details of wait events. b. C & D and the index is on B. By rebuilding the table with its rows sorted by the particular index columns we can reduce the Clustering Factor and hence the number of table data blocks that we have to visit for each index block. and reload the table. Inc.18 0. 37 © Copyright © 2006 Oracle.D. then more table data blocks have to be visited in order to get the rows in each Index block. SQL Ordered by Gets: These SQLs performed a high number of logical reads while retrieving data. In this case. Generate the explain plan of the sql statements.00 0.883 10.00 0.16 3. If the index being used has a large Clustering Factor.839 %Time -outs 0.22 The followings are the most common wait events found in Oracle database: The most common I/O related wait events is “db file sequential read”.00 Total Wait Time (s) 26 12 9 9 8 6 Avg wait (ms) 12 5 1 0 1 1 Waits /txn 1.00 0. If Index Range scans are involved. more blocks than necessary could be being visited if the index is unselective. SQL Ordered by Reads: These SQLs performed a high number of physical disk reads while retrieving data. again we have to visit more blocks because there is less index data per block. SQL Ordered by Version Count: These SQLs have a large number of versions in shared pool for some reason. Wait Events Event db file sequential read db file scattered read log file parallel write control file sequential read db file parallel write control file parallel write Waits 4.00 1.7/27/2011 • • • • • • • PeopleSoft Red Paper SQL Ordered by Elapsed Time: Includes SQL statements that took significant execution time during processing. All rights reserved. . If indexes are fragmented. one should go to Wait Events Statistics section.658 8. a. For example.

In cases where such multiblock scans are necessary. Oracle introduces an Asynchronous Commit. This value is platform-dependent and is 1MB for most platforms. It occurs when multiblock reads from disk are performed into non-contiguous buffers in the Buffer Cache. If this wait event is high then the Top SQL statements with Physical Reads in SQL ordered by Reads section can be investigated to see if their execution plans contain Full Table or Fast Full Index scans. If there is no SQL with suboptimal execution plans and I/O is evenly spread out with similar response times from all disks then a larger Buffer Cache may help.1. Possible solutions can be: • • Reduce the number of controlfile copies to the minimum that ensures that not all copies can be lost at the same time. Shared pool. I/Os on particular datafiles may be being serviced slower due to excessive activity on their disks. “log file single write” and the redo statistics. Another popular wait event is “log file sync”. please refer to Metalink Note 336119. then one of the following may be happening: a. If systemwide waits for this wait event are significant then this either indicates numerous writes to the controlfile (too many control files copies). “log file parallel write”. the initialization parameter DB_FILE_MULTIBLOCK_READ_COUNT is now automatically tuned to use a default value when this parameter is not set explicitly. or slow performance of writes to the controlfiles. In this case. If there is no particular SQL statement with bad execution plan. To understand what is delaying the log file sync. 38 .Large pool and Java pool by setting the parameter SGA_TARGET.as well as on SESSION-LEVEL. it is possible to tune the size of multiblock I/Os issued by Oracle by setting the instance parameter DB_FILE_MULTIBLOCK_READ_COUNT to be as below: DB_BLOCK_SIZE x DB_FILE_MULTIBLOCK_READ_COUNT = max_io_size of system Starting with Oracle10g Release 2. Because the parameter is expressed in blocks. Automatic Shared Memory Management (ASMM) feature is introduced to automatically determine the size of Database buffer cache (default pool). Such reads are issued for up to the number of blocks specified by this parameter DB_FILE_MULTIBLOCK_READ_COUNT at a time. please refer to this metalink Note 257643. RAID and other technologies to automatically perform I/O load balancing for us. This default value corresponds to the maximum I/O size that can be performed efficiently. To read more about this feature. it will be set to a value that is equal to the maximum I/O size that can be performed efficiently divided by the standard block size.7/27/2011 PeopleSoft Red Paper 2. Inc. For more details about ASMM. Enable asynchronous I/O or move the controlfiles to less I/O saturated disks. looking at the File I/O Statistics section of the AWR report will help us find such hot disks and spread out the I/O by manually moving datafiles to other storage or by making use of Striping. The details of this wait is reported in Background Wait Events section.1. Another common I/O related wait event is “control file parallel write'” It occurs when Oracle is writing physical blocks to all controlfiles and is waiting for the IO/s to complete. © Copyright © 2006 Oracle. In Oracle Database 10g. 3. All rights reserved. Another common I/O related wait event is “db file scattered read”. there is a need to examine some other wait events such as “LGWR wait for redo copy”.These typically happen for Full Table Scans and for Fast Full Index scans. It is enabled with the initialization parameter COMMIT_WRITE to change the commit behaviour on SYSTEM. It occurs when a user session issues a COMMIT and is waiting for LGWR to finish flushing all redo from the log buffer to disk. Some general tuning tips for this wait event are: • • Move all the log members to high speed disks Move log members to low I/O activities disk controllers Starting with Oracle 10gR2.

In addition. systems where CPU time is dominant usually need less tuning than the ones where wait time is dominant. Inc.1 Archiver Best Practices Note 62172. A steep increase in wait times is a sign of contention and need to be addressed for good scalability. A snapshot of the database workload taken periodically throughout the day is necessary to detect such performance issues.7/27/2011 PeopleSoft Red Paper As a general rule. On the other hand. All rights reserved. Below is a list of metalink reference notes that can useful for database tuning. Note 190124.1 Understanding and Tuning Buffer Cache and DBWR Note 147468. the proportion of CPU time to WAIT time always tends to decrease as load on the system increases.1 Init.1 Checkpoint Tuning and Troubleshooting Guide Note 76713.ora Parameter "DB_FILE_DIRECT_IO_COUNT" Reference Note Note 45042.1 THE COE PERFORMANCE METHOD Note 30286.1 I/O Tuning with Different RAID Configurations Note 30712. heavy CPU usage could be caused by poor Sql access paths or badly written SQL so one should not neglect it.6 WHAT IS THE DB_FILE_MULTIBLOCK_READ_COUNT PARAMETER? Note 47324.1 8i Parameters that Influence Checkpoints Note 76374. 39 .1 Init.ora Parameter "DB_FILE_MULTIBLOCK_READ_COUNT" Reference Note Note 1037322.1 Multiple Buffer Pools © Copyright © 2006 Oracle.

truncate it here. Inc. It may require changes and modifications to suit your need. ** ** Purpose: ** To generate statistics on all non-system schema table and index objects ** that are considered by the database to be stale and/or missing. It then will generate the appropriate update statistics command for regular table and indexes while skipping PS temp tables and indexes. lts_StartTime TIMESTAMP(2). This script directly accesses: ** DBA_INDEXES ** DBMS_STATS ** All the table/index objects within all the schemas in the database. the executing user ** may need the DBA role. VARCHAR2(30). lts_FinishTime TIMESTAMP(2). 40 . VARCHAR2(30). ** Date: 16-Jan-2007 ** ** Format: SQL*Plus (10g) DBA script.7/27/2011 PeopleSoft Red Paper Appendix A – Sample script to gather statistics on tables The script is written based on the assumption that a PS temp table is defined in PSRECDEFN as having a rectype=7 and PS regular table is defined as having a rectype =0. ** ** Other rights may also be needed. BOOLEAN. VARCHAR2(2000). BEGIN /** ** Delete Old Status Info here ** ** If an external table is used to hold the log ** of the executions. NUMBER(2.0). SET SERVEROUTPUT ON SIZE UNLIMITED SET LINESIZE 1000 SET PAGESIZE 10000 /** ** Oracle USA. © Copyright © 2006 Oracle. lvc_tableowner lvc_tablename lvc_PSRecordName lint_tmp lb_IsTempTable sql_stmt VARCHAR2(30).objecttab. **/ /** ** Flush Monitoring info ** ** This forces the database to "flush" the modification data ** so that dbms_stats can tell whether the stats are stale. while not ** generating statistics for PeopleSoft "temporary" tables and indexes. ** ** Please note: ** For this script to function properly. **/ DECLARE lot_ObjectsNeedingStats dbms_stats. All rights reserved. Inc.

ownname AND index_name = lot_ObjectsNeedingStats( i ). END IF.7/27/2011 ** Documentation says this is not needed.'CTXSYS' .'SYSTEM' .table_name INTO lvc_tableowner .. All rights reserved. /** Strip "PS_" **/ /** Set the temp table trap **/ lb_IsTempTable := FALSE.FLUSH_DATABASE_MONITORING_INFO.last.objname. ELSE lvc_tableowner := lot_ObjectsNeedingStats( i ). 1. /** Object Type checking **/ /** ** Trim off the default "PS_" from the table name if it exists **/ IF SUBSTR( lvc_tablename.'SYSMAN' .ownname.'DBSNMP' ) THEN /** ** Non System object ** ** Determine whether this object is an "INDEX" or "TABLE" **/ IF lot_ObjectsNeedingStats( i ). 0 ) . /** ** Check to see if the record ** is a base temp table. 3 ) = 'PS_' THEN lvc_PSRecordName := SUBSTR( lvc_tablename.ownname NOT IN ( 'SYS' . Inc.objname.first.PSRECDEFN WHERE recname = :b1 and rectype = 7'. 4 ). 41 . Doing it just in case. NVL( lot_ObjectsNeedingStats. /** rectype = 7 denotes a PeopleSoft temp table **/ sql_stmt := 'SELECT 1 FROM ' || lvc_tableowner || '.objtype = 'INDEX' THEN SELECT table_owner .options => 'LIST AUTO' .lvc_tablename FROM dba_indexes WHERE 1 = 1 AND owner = lot_ObjectsNeedingStats( i ).objlist => lot_ObjectsNeedingStats ). FOR i IN NVL( lot_ObjectsNeedingStats. 0 ) LOOP /** ** Filter out all the system objects **/ IF lot_ObjectsNeedingStats( i ). ELSE lvc_PSRecordName := lvc_tablename. ** ** Example Table name = PS_TEMP_TAO **/ BEGIN EXECUTE IMMEDIATE sql_stmt INTO lint_tmp © Copyright © 2006 Oracle. END IF. **/ DBMS_STATS.GATHER_DATABASE_STATS ( cascade => TRUE . PeopleSoft Red Paper /** ** Find all tables and indexes that have stale stats **/ DBMS_STATS. lvc_tablename := lot_ObjectsNeedingStats( i ).

EXCEPTION WHEN NO_DATA_FOUND THEN /** ** Record was not a single digit temp instance. -. PeopleSoft Red Paper EXCEPTION WHEN NO_DATA_FOUND THEN /** ** Record was not a base temp table ** ** Check if record is a single digit temp instance ** ** Example Table name = PS_TEMP_TAO1 **/ IF SUBSTR( lvc_PSRecordName. All rights reserved. Inc. LENGTH( lvc_PSRecordName ). 1 ) BETWEEN '0' AND '9' THEN /** Remove the last digit **/ lvc_PSRecordName := SUBSTR( lvc_PSRecordName. WHEN OTHERS THEN RAISE.If we make it here. END. /** 2 digit dedicated temp table Check **/ END IF. we found a record lb_IsTempTable := TRUE.1 ).1 ). LENGTH( lvc_PSRecordName ). /** ** Do the Check **/ BEGIN EXECUTE IMMEDIATE sql_stmt INTO lint_tmp USING lvc_PSRecordName. 1 ) BETWEEN '1' AND '9' THEN /** Remove the 2nd to last digit **/ lvc_PSRecordName := SUBSTR( lvc_PSRecordName. -. we found a record lb_IsTempTable := TRUE. LENGTH( lvc_PSRecordName ) . 1.If we make it here. END. /** ** Do the Check **/ BEGIN EXECUTE IMMEDIATE sql_stmt INTO lint_tmp USING lvc_PSRecordName.If we make it here. ** ** Check if record is a double digit temp instance ** ** Example Table name = PS_TEMP_TAO26 **/ IF SUBSTR( lvc_PSRecordName. LENGTH( lvc_PSRecordName ) . EXCEPTION WHEN NO_DATA_FOUND THEN -. we found a record lb_IsTempTable := TRUE. -.We have not found a temp table! NULL. /** single digit dedicated temp table Check **/ © Copyright © 2006 Oracle. 42 . /** Check 2nd last char for digit **/ WHEN OTHERS THEN RAISE. 1.7/27/2011 USING lvc_PSRecordName.

-----.' ). ** Generate Stats **/ NULL.----------------------.partname => ''' || lot_ObjectsNeedingStats( i ).indname => ''' || lot_ObjectsNeedingStats( i ). 43 . END IF. END. END. All rights reserved. IF lot_ObjectsNeedingStats( i ).degree => DBMS_STATS.objname || ''' .objtype ) || ' ' || lot_ObjectsNeedingStats( i ). /** Checking last digit **/ WHEN OTHERS THEN IF SQLCODE = -942 THEN /** table or view does not exist **/ /** Non PeopleSoft Table/Index found. '.' || lot_ObjectsNeedingStats( i ). Inc. ** Treat as though it was not a temp table.ownname || '. dbms_output.7/27/2011 PeopleSoft Red Paper END IF.AUTO_DEGREE ).put_line( 'Generating stats on ' || LOWER( lot_ObjectsNeedingStats( i ).objname || '.ownname || ''' . /** base temp table check**/ IF lb_IsTempTable = FALSE THEN lts_StartTime := SYSTIMESTAMP. ELSE /** Unexpected error **/ RAISE.partname || ''' .AUTO_SAMPLE_SIZE .-------OWNNAME VARCHAR2 IN INDNAME VARCHAR2 IN PARTNAME VARCHAR2 IN DEFAULT ESTIMATE_PERCENT NUMBER IN DEFAULT STATTAB VARCHAR2 IN DEFAULT STATID VARCHAR2 IN DEFAULT STATOWN VARCHAR2 IN DEFAULT DEGREE NUMBER IN DEFAULT GRANULARITY VARCHAR2 IN DEFAULT NO_INVALIDATE BOOLEAN IN DEFAULT STATTYPE VARCHAR2 IN DEFAULT FORCE BOOLEAN IN DEFAULT */ EXECUTE IMMEDIATE ' BEGIN DBMS_STATS.----------------------.GATHER_INDEX_STATS( ownname => ''' || lot_ObjectsNeedingStats( i ).-------OWNNAME VARCHAR2 IN TABNAME VARCHAR2 IN PARTNAME VARCHAR2 IN DEFAULT ESTIMATE_PERCENT NUMBER IN DEFAULT BLOCK_SAMPLE BOOLEAN IN DEFAULT METHOD_OPT VARCHAR2 IN DEFAULT DEGREE NUMBER IN DEFAULT GRANULARITY VARCHAR2 IN DEFAULT CASCADE BOOLEAN IN DEFAULT STATTAB VARCHAR2 IN DEFAULT STATID VARCHAR2 IN DEFAULT STATOWN VARCHAR2 IN DEFAULT © Copyright © 2006 Oracle.-----.objtype = 'INDEX' THEN /* PROCEDURE GATHER_INDEX_STATS Argument Name Type In/Out Default? -----------------------------. ELSE /* PROCEDURE GATHER_TABLE_STATS Argument Name Type In/Out Default? -----------------------------.estimate_percent => DBMS_STATS.

END IF.ownname || ''' .ownname || '.put_line( 'NOT Generating stats on temp ' || LOWER( lot_ObjectsNeedingStats( i ). END IF. All rights reserved.AUTO_SAMPLE_SIZE .AUTO_DEGREE . Inc.objtype ) || ' ' || lot_ObjectsNeedingStats( i ).cascade => FALSE ). ** ** If so inclined.partname || ''' .tabname => ''' || lot_ObjectsNeedingStats( i ).method_opt => ''FOR ALL COLUMNS SIZE AUTO'' .partname => ''' || lot_ObjectsNeedingStats( i ). END.degree => DBMS_STATS.objname || '.' ).GATHER_TABLE_STATS( ownname => ''' || lot_ObjectsNeedingStats( i ). 44 .estimate_percent => DBMS_STATS. / © Copyright © 2006 Oracle. /** System object filter **/ END LOOP.block_sample => FALSE .objname || ''' . '. **/ ELSE dbms_output.7/27/2011 NO_INVALIDATE STATTYPE FORCE */ BOOLEAN VARCHAR2 BOOLEAN IN IN IN DEFAULT DEFAULT DEFAULT PeopleSoft Red Paper EXECUTE IMMEDIATE ' BEGIN DBMS_STATS.' || lot_ObjectsNeedingStats( i ). /** Gen Stats **/ /** ** Insert status info ** ** If so inclined ** COMMIT. /** ** Create status string here. **/ END IF. lts_FinishTime := SYSTIMESTAMP. /** Object stale stats loop **/ END.

Lessons learned from these customer experiences will be posted here. © Copyright © 2006 Oracle.7/27/2011 PeopleSoft Red Paper Appendix B – Validation and Feedback This section documents that real-world validation that this Red Paper has received. Inc. FIELD VALIDATION PeopleSoft Consulting has provided feedback and validation on this document. Additional lessons learned from field experience will be posted here. 45 . CUSTOMER VALIDATION PeopleSoft is working with PeopleSoft customers to get feedback and validation on this document. All rights reserved.

All rights reserved.References 1.com © Copyright © 2006 Oracle. Peoplesoft Installation Guide .com/oramag/ 3. http://metalink.7/27/2011 PeopleSoft Red Paper Appendix C .oracle. 46 . Inc.oracle.Oracle Tuning chapter 2. http://www.

and developer. and 12 years of Oracle database experience.7/27/2011 PeopleSoft Red Paper Appendix D – Revision History Authors Jayagopal Theranikal. Worked on SCM application tuning and benchmarks in Performance & Benchmarks group. 02/29/2007: Peoplesoft Enterpise Performance on Oracle 10g Database Jan 2007 Author: Jayagopal Theranikal Contributing Authors: Rama Tiruveedhula © Copyright © 2006 Oracle. Inc. Rama Tiruveedhula. development DBA. Principal Performance Engineer 15 years of Oracle database experience as a production DBA. 47 . Glenn Low. Worked on Fusion/Enterprise applications architecture within Performance & Benchmarks group. Application Performance Having more than 15 years of Oracle database experience and more than 6 years of Peoplesoft Application tuning experience. 2+ years experience with PeopleSoft applications tuning. Worked on SCM applications tuning within Performance & Benchmarks group. Principal Performance Engineer Lawrence Schapker. Consulting Performance Engineer 10+ years of experience with PeopleSoft applications tuning. Principal Performance Engineer Reviewers The following people reviewed this Red Paper: • • • Revision History 1. 02/01/2007: Created document. 2. All rights reserved. systems engineer. Michelle Lam. Senior Manager.

S.7200 oracle. PeopleSoft. JD Edwards. All rights reserved. including implied warranties and conditions of merchantability or fitness for a particular purpose. PeopleSoft Red Paper Worldwide Inquiries: Phone: +1. without our prior written permission. This document is not warranted to be error-free. Other names may be trademarks of their respective owners. CA 94065 U. This document may not be reproduced or transmitted in any form or by any means. electronic or mechanical. © Copyright © 2006 Oracle. 48 .650. Oracle.7000 Fax: +1.506.650. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document.A.506. This document is provided for information purposes only and the contents hereof are subject to change without notice. for any purpose. Inc. All rights reserved. nor subject to any other warranties or conditions. whether expressed orally or implied in law.7/27/2011 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores. Oracle. and Siebel are registered trademarks of Oracle Corporation and/or its affiliates.com Copyright © 2006.

Sign up to vote on this title
UsefulNot useful