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

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

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

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

we want to change the ESTIMATE_PERCENT option of LOW option to be 5% and HIGH option to be 80%.7/27/2011 PeopleSoft Red Paper Let’s assume. If you find any temporary table that was not updated during the run time. 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.5 0 F e t c h Count Time 0.17.$long DBMS_STATS.0.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. Having the update statistics at the runtime incurs some overhead. method_opt=> 'FOR ALL INDEXED COLUMNS SIZE 1'.18 . Make sure the temporary table statistics have been handled as shown above.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.S Count Time 2 0. estimate_percent=>80... check the process scheduler documentation.0.. // 2.cascade=>TRUE).GATHER_TABLE_STATS (ownname=> [DBNAME]. 4.. 5 .DMS through DataMover. it is highly not recommended to turn this feature off.cascade=>TRUE). If this feature is to be turned off. // 5. then plan to use a manual method of updating the statistics.GATHER_TABLE_STATS (ownname=> [DBNAME]. All rights reserved.2.InsBalT. Run the modified DDLORA..0... Turning off %UpdateStats Note: Due to this change affecting the entire process scheduler.0.0 Time 19.DMS delivered script: The first occurrence of the DBMS_STATS is used for the LOW option of %UpdateStats. Modify %UpdateStats to use Analyze command: If you suspect that DBMS_STATS is causing performance degradation of your AE process. 1.44.UpdStat. CREATE OR REPLACE PACKAGE PSSTATS AS © Copyright © 2006 Oracle.$long DBMS_STATS. tabname=>[TBNAME]. Inc. Edit the DDLORA.. and look for statements that used the “RECSTATS” command: -.2. estimate_percent=>5. The second one is used for the HIGH option of %UpdateStats. method_opt=> 'FOR ALL INDEXED COLUMNS SIZE 1'. you can review your AE trace.(GL_JEHDR.5 InsBalT. tabname=>[TBNAME].

EXECUTE IMMEDIATE command_text. stats_mode varchar2) IS command_text VARCHAR2(2000). / CREATE OR REPLACE PACKAGE BODY PSSTATS AS PROCEDURE ANALYZE_TABLE (tab_name IN VARCHAR2. stats_mode varchar2). else command_text := 'ANALYZE TABLE '||tab_name||' COMPUTE STATISTICS'. END PSSTATS. END ANALYZE_TABLE. END PSSTATS. 6 . All rights reserved.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. © Copyright © 2006 Oracle.7/27/2011 PeopleSoft Red Paper PROCEDURE ANALYZE_TABLE (tab_name VARCHAR2. BEGIN if stats_mode <> 'HIGH' then command_text := 'ANALYZE TABLE '||tab_name||' ESTIMATE STATISTICS'. end if. Inc.

© Copyright © 2006 Oracle. All rights reserved. 2.2) Choose SQL #4 (out of 5) for Oracle Platform. 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.3) Replace SQL#4 (out of 5) for Oracle Platform. Inc. 7 .7/27/2011 PeopleSoft Red Paper 2.

2.4) Choose SQL #5 (out of 5) for Oracle Platform.analyze_table(tab_name=>[TBNAME].5) Replace SQL#5 (out of 5) for Oracle Platform. All rights reserved. psstats.7/27/2011 psstats. PeopleSoft Red Paper 2.analyze_table(tab_name=>[TBNAME]. 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.stats_mode=>'LOW'). © Copyright © 2006 Oracle. 8 .stats_mode=>'HIGH').

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

10 . are static and only change when new statistics are generated with the “SIZE” option within the DBMS_STATS procedures. For uniformly distributed data. Column is used in the where clause but contains a bind variable instead of a literal. Note: If any other value for “METHOD_OPT” is provided (ex. Histograms. the use of BP is not recommended. 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. Inc. Candidate Columns for Histograms Within PeopleSoft Applications Histograms can affect performance and should be used only when they substantially improve query plans. But. Columns that are frequently used in WHERE clauses of queries. Have a highly skewed data distribution. “… SIZE 1” or “… SIZE REPEAT”). Note: “Bind Peeking” (BP) was designed to “fix” the last bullet point above. Columns such as PROCESS_INSTANCE. In general. Histograms are not useful for columns with the following characteristics: • • • • Column data is uniformly distributed. Column is unique. Based on column usage within runtime SQL “where clauses” and the amount of data skew within the column. Histograms are persistent objects. ORD_STATUS are likely candidates that benefit from histograms. due to additional issues BP causes. like all other optimizer statistics. 3. there are maintenance and storage costs for using them. the “SIZE AUTO” value instructs the “DBMS_STATS” procedure that only columns benefiting from histograms are to be generated. the CBO can make fairly accurate estimates about the cost of executing a particular statement without the use of histograms. the automatic creation of histograms is deactivated. 2. Literal value is provided instead of using a bind variable for the given column in the where clause. All rights reserved. So. histograms should be created on: 1. Column is not used in WHERE clauses of queries.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. Please refer to Oracle documentation for more details. 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”.

7/27/2011 PeopleSoft Red Paper Chapter 3 . 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.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. Inc. APPLICATION ENGINE PERFORMANCE WITH DEDICATED TEMPORARY TABLES © Copyright © 2006 Oracle. These are regular Oracle tables but flagged as temporary in the PeopleSoft dictionary tables. 11 . configure the initialization parameters of the database to include a seperate buffer cache for this new block size. This may lessen the contention during parallel truncates. All rights reserved. This technique minimizes potential locking issues and improves processing time. When implemented on Oracle databases. PeopleSoft designated temporary tables are built using Oracle tables. Then. If the number of programs run are more than the specified count (10 in this example). Performance Tips for Dedicated Temp Tables If issues are found with parallel truncates on dedicated tempory tables. create seperate tablespace for the these tables with a block size that is greater (if possible) than the current standard tablespace block size. Required temp tables are linked to the AE program in the program property window. And the required number of instances is also specified for each AE program. 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.

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. 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. Test case explaining temp table behavior Here is the sample scenario that explains the temp table usage. that means that the program will not be called from online. the appropriate temp table instance will be used during the runtime. Temp table settings Setup the Temp Tble Instance (online) as per the requirement. © Copyright © 2006 Oracle.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. 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. Inc. This should be equivalent to the number of concurrent streams you are planning to run. 12 . PROCESS PROCESS 4 5 If the Batch Only option is selected. All rights reserved. unless you are using EPM.

temp table instance 1 will be used. 3. To overcome the drawbacks described above. there could be a possibility of contention. the first three concurrent streams will use the instance counts 1. and 3. Drawbacks Use of base temp tables for any AE process is not recommended due to the following reasons.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.2. setup a temp table instance even if you are planning to run only one process at a time. Max API Aware value should be larger than or equal to the total of Max Concurrent value set of all the process types. As multiple streams use the same base temp table. Frequent deletes and inserts could cause fragmentation for the base temp tables. Setup required value for the process scheduler server in the max concurrent field. 1. Recommendations 1. 2. When the user tries to run the 4th. 3. Always setup an adequate number of temp table instances to achieve good performance. and 6th streams.5th. 13 . Number of concurrent executions The number of concurrent executions in this example is 6. All rights reserved. The subsequent parallel streams will use the rest of the instances in sequence. In this example. where as the number of available temp table instances are just 3. Runtime table statistics on the base temp tables are ignored. So. AE Program issues a delete for the base temp tables while it truncates the temp table instances. The final three are using the base temp tables. 2. the first three processes are using the temp table instance. 4. Inc. © Copyright © 2006 Oracle. the program will not find an available temp table instance and will use the base temp table.

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

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

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

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

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

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.column_name from dba_indexes a.7/27/2011 PeopleSoft Red Paper select a. Inc.column_expression.dba_ind_columns b where b.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.index_name='PS_GL_ACCOUNT_TBL' and a.index_type.index_name=b.com/psdb.a.column_position from dba_ind_expressions where index_name='PS_GL_ACCOUNT_TBL'. PeopleSoft had recommended to disable the functional indexes causing sql(s) that were relying on these indexes to perform in an inefficient manner. 19 . We suggested that you go to the following link http://www4.peoplesoft.b. select index_name.index_name. All rights reserved.

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

10000001.01 0 2 5 0..46.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 0..(PC_PRICING.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 ------.5 F e t c h Count 0 Time 0.---------.00 0.16. 21 .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 / -.00 0 0 0 0.0 Time 2.S Count 252 Time 0.---------.00 .6 E x e c u t e Count 252 Time 1.-----total 2 cpu elapsed disk query current -------.BL6100.---------.---------.01 0.Row(s) affected: 1 C o m p i l e Total SQL Statement BL6100.. Inc.---------.-----Parse 1 Execute 1 Fetch 0 ------.---------0. All rights reserved.---------0.00 0 0 0 -------.01 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.---------.

.0 Time 0.---------0.4 F e t c h Count 0 Time 0.---------.-----total 253 cpu elapsed disk query current -------.. All rights reserved. 22 .---------.00 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 ------.16.10000001.S Count 1 Time 0.---------..57.00 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.---------. Statement with Re-Use flag: AE Trace -.22 0 509 1284 0.22 0.-----Parse 1 Execute 252 Fetch 0 ------.(PC_PRICING.00 0 0 0 0.00 0 0 0 -------.0 E x e c u t e Count 252 Time 0..BL6100.---------.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.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 / -.Bind variables: -1) 10000751 -2) US004 -3) PRICINGA1 -4) ACTIVITYA1 -5) VUS004VA10114050 -6) 1 -.---------. Inc.57 ..---------0.Row(s) affected: 1 C o m p i l e Total SQL Statement BL6100.22 0.

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

) ORDER BY ….27 99.---------197. NOT EXISTS (SELECT :SYS_B_09 FROM PS_PICKZON_INV_VW PZI WHERE PZI.-----Parse 27118 Execute 33788 Fetch 54988 ------.21 9.---------.---------.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 ------.---------rows ---------- © Copyright © 2006 Oracle.54 0 1074 0 51.44 15.---------.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 ------.---------.93 102.06 0 49 1 2.57 1 97241 0 -------.44 2.---------.---------.---------.---------98.-----total 115894 cpu elapsed disk query current -------. 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 -------.-----cpu elapsed disk query current -------.21 197.69 0 0 0 44.BUSINESS_UNIT = :SYS_B_10 AND PZI.---------10.---------.---------.51 173 231362 333538 45.---------.---------. Inc.---------. Pros and Cons of CURSOR_SHARING By setting the above parameter at the session level the over all processing time reduced significantly.11 1757 242929 371000 47.---------.INV_ITEM_ID = :SYS_B_11 AND …….7/27/2011 Oracle TKPROF Output with CURSOR_SHARING=FORCE PeopleSoft Red Paper SELECT ……… FROM PS_PHYSICAL_INV PI.22 0 5577 235 2.---------.---------5..---------104.---------. All rights reserved. 24 .---------. PS_STOR_LOC_INV SLI WHERE ………….---------.35 5.---------.---------.---------.85 47.47 43.---------15.02 2784 1439571 235104 -------.09 50.---------...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 -------.43 3027 1455101 235446 -------.42 2.

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

As per the PeopleSoft architecture. Have a dedicated network connection between the batch server and the database to minimize the overhead. Inc. this TCP/IP can be a big overhead and may impact processing times.Batch Server Selection Process Scheduler executes PeopleSoft batch processes. the impact due to TCP/IP overhead may not be that big. 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. © Copyright © 2006 Oracle. As the batch process may involve extensive SQL processing.7/27/2011 PeopleSoft Red Paper Chapter 7 . process scheduler (Batch Server) can be setup to run from database server or any other server. 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. At the same time it does use the additional server memory. 26 . For the processes where majority of SQL statements are of set based. All rights reserved. The impact is more evident in a process where excessive row-by-row processing is done.

At the same time. WHAT IS THE RECOMMENDED SCENARIO? Considering the performance impact due to TCP/IP for the row-by-row processing. All rights reserved. © Copyright © 2006 Oracle. Inc. All the CRITICAL jobs can be run using scenario 2. 27 . Make fair judgment depending on your environment and usage. it may not be possible to run the extensive batch processes on the database server due to the limited availability of server resources. All the Report jobs can be run using scenario 1. 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.7/27/2011 PeopleSoft Red Paper Set the following value in the process scheduler configuration file "psprcs.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. the scenario 2 is recommended where the connection overhead is eliminated.

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

SQL connect. 16 . 128 . 512 . 1024 . 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. Bit Type of tracing . 16 . If tracing at the application server level is not adequate.Database API specific calls .Sybase Fetch information .Trace entire program . 4 . This is mainly due to on-line sessions sharing of the database connections. disconnect.Trace start of programs . not data) .Manager information . All rights reserved. 8 .COBOL statement timings . 8192 . and as database connections are used.------------------------------------------------------------------------.Row Fetch (indicates that it occurred. ----------------.Show function return value . a single web server session could use many different database connections. 29 .List the program .Show fetched values . to be selected). PeopleCode Tracing Bitfield . 512 . 4 .Trace internal function calls . 64 . 32 .Trace external function calls . 256 . Inc. 4096 . .Mapcore information .Sybase Bind information . 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).Show parameter values . 128 . contact customer support for more assistance.All other API calls except ssb . .Trace each statement in program . 256 .7/27/2011 PeopleSoft Red Paper . 64 .Show assignments to variables . 2048 . 1 . commit and rollback .Set Select Buffers (identifies the attributes of columns . Dynamic change allowed for TraceSql and TraceSqlMask TraceSql=31 TraceSqlMask=12319 . 8 . 2 .Show stack .

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

Sample snippet from psprcs. disconnect. 2048 . All rights reserved. 16 .Row Fetch (indicates that it occurred. 2048 . ----------------.cfg . 32 .SQL statements . 8 . . 1 .Trace each statement in program (recommended) .Show function return value . SQL Tracing Bitfield . PeopleCode Tracing Bitfield .SQL connect.Show fetched values . not data) . 64 . ----------------. Bit Type of tracing . 256 .Show assignments to variables . 512 . 4 .------------------------------------------------------------------------.Trace Evaluator instructions (not recommended) . but is helpful when trying to debug procedural issues. 1024 . 2 .Show parameter values . to be selected).All other API calls except ssb .7/27/2011 .Sybase Bind information . 64 .Show stack . 256 . A raw SQL trace file generated by this setting will be created within the “UDUMP” directory on the database server.Trace start of programs . 4 . 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.COBOL statement timings . 1 .Sybase Fetch information . “31” is the recommended value when tracing with “TraceSQL”. 512 . . 8 . Please remember to restore original configuration values after completing the trace.Trace internal function calls .SQL statement variables . 256 . 31 . © Copyright © 2006 Oracle.SQL Informational Trace . 1024 . 128 . Bit Type of tracing . Inc. 2 . commit and rollback . 1024 . Setting value in AE trace section of process scheduler configuration file.Set Select Buffers (identifies the attributes of columns .List Evaluator program (not recommended) . 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. 16 . “1984” is the recommended value when tracing with “TracePC”.Trace external function calls . 512 .Database API specific calls . 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. 128 . Dynamic change allowed for TraceSql and TraceSqlMask TraceSQL=31 .

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

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

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

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

284 Waits Time(s) 114 26 12 9 9 12 5 1 0 Avg Wait(ms) % Total Call Time 75.883 10.33 8.4 System I/O 1. 59% of the total DB CPU is spent in sql execute elapsed time.05 0.71 2.00 From the above.37 0.67 % of DB Time 75.658 8.65 31.336 28. 36 .16 0. high physical Reads. To drill further into the details of the CPU consumption.07 0.02 66. 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.00 134.01 0. one will need to look at the Sql Statistics section to look for problem sql’s (such as sql that have high Gets. the system is CPU bound with 75.20 59.67 3. High Parse.. Inc.19 92.92 11.12 0.2% of the processing time being spent in CPU.40 1.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. one needs to look at the Time Model Statistics section.5 User I/O 1..4 User I/O 8.01 0.) SQL STATISTICS: © Copyright © 2006 Oracle.59 0.3 System I/O Wait Class After a glance at the above.2 13. All rights reserved.54 1.79 0.02 0.

16 3. 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. SQL Ordered by Parse Calls: These SQLs experienced a high number of reparsing operations.00 0. more blocks than necessary could be being visited if the index is unselective. again we have to visit more blocks because there is less index data per block. b. For example.284 6. 37 © Copyright © 2006 Oracle. if the table has columns A.658 8.02 1. SQL Ordered by Version Count: These SQLs have a large number of versions in shared pool for some reason.D.547 10. Find the Top SQL statements with Physical Reads in SQL ordered by Reads section. If Index Range scans are involved. SQL Ordered by CPU Time: Includes SQL statements that consumed significant CPU time during its processing. Generate the explain plan of the sql statements.00 0.00 1.883 10. It occurred on single block read for index data or table data accessed through an index. one should go to Wait Events Statistics section. If this wait event is high then tune it as followed: 1. rebuilding the index will compact its contents into fewer blocks. Inc.336 28.839 %Time -outs 0. c. D then we can export the table data in order by B. then more table data blocks have to be visited in order to get the rows in each Index block. C & D and the index is on B.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”. a. If indexes are fragmented. SQL Ordered by Reads: These SQLs performed a high number of physical disk reads while retrieving data. and reload the table.00 0. To get the details of wait events. SQL Ordered by Gets: These SQLs performed a high number of logical reads while retrieving data.18 0.7/27/2011 • • • • • • • PeopleSoft Red Paper SQL Ordered by Elapsed Time: Includes SQL statements that took significant execution time during processing.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 the index being used has a large Clustering Factor. By creating a more selective index. In this case. B. SQL Ordered by Sharable Memory: Includes SQL statements cursors which consumed a large amount of SGA shared pool memory.74 1. All rights reserved.00 0. we can access the same table data by visiting fewer index blocks (and doing fewer physical I/Os). 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.

This value is platform-dependent and is 1MB for most platforms. © Copyright © 2006 Oracle. Shared pool. If systemwide waits for this wait event are significant then this either indicates numerous writes to the controlfile (too many control files copies). 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. Another popular wait event is “log file sync”.7/27/2011 PeopleSoft Red Paper 2. the initialization parameter DB_FILE_MULTIBLOCK_READ_COUNT is now automatically tuned to use a default value when this parameter is not set explicitly. I/Os on particular datafiles may be being serviced slower due to excessive activity on their disks. please refer to this metalink Note 257643. Inc. To read more about this feature. 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. 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.as well as on SESSION-LEVEL. In this case. 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. The details of this wait is reported in Background Wait Events section. Because the parameter is expressed in blocks.Large pool and Java pool by setting the parameter SGA_TARGET. It is enabled with the initialization parameter COMMIT_WRITE to change the commit behaviour on SYSTEM. 3. 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. If there is no particular SQL statement with bad execution plan. Oracle introduces an Asynchronous Commit. RAID and other technologies to automatically perform I/O load balancing for us. Another common I/O related wait event is “db file scattered read”. All rights reserved. In cases where such multiblock scans are necessary. For more details about ASMM. 38 . 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. 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. there is a need to examine some other wait events such as “LGWR wait for redo copy”. This default value corresponds to the maximum I/O size that can be performed efficiently. It occurs when multiblock reads from disk are performed into non-contiguous buffers in the Buffer Cache. then one of the following may be happening: a. “log file parallel write”. 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. Enable asynchronous I/O or move the controlfiles to less I/O saturated disks. Such reads are issued for up to the number of blocks specified by this parameter DB_FILE_MULTIBLOCK_READ_COUNT at a time. or slow performance of writes to the controlfiles. Automatic Shared Memory Management (ASMM) feature is introduced to automatically determine the size of Database buffer cache (default pool). To understand what is delaying the log file sync. please refer to Metalink Note 336119.These typically happen for Full Table Scans and for Fast Full Index scans.1. “log file single write” and the redo statistics. 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 Oracle Database 10g.

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

It then will generate the appropriate update statistics command for regular table and indexes while skipping PS temp tables and indexes. This script directly accesses: ** DBA_INDEXES ** DBMS_STATS ** All the table/index objects within all the schemas in the database. BOOLEAN.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. VARCHAR2(30). ** ** 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. 40 . Inc. Inc. while not ** generating statistics for PeopleSoft "temporary" tables and indexes. It may require changes and modifications to suit your need. **/ /** ** Flush Monitoring info ** ** This forces the database to "flush" the modification data ** so that dbms_stats can tell whether the stats are stale. ** Date: 16-Jan-2007 ** ** Format: SQL*Plus (10g) DBA script.objecttab. lts_StartTime TIMESTAMP(2). © Copyright © 2006 Oracle. the executing user ** may need the DBA role. VARCHAR2(2000). SET SERVEROUTPUT ON SIZE UNLIMITED SET LINESIZE 1000 SET PAGESIZE 10000 /** ** Oracle USA.0). All rights reserved. VARCHAR2(30). lvc_tableowner lvc_tablename lvc_PSRecordName lint_tmp lb_IsTempTable sql_stmt VARCHAR2(30). ** ** Other rights may also be needed. **/ DECLARE lot_ObjectsNeedingStats dbms_stats. NUMBER(2. truncate it here. BEGIN /** ** Delete Old Status Info here ** ** If an external table is used to hold the log ** of the executions. ** ** Please note: ** For this script to function properly. lts_FinishTime TIMESTAMP(2).

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

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

indname => ''' || lot_ObjectsNeedingStats( i ). ELSE /* PROCEDURE GATHER_TABLE_STATS Argument Name Type In/Out Default? -----------------------------. '.partname || ''' .partname => ''' || 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.' ).AUTO_DEGREE ). dbms_output. IF lot_ObjectsNeedingStats( i ).objtype ) || ' ' || lot_ObjectsNeedingStats( i ).-------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. END.GATHER_INDEX_STATS( ownname => ''' || lot_ObjectsNeedingStats( i ).estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE .objname || ''' .----------------------. ** Generate Stats **/ NULL. /** base temp table check**/ IF lb_IsTempTable = FALSE THEN lts_StartTime := SYSTIMESTAMP. /** Checking last digit **/ WHEN OTHERS THEN IF SQLCODE = -942 THEN /** table or view does not exist **/ /** Non PeopleSoft Table/Index found.degree => DBMS_STATS.7/27/2011 PeopleSoft Red Paper END IF.----------------------. All rights reserved. ELSE /** Unexpected error **/ RAISE. Inc. ** Treat as though it was not a temp table.' || lot_ObjectsNeedingStats( i ).ownname || '.objname || '.-----. END IF.ownname || ''' .put_line( 'Generating stats on ' || LOWER( lot_ObjectsNeedingStats( i ). 43 . END.-----.objtype = 'INDEX' THEN /* PROCEDURE GATHER_INDEX_STATS Argument Name Type In/Out Default? -----------------------------.

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

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

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

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

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

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master Your Semester with a Special Offer from Scribd & The New York Times

Cancel anytime.