Oracle Business Intelligence Applications Version 7.9.

6 Performance Recommendations
An Oracle Technical Note January 2010

1

Oracle Business Intelligence Applications Version 7.9.6 Performance Recommendations

Introduction ....................................................................................................................................................... 4 Hardware recommendations for implementing Oracle BI Applications ............................................................ 4 Storage Considerations for Oracle Business Analytics Warehouse............................................................. 5 Introduction............................................................................................................................................... 5 Shared Storage Impact Benchmarks ....................................................................................................... 5 Conclusion................................................................................................................................................ 7 Source Tier ................................................................................................................................................... 7 Oracle BI Enterprise Edition (OBIEE) / ETL Tier .......................................................................................... 7 Review of OBIEE/ETL Tier components .................................................................................................. 7 Deployment considerations for the ETL components .............................................................................. 7 Target Tier .................................................................................................................................................... 7 Oracle RDBMS ......................................................................................................................................... 7 Oracle Business Analytics Warehouse configuration ....................................................................................... 8 Database configuration parameters ............................................................................................................. 8 ETL impact on amount of generated REDO Logs ........................................................................................ 8 Oracle RDBMS System Statistics ................................................................................................................. 9 Parallel Query configuration ......................................................................................................................... 9 Oracle Business Analytics Warehouse Tablespaces ................................................................................. 10 Informatica configuration for better performance............................................................................................ 10 Informatica PowerCenter 8.6 32-bit vs. 64-bit ............................................................................................ 10 Informatica Session Logs ........................................................................................................................... 10 Informatica Lookups ................................................................................................................................... 11 Disabling Lookup Cache for very large Lookups ........................................................................................ 12 Joining Staging Tables to Lookup Tables in Informatica Lookups ............................................................. 12 Informatica Custom Relational Connections for long running mappings.................................................... 13 Informatica Session Parameters ................................................................................................................ 14 Commit Interval ...................................................................................................................................... 14 DTM Buffer Size ..................................................................................................................................... 14 Additional Concurrent Pipelines for Lookup Cache Creation ................................................................. 14 Default Buffer Block Size ....................................................................................................................... 14 Informatica Load: Bulk vs. Normal ............................................................................................................. 15 Use of NULL Ports in Informatica Mappings .............................................................................................. 15 Informatica Parallel Sessions Load on ETL tier.......................................................................................... 15 Informatica Load Balancing Implementation .............................................................................................. 16 Bitmap Indexes usage for better queries performance ................................................................................... 16 Introduction ................................................................................................................................................. 16 DAC properties for handling bitmap indexes during ETL ........................................................................... 16 Bitmap Indexes handling strategies ............................................................................................................ 18 Disabling Indexes with DISTINCT_KEYS = 1............................................................................................. 21 Monitoring and Disabling Unused Indexes ................................................................................................. 22 Handling Query Indexes during Initial ETL ................................................................................................. 24 Partitioning guidelines for Large Fact tables ................................................................................................... 25 Introduction ................................................................................................................................................. 25 Convert to partitioned tables ....................................................................................................................... 25 Identify a partitioning key and decide on a partitioning interval .............................................................. 25 Create a partitioned table in Data Warehouse ....................................................................................... 27 Configure Informatica to support partitioned tables ............................................................................... 29 Configure DAC to support partitioned tables .......................................................................................... 29

2

Unit test the changes for converted partitioned tables in DAC ............................................................... 36 Interval Partitioning ..................................................................................................................................... 37 Table Compression implementation guidelines .............................................................................................. 37 Guidelines for Oracle optimizer hints usage in ETL mappings ....................................................................... 38 Hash Joins versus Nested Loops in Oracle RDBMS.................................................................................. 38 Suggested hints for Oracle Business Intelligence Applications 7.9.6 ......................................................... 41 Using Oracle Optimizer Dynamic Sampling for big staging tables ............................................................. 44 Custom Indexes in Oracle EBS for incremental loads performance .............................................................. 45 Introduction ................................................................................................................................................. 45 Custom OBIEE indexes in EBS 11i and R12 systems ............................................................................... 45 Custom EBS indexes in EBS 11i source systems ...................................................................................... 47 Oracle EBS tables with high transactional load .......................................................................................... 48 Custom EBS indexes on CREATION_DATE in EBS 11i source systems ................................................. 49 Wide tables with over 255 columns performance ........................................................................................... 50 Introduction ................................................................................................................................................. 50 Wide tables structure optimization ............................................................................................................. 50 Oracle BI Applications HIgh Availability .......................................................................................................... 51 Introduction ................................................................................................................................................. 51 High Availability with Oracle Data Guard and Physical Standby Database ................................................ 51 Oracle BI Applications ETL Performance Benchmarks .................................................................................. 53 Oracle BI Applications 7.9.6.1, Siebel CRM 8.0 Adapter............................................................................ 53 Oracle BI Applications 7.9.6.1, Oracle EBS R12 Projects Adapter ............................................................ 54 Oracle BI Applications 7.9.6.1, Oracle EBS 11i10 Enterprise Sales Adapter ............................................. 54 Oracle BI Applications 7.9.6.1, Oracle EBS 11i10 Supply Chain Adapter .................................................. 55 Conclusion ...................................................................................................................................................... 56

3

Oracle Business Intelligence Applications Version 7.9.6 Performance Recommendations

INTRODUCTION
Oracle Business Intelligence (BI) Applications Version 7.9.6 delivers a number of adapters to various business applications on Oracle database. 7.9.6.1 version is certified with other major data warehousing platforms. Each Oracle BI Applications implementation requires very careful planning to ensure the best performance both during ETL and web queries or dashboard execution. This article discusses performance topics for Oracle BI Applications 7.9.6 and higher using Informatica PowerCenter 8.6 ETL platform. Note: The document is intended for experienced Oracle BI Administrators, DBAs and Applications implementers. It covers advanced performance tuning techniques in Informatica and Oracle RDBMS, so all recommendations must be carefully verified in a test environment before applied to a production instance. Customers are encouraged to engage Oracle Expert Services to review their configurations prior to implementing the recommendations to their BI Applications environments.

HARDWARE RECOMMENDATIONS FOR IMPLEMENTING ORACLE BI APPLICATIONS
Depending on source data volumes, Oracle BI Applications Version 7.9.6 implementations can be categorized as small, medium and large. The table below summarizes hardware recommendations for Oracle BI Applications tiers by the volume ranges. Source Data Volume SMALL: Up to 200Gb MEDIUM: 200Gb to 1Tb Target Tier # CPU cores Physical RAM Storage Space 8 16Gb Up to 400Gb 16 32Gb 400Gb - 2Tb 32* 64Gb* 2Tb and higher High performance SCSI or network attached storage. Hardware RAID controller with multiple I/O channels. LARGE: 1Tb and higher

Storage System

Local (PATA, SATA, iSCSI). Local (PATA, SATA, iSCSI), Recommended two or more preferred RAID configuration I/O controllers Oracle BI Enterprise Edition / ETL Tier

# CPU cores Physical RAM

4-8 8Gb

8 - 16 8 - 16Gb

16** 16Gb**

4

Storage Space

100Gb local

200Gb local

400Gb local

* Consider implementing Oracle RAC with multiple nodes to accommodate large numbers of concurrent users accessing web reports and dashboards. ** Consider installing two or more servers on ETL tier and implementing Informatica Load Balancing across all ETL tier servers. Important: All Oracle BI Applications tiers must be set up in the same local area network. Installation of any of these three tiers over Wide Area Network (WAN) may cause timeouts during ETL mappings execution on the ETL tier.

Storage Considerations for Oracle Business Analytics Warehouse
Introduction Oracle BI Applications ETL execution plans are optimized to maximize hardware utilization on ETL and target tiers and reduce ETL runtime. Usually a well-optimized infrastructure consumes higher CPU and memory on an ETL tier and causes rather heavy storage I/O load on a target tier during an ETL execution. The storage could easily become a major bottleneck as the result of such actions as: • • • Setting excessive parallel query processes (refer to ‘Parallel Query Configuration’ section for more details) Running multiple I/O intensive applications, such as databases, on a shared storage Choosing sub-optimal storage for running BI Applications tiers.

Oracle positions Exadata solution as fast and efficient hardware for addressing I/O bottlenecks in large volume environments. The internal benchmarks for running Oracle BI Applications on Exadata will be published soon. Shared Storage Impact Benchmarks Sharing storage among heavy I/O processes could easily degrade ETL performance and result in extended ETL runtime. The following benchmarks helped to measure the impact from sharing the same NetApp filer storage between two target databases, concurrently loading data in two parallel ETL executions. Configuration description: • • • • Linux servers #1 and #2 have the following configurations: 2 quad-core 1.8 GHz Intel Xeon CPU 32 GB RAM Shared NetApp filer volumes, volume1 and volume2, are mounted as EXT3 file systems: o o Server #1 uses volume1 Server #2 uses volume2

Execution test description: • • • Set record block size for I/O operations to 32k, the recommended db block size in a target database. Execute parallel load using eight child processes to imitate average workload during ETL run. Run the following test scenarios: o Test#1: execute parallel load above on NFS volume1 using Linux server #1; keep Linux server #2 idle. o Test#2: execute parallel load above on both NFS volume1 and volume2 using Linux servers #1 and #2.

5

Re-Read: re-read an existing file. Mixed workload: read and write a file with accesses made to random locations in the file. Stride Read.45 KB/sec 1765427.53 KB/sec 3223637. Strided Read: read a file with a strided access behavior. Random Write.92 KB/sec 1795288.05 KB/sec 3134220. Rewrite. Reverse Read: read a file backwards.49 KB/sec 1755344. Random Write: write a file with accesses made to random locations in the file.46 KB/sec 1724525. and Pwrite (buffered write operation) were impacted the most.82 KB/sec 25367. Mixed Workload and Pread (buffered read operation) were impacted the least by the concurrent load.21 KB/sec 2837808.10 KB/sec 70104. Read operations do not require specific RAID sync-up operations therefore read requests are less dependent on the number of concurrent threads.78 KB/sec 1754192. Initial Read. Record Rewrite: write and re-write the same record in a file. The test summary: Test Type "Initial write " "Rewrite " "Read " "Re-read " "Reverse Read " "Stride read " "Random read " "Mixed workload " "Random write " "Pwrite " "Pread " Total Time Test #1 46087.30 KB/sec 110 min Test #2 30039. 6 .90 KB/sec 30106.83 KB/sec 3038416.25 KB/sec 2078320.The following benchmarks describe performance measurements in KB / sec: Initial Write: write a new file.70 KB/sec 68053. while Reverse Read. Rewrite: re-write in an existing file. seek 200 Kbytes.19 KB/sec 216 min Initial Write.17 KB/sec 1783300. Read: read an existing file. Random Read: read a file with accesses made to random locations in the file. read for a length of 4 Kbytes.34 KB/sec 2578445. seek 200 Kbytes and so on.63 KB/sec 2704878.60 KB/sec 45778. for example: read at offset zero for a length of 4 Kbytes. Random Read.06 KB/sec 23794.27 KB/sec 2456869.

1.1 Data Warehouse Administration Console server 10.3. or a Windows server. Avoid sharing the same RAID controller(s) across multiple databases. Oracle BI Enterprise Edition (OBIEE) / ETL Tier Review of OBIEE/ETL Tier components The Oracle BIEE/ETL Tier is composed of the following parts: Oracle Business Intelligence Server 10. as Oracle Business Analytics Warehouse.4. Source Tier Oracle BI Applications data loads may cause additional overhead of up to fifteen percent of CPU and memory on a source tier.6 Server Data Warehouse Administration Console (DAC) client 10.Conclusion Make sure you carefully plan for storage deployment. VLM/AWE implementations would increase database address space to allow for more database buffers or a larger indirect data buffer window. running under 64-bit Operating System (OS). configuration and usage in Oracle BI Applications environment.4. Refer to Oracle Metalink for VLM / AWE implementation for your platform. If 64-bit OS is not available. Target Tier Oracle RDBMS Oracle recommends deploying Oracle Business Analytics Warehouse on Oracle RDBMS 64-bit. then consider implementing Very Large Memory (VLM) on Unix / Linux and Address Windowing Extensions (AWE) for Windows 32 bit Platforms.1. The Informatica client and DAC client can be located on an ETL Administration client machine. IBM DB2 or Microsoft SQL Server. if the target database platform is Oracle. There might be a bigger impact on the I/O subsystem. The Informatica server and DAC server cannot be installed separately on different servers. running Informatica and DAC servers. Set up periodic monitoring of your I/O system during both ETL and end user queries load for any potential bottlenecks.4 Informatica PowerCenter 8. especially during full ETL loads. Using several I/O controllers or a hardware RAID controller with multiple I/O channels on the source side would help to minimize the impact on Business Applications during ETL runs and speed up data extraction into a target data warehouse. The Informatica server and DAC server host machine should be physically located near the source data machine to improve network performance.1.3. Informatica and DAC repositories can be deployed as separate schemas in the same database.6 Client Informatica PowerCenter 8.1 Informatica BI Applications Repository (usually stored in a target database) DAC BI Applications Repository (usually stored in a target database) Deployment considerations for the ETL components • • • • • The Informatica server and DAC server should be installed on a dedicated machine for best performance.3. 7 .

1.ora template for Oracle RDBMS 11g Review an appropriate init. Oracle 10g customers should use Oracle 10. partitioned tables. Oracle 11g customers should use Oracle 11.4 or higher.ora files with recommended and required parameters located in the <ORACLEBI_HOME>\dwrep\Documentation\ directory: init9iR2. execute Initial ETL.ora . 2.init. when loading large data volumes in a data warehouse database. 10g and 11g. and other database features in both ETL and front-end queries logic. If your target database is configured to run in ARCHIVELOG mode. Oracle BI Applications include template init. 8 . it is important that Oracle BI Applications customers install the latest database releases for their Data Warehouse tiers: Oracle 9i customers should use Oracle 9.1 customers must upgrade their Oracle Business Analytics Warehouses to the latest Patchset.0.0.2.init.0.ora template for Oracle RDBMS 9i init10gR2. ETL impact on amount of generated REDO Logs Initial ETL may cause higher than usual generation of REDO logs.ora template file and follow its guidelines to configure target database parameters specific to your data warehouse tier hardware.ora – init. Below is a calculation of generated REDO amount in an internal initial ETL run: redo log file sequence: start : 641 (11 Jan 21:10) end : 1624 (12 Jan 10:03) total # of redo logs : 983 log file size : 52428800 redo generated: 983*52428800 = 51537510400 (48 GB) Data Loaded in warehouse: SQL> select sum(bytes)/1024/1024/1024 Gb from dba_segments where owner='DWH' and segment_type='TABLE'.0. Important: Oracle 10. You would have to manually resize all SGA memory components and use db_block_buffers instead of db_cache_size to specify your data cache. ORACLE BUSINESS ANALYTICS WAREHOUSE CONFIGURATION Database configuration parameters Oracle Business Intelligence Applications version 7.9. Allocate up to 10-15% of additional space to accommodate for archived REDO logs during Initial ETL. you can consider two options: 1.ora template for Oracle RDBMS 10g init11g.Note: You cannot use sga_target or db_cache_size parameters if you enable VLM / AWE by setting 'use_indirect_data_buffers = true'.ora . take a cold backup and switch the database back to ARCHIVELOG mode.7 or higher. Switch the database to NOARCHIVELOG mode. Since Oracle BI Applications extensively use bitmap indexes.8.2.2.6 are certified with Oracle RDBMS 9iR2.

interval=>N) where N is the number of minutes when statistics gathering will be stopped automatically. 9 .gather_system_stats. located in <ORACLEBI_HOME>\dwrep\Documentation for details on setting the following parameters: parallel_max_servers parallel_min_servers parallel_threads_per_cpu Important: Parallel execution is non-scalable.gather_system_stats('stop') procedure at the end of the workload window. and increasing response time when the resources are shared by many concurrent transactions. Reduce the "parallel_threads_per_cpu" and "parallel_max_servers" value if the system is overloaded. the parallel execution may cause performance problems if the values parallel_max_servers and parallel_threads_per_cpu are too high. CPU speed. The system load from parallel operations can be observed by executing the following query: SQL> select name. Run dbms_stats. Failure to gather workload statistics may result in sub-optimal execution plans for queries. when the database is not idle. excessive temporary space consumption. - Important: Execute dbms_stats. It could easily lead to increased resource contention. Optimizer takes system statistics into account. Usually half an hour is sufficient to generate the valid statistic values. when it computes the cost of query execution plans. Oracle recommends two options to gather system statistics: Run the dbms_stats. Oracle computes desired system statistics when database is under significant workload. Parallel Query configuration The Data Warehouse Administration Console (DAC) leverages the Oracle Parallel Query option for computing statistics and building indexes on target tables.gather_system_stats('start') procedure at the beginning of the workload window.Gb ---------280.ora template files.gather_system_stats('interval'. and various system throughputs. and ultimately impact BI Applications performance. Since DAC creates indexes and computes statistics on target tables in parallel on a single table and across multiple tables. Refer to the init. then the dbms_stats. creating I/O bottlenecks. value from v$sysstat where name like 'Parallel%'.49 Oracle RDBMS System Statistics Oracle has introduced workload statistics in Oracle 9i to gather important information about system such as single and multiple block read time. By default DAC creates indexes with the 'PARALLEL' clause and computes statistics with pre-calculated degree of parallelism. Oracle BI Applications customers are required to gather workload statistics on both source and target Oracle databases prior to running initial ETL.

by default DAC drops and rebuilds indexes.9. and their performance is heavily impacted by data from incremental extracts and high watermark warehousing volumes. Each session log provides the detailed information about transformations as well as summary of a mapping execution. On the contrast. Depending on your hardware configuration on the target tier you can improve its performance by rearranging your data warehouse tablespaces. and allow maximum two gigabytes for any application. so you should separate all indexes in a dedicated tablespace and. including the detailed percentage run time. Informatica 64-bit takes the advantage of more physical RAM for performing complex transformations in memory and eliminating costly disk I/O operations.6 32-bit vs. Additionally BI Applications ETL execution plans employ parallel mappings execution. thus causing rather dramatic regression in ETL performance. Oracle BI Applications ETL mappings use complex Informatica transformations such as lookups. which has improved log reports.6. DAC deploys all data warehouse entities into two tablespaces: all tables into a DATA tablespace. idle time. So. During incremental loads. if you have multiple RAID / IO Controllers.8Tb > 200Gb Note that the INDEX Tablespace may increase if you enable more query indexes in your data warehouse. etc. The following table summarizes space allocation estimates in a data warehouse by its data volume range: SMALL: Target Data Volume Up to 400Gb Temporary Tablespace DATA Tablespace INDEX Tablespace 40 – 60Gb 350Gb 50Gb MEDIUM: 400Gb to 2Tb 60 – 150Gb 350Gb – 1. Oracle Business Intelligence Applications customers are strongly encouraged to use Informatica 8. The internal benchmarks of BI Applications ETL mappings for Informatica 8. You may also consider isolating staging tables (_FS) and target fact tables (_F) on different controllers. 64-bit 32-bit OS memory can address only 2 ^ 32 bytes. INFORMATICA CONFIGURATION FOR BETTER PERFORMANCE Informatica PowerCenter 8.6 64-bit version for Medium and Large environments.6 uses Informatica PowerCenter 8.6 32-bit vs.8Tb 50 – 200Gb LARGE: 2Tb and higher 150 – 250Gb > 1. 64-bit showed at least two times better throughputs for 64-bit configuration. Informatica PowerCenter 8.Oracle Business Analytics Warehouse Tablespaces By default. move the INDEX tablespace to a separate controller. Below is an example of the execution summary from an Informatica session log: ***** RUN INFO FOR TGT LOAD ORDER GROUP [1]. Informatica Session Logs Oracle BI Applications 7. or four gigabytes of RAM. and all indexes into an INDEX tablespace.6 provides a true 64-bit performance and the ability to scale because no intermediate staging or hashing files on disk are required for processing. So 32-bit ETL tier can quickly exhaust the available memory and end up with very expensive I/O paging and swapping operations. cached in memory. CONCURRENT SET [1] ***** 10 . Such configuration would help to speed up Target Load (SIL) mappings for fact tables by balancing I/O load on multiple RAID controllers.

Total Run Time = [559.80%) for the READER Thread. Informatica computes it for a single thread in a mapping as follows: Busy Percentage = (Total Run Time – Total Idle Time) / Total Run Time If the report log shows high Busy Percentage (> 70 . and the mapping is overloaded with lookups. then you may need to review the mapping’s Reader Source Qualifier Query for any performance bottlenecks.157895 percent mplt_Get_Etl_Proc_Wid. The log above shows that most probably the mapping is well balanced between Reader and Transformation threads and it keeps Writer busy with inserts.Exp_W_CUSTOMER_LOC_USE_D_Transform: 3. Such lookup could cause significant performance overhead on ETL tier. so it may be considered a candidate for investigation. If Lookup table row count is too high. you may want to turn off Bulk Mode.453112] secs Busy Percentage = [37.Exp_Decide_Etl_Proc_Wid: 3.000000 percent mplt_SIL_CustomerLocationUseDimension.Exp_Scd2_Dates: 44.210526 percent mplt_SIL_CustomerLocationUseDimension.755389] Thread [TRANSF_1_1_1] created for [the transformation stage] of partition point [Sq_W_CUSTOMER_LOC_USE_DS] has completed.843748] secs Total Idle Time = [322. All threads statistics must be reviewed together.Thread [READER_1_1_1] created for [the read stage] of partition point [Sq_W_CUSTOMER_LOC_USE_DS] has completed. • If a Reader Source Qualifier query is not a bottleneck in a slow mapping.157895 percent Thread [WRITER_1_*_1] created for [the write stage] of partition point [W_CUSTOMER_LOC_USE_D] has completed.105263 percent Exp_W_CUSTOMER_LOC_USE_D_Update_Flg: 10.EXP_Constant_for_Lookup: 1. Normal” for more details. 11 .000000] secs Busy Percentage = [100.526316 percent Lkp_W_CUSTOMER_LOC_USE_D: 13.464472] Thread work time breakdown: Fil_W_CUSTOMER_LOC_USE_D: 2. it may not necessarily be a performance bottleneck. Depending on the processed data volumes. Total Run Time = [561.Exp_Scd2_Dates” consumes 44.171875] secs Total Idle Time = [0.052632 percent mplt_Get_Etl_Proc_Wid.684211 percent mplt_Get_Etl_Proc_Wid. then you need to review the detailed transformations execution summary and identify the most expensive transformation. • If functional logic permits.105263 percent mplt_Get_Etl_Proc_Wid.70%) for the TRANSF Thread. Total Run Time = [559.2% of all TRANSF runtime. including each lookup’s percentage runtime.000000] Busy Percentage for a single thread cannot be considered as an absolute measure of performance for a whole mapping. Refer to the section “Informatica Load: Bulk vs. consider pushing lookups with row counts less than two million into the Reader SQL as OUTER JOINS. Review the guidelines below for handling Informatica Lookups in Oracle Business Intelligence Applications mappings: • Inspect Informatica session logs for the number of lookups. If the report shows high Busy Percentage for the WRITER Thread. Informatica will cache a smaller subset in its Lookup Cache.109055] secs Busy Percentage = [42.812502] secs Total Idle Time = [348. In the example above the transformation “mplt_SIL_CustomerLocationUseDimension. consider reducing a large lookup row count by adding more constraining predicates to the lookup query WHERE clause. If the report shows high Busy Percentage (> 60 .LKP_ETL_PROC_WID: 20. • Check “Lookup table row count” and “Lookup cache row count” numbers for each Lookup Transformation.Exp_Get_Integration_Id: 2. Informatica Lookups Too many Informatica Lookups in an Informatica mapping may cause significant performance slowdown.

then consider disabling the lookup cache. Then Oracle Optimizer would choose INDEX FAST FULL SCAN to retrieve the lookup values from index blocks rather than scanning the whole table. If constraining a large lookup is not possible. W_PARTY_D. which are used in the lookup query. Consult Oracle Development prior to re-writing Oracle Business Intelligence Applications mappings.EFFECTIVE_FROM_DT as EFFECTIVE_FROM_DT.ROW_WID as ROW_WID. so they cannot be constrained or pushed down into Reader queries. Disabling Lookup Cache for very large Lookups Informatica uses Lookup cache to store the lookup data on the ETL tier in flat files (dat and idx). Such update would slow down the Reader SQL execution.Important: Some lookups could be reusable within a mapping or across multiple mappings. For example.DATASOURCE_NUM_ID as DATASOURCE_NUM_ID. the lookup data can be stored in memory and transformation processes the rows very fast. • If you identify a very large lookup with row count more than 15-20 million. Check the explain plan for the lookup query to ensure index access path. and speed up the rows processing on its Transformation thread. As a result. Joining Staging Tables to Lookup Tables in Informatica Lookups If you identify bottlenecks with lookups having very large rowcounts. the lookup cannot fit into the allocated memory and the data has to be paged in and out many times during a single session. and find the desired transformation in the Transformations folder on the Mapping tab. so it is parsed only once in the lookup source database.GEO_WID as GEO_WID. W_PARTY_D. Connect to Informatica Workflow Manager. but it might improve overall mapping’s performance. the Integration Service issues a select statement against the lookup source database to retrieve lookup values for each row from the Reader Thread. Additionally Informatica takes more time to build such large lookups. you can consider constraining them by updating the Lookup queries and joining to a staging table used in the mapping. As a result. Disabling lookup cache may work faster for very large lookups under following conditions: • • Lookup query must use index access path. • Make sure you test the changes to avoid functional regressions before implementing optimizations in your production environment. It would not store any data in its flat files on ETL tier. consider pushing it down as an OUTER JOIN into the mapping’s Reader Query. Disabling the lookup cache for heavy lookups will help to avoid excessive paging on the ETL tier. W_PARTY_D.EFFECTIVE_TO_DT as EFFECTIVE_TO_DT 12 . W_PARTY_D. the original query for Lkp_W_PARTY_D_With_Geo_Wid SELECT DISTINCT W_PARTY_D. Then uncheck Lookup Cache Enabled property and save the session. Remember that Informatica would fire the lookup query for every record from its Reader thread. such lookup transformations adversely affect the overall mapping performance. The issued lookup query uses bind variables.INTEGRATION_ID as INTEGRATION_ID. otherwise data retrieval would be very expensive on the source lookup database tier. W_PARTY_D. If Lookup data is small. • Make sure you test the modified mapping with the selected disabled lookups in a test environment and benchmark its performance prior to implementing the change in the production system. The Integration Service builds cache in memory when it processes the first row of data in the cached Lookup Transformation. open the session properties. if Lookup data is very large (typically over 20M). But. Informatica will execute the lookup query and cache much fewer rows. Consider creating an index for all columns. When the lookup cache is disabled.

W_PARTY_D.DATASOURCE_NUM_ID as DATASOURCE_NUM_ID. Click on ‘Mapping’ tab 3. W_RESPONSE_FS WHERE W_PARTY_D. Use the same values as in ‘DataWarehouse’ connection 4.EFFECTIVE_FROM_DT as EFFECTIVE_FROM_DT. Open a session in Task Developer 2. W_PARTY_D. alter session set sort_area_size = 1000000000. To speed up such ETL mappings execution. Open Informatica Workflow Manager and navigate to Connections -> Relational -> New 2. alter session set hash_area_size = 2000000000. This approach can be applied selectively to both initial and incremental mappings after thorough benchmarks. Define a new Target connection 'DataWarehouse_Manual_PGA' 3.EFFECTIVE_TO_DT as EFFECTIVE_TO_DT FROM W_PARTY_D. Click on ‘Connection Environment SQL’ and insert the following commands: Repeat the same steps to define another custom Relational connection to your Oracle Source database. W_PARTY_D.DATASOURCE_NUM_ID Such change ensured the lookup row count drop from > 22M to 180K and helped to improve the mapping performance.PARTY_ID AND W_PARTY_D. Select the defined Custom value for Source or Target connection 13 .INTEGRATION_ID=W_RESPONSE_FS. W_PARTY_D.GEO_WID as GEO_WID. you can increase only the sort_area_size as sorting operations for aggregate mappings are more memory intensive. set sort_area_size and hash_area_size to higher values. Each mapping that is a candidate to use the custom Relational connections. Informatica Custom Relational Connections for long running mappings If you plan to summarize very large volumes of data (usually over 100 million records). alter session set workarea_size_policy = manual.INTEGRATION_ID as INTEGRATION_ID.FROM W_PARTY_D Can be modified to: SELECT DISTINCT W_PARTY_D. Hash joins involving bigger tables can still perform better with smaller hash_area_size. W_PARTY_D.ROW_WID as ROW_WID. should meet the requirements below: The mapping doesn’t use heavy transformations on ETL tier The Reader query joins very large tables Its Reader query execution plan uses HASH JOINS Connect to Informatica Workflow Manager and complete the following steps for each identified mapping: 1.DATASOURCE_NUM_ID=W_RESPONSE_FS. If you have limited system memory. Select ‘Connections’ in the left pane 4. Follow the steps below to create a new Relational Connection with custom session parameters in Informatica: 1. you could speed up the large data ETL mappings by turning off automated PGA structures allocation and set SORT and HASH areas manually for the selected sessions.

DTM Buffer Size The DTM Buffer Size specifies the amount of memory the Integration Service uses for DTM buffer memory. Important: Make sure you carefully analyze long running mapping bottlenecks before turning on lookup cache build concurrency in your production environment.000 (512K). Default Buffer Block Size The buffer block size specifies the amount of buffer memory used to move a block of data from the source to the target. Commit Interval The target-based commit interval determines the commit points at which the Integration Service commits data writes in the target database. Informatica Session Parameters There are three major properties. The larger the commit interval. the better the overall mapping’s performance. Enabling concurrent lookup cache creation may result in additional overhead on a target database and longer execution time.000. Informatica uses DTM buffer memory to create the internal data structures and buffer blocks used to bring data into and out of the Integration Service. Oracle BI Applications Informatica mappings have the default setting 128. Oracle BI Applications Informatica mappings have the default setting 0. 14 .000. which are overloaded with lookups. You can consider turning on lookup cache creation concurrency when you have one or two long running mappings. Oracle BI Applications Informatica mappings have the default setting 10. as it may cause performance regressions for your sessions.5. which impact Informatica mappings performance. You can reduce lookup cache build time by enabling parallel lookup cache creation by setting the value larger than one. The recommended range for commit intervals is from 10. The internal tests showed better performance for both Initial and Incremental ETL with Default Buffer Block Size set to 512. defined in Informatica Workflow Manager for each session. SQL> commit. However too large commit interval may cause database logs to fill and result in session failure. Avoid using ‘Auto’ value for Default Buffer Block Size. You can run the following SQL to update the Buffer Block Size to 512K for all mappings in your Informatica repository: SQL> update opb_cfg_attr set attr_value='512000' where attr_value='128000' and attr_id = 5. Oracle BI Applications execution plans take advantage of parallel workflows execution. Additional Concurrent Pipelines for Lookup Cache Creation Additional Concurrent Pipelines for Lookup Cache Creation parameter defines the concurrency for lookup cache creation.000.000 up to 200. Important: Make sure you test the changes in your development repository and benchmark ETL performance before making changes to your production environment. Save the changes.

Refer to Hardware Recommendations section for more details. the internal Informatica session processing for wide mappings becomes even more complex. Ensure you have enough physical memory on your ETL tier server. It also includes NULL values into INSERT statements. Set smaller number of connections to Informatica Integration Service in DAC. Oracle slows down the mapping’s overall performance. As the table grows larger. • • • 15 . slows down because of writer thread. then you should consider changing the session load mode from Bulk to Normal in Informatica Workflow Manager. which could be eliminated. Keep in mind that too many Informatica sessions. running in parallel. To avoid such potential bottlenecks: • Consider implementing Informatica 64-bit version on your ETL tier. Use of NULL Ports in Informatica Mappings The use of connected or disconnected ports with hard-coded NULL values in Informatica mappings can be yet another reason for slower ETL mappings performance. The session CPU time grows nearly proportionally to the number of connected ports. it takes longer and longer to scan the segment for chunks of 12 contiguous blocks. Informatica Parallel Sessions Load on ETL tier Informatica mappings with complex transformations and heavy lookups typically consume larger amounts of memory during ETL execution. processed by Informatica. depending on the number of NULL ports. The internal study showed that. Try to keep the total number of ports no greater than 50 per mapping. To determine whether your mapping. Normal The Informatica writer thread may become a bottleneck in some mappings that use bulk mode to load very large volumes (>200M) into a data warehouse. open its Informatica session log. executed by WRITER thread on data warehouse tier. and its execution runtime slows down dramatically. which loads very large data in bulk mode. may overload either source or target database. such mappings may easily overload the ETL server and cause very heavy memory swapping and paging. As soon as certain threshold of ports reached. Navigate to DAC’s Setup screen -> Informatica Servers tab -> Maximum Sessions in the lower pane for both Informatica and Repository connections. As the result. and test the mapping with the updated setting. The recommended range is from 5 to 10 sessions. Even though it does bypass database block cache with SYS_DL_CURSOR hint. and compute the time to write the same set of blocks (usually 10. The database session performs two direct path writes to insert each new portion of data.Informatica Load: Bulk vs. The performance gap becomes larger when more ports are used in a mapping. the overall ETL execution would take much longer time to complete.000) at the beginning and the end of the log. The analysis of a trace file from a Writer database session shows that Informatica uses an internal Oracle hint SYS_DL_CURSOR to load data in Bulk mode. so does the row width. Review slow mappings for NULL ports or any other potentially redundant ports. such mappings performance can drop two times or even more. While processing large data volumes and executing in parallel. The internal tests demonstrated that Informatica treats equally NULL and non-NULL values and allocates critical resources for processing NULL ports. To ensure effective performance of Informatica mappings: Avoid using NULL ports in Informatica transformations. If you observe significant increase in the writer execution time at the end of the log. Every time Oracle scans for 12 contiguous blocks in a target table to perform a new write transaction.

Dropping all bitmap indexes on a large table prior to an ETL run. consider implementing Informatica Load Balancing to balance the Informatica load across multiple ETL tiers and speed up mappings execution. The internal benchmarks showed performance gains when B-Tree indexes on the foreign keys and attributes were replaced with bitmap indexes. Version 7. Create Informatica services on each Informatica node and subscribe them to the single domain BITMAP INDEXES USAGE FOR BETTER QUERIES PERFORMANCE Introduction Oracle Business Intelligence Applications Version 7. This is especially the case when there are a large number of such indexes.9. performed on one node. Register additional Informatica Server(s) in DAC. This section reviews the index processing behavior of the DAC and provides the recommendations for bitmap indexes handling during ETL runs. You can register one or more Informatica servers and the Informatica Repository Server in DAC and specify the number of workflows that can be executed in parallel. Although bitmap indexes improve star queries response time. and inserts are performed with indexes in place. To minimize the overhead from Informatica repositories maintenance. 1.9. The DAC server automatically load balances across the servers. Version 7. consider the load balancing implementation below: • • Configure a single Informatica domain and deploy a single PowerCenter Repository service in it. Prior to an initial load in a data warehouse. 10g and 11g. the quality of the existing bitmap indexes may degrade as more updates.0 introduced the use of the Bitmap Index feature of the Oracle RDBMS. In comparison with B-Tree indexes. or when there is little change expected in the number of records updated or inserted into a table during each ETL run. there are no indexes created on the tables except for the unique B-Tree indexes to preserve data integrity. making such indexes less effective unless they are rebuilt. Bitmap indexes provide significant performance improvements on data warehouse star queries.• Benchmark your ETL performance in your test environment prior to implementing the change in the production system. Refer to the section Registering Informatica Servers in the DAC Client in the publication Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users. Informatica Load Balancing Implementation To improve the performance on the ETL tier.6. 2. Any repository updates or configuration changes. Conversely.6 Configure the database connection information in Informatica Workflow Manager. Refer to the section Process of Configuring the Informatica Repository in Workflow Manager in the publication Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users. It does not run more sessions than the value specified for each of them. To implement Informatica Load Balancing in DAC perform the following steps. and then recreating them after the ETL completion may be quite expensive and time consuming. their use may cause ETL performance degradations both in Oracle 9i. must be replicated across all the participating nodes in the multiple domains configuration. Important: Deploying multiple Informatica domains and repository services on different server nodes would cause additional maintenance overhead. 16 . DAC properties for handling bitmap indexes during ETL DAC handles the same indexes differently for initial and incremental ETL runs.9. deletes.

N . The recommended default value for other platforms is Y. which will be required for faster execution of subsequent mappings.4. unless you are executing a micro ETL in which case it would be too expensive to drop and create all indexes. this parameter overrides all other index level properties. the index would not be dropped and recreated during subsequent ETL runs. applicable to all indexes. applicable to bitmap indexes only. 17 . DAC’s index handling will vary based on the combination of the several DAC properties and individual index usage settings.a Bitmap index will be dropped prior to an ETL run.indexes with Always Drop & Create (Bitmap) will be dropped during an incremental ETL N .3. N/A Always Drop Index & Create Y|N - The index property Always Drop & Create does not override Drop/Create Indices execution plan property if the latter is set to N'. For an incremental ETL run. The property Always Drop and Create is an index specific property. Y – an index will be dropped prior to an ETL run.no indexes will be dropped during an incremental ETL Y - DB2/390 customers may want to set it to N.1. N/A The index property Always Drop & Create Bitmap does not override Drop/Create Indices execution plan property if the latter is set to N'. so the value should be changed to N. the index would not be dropped and recreated during subsequent ETL runs. Important: When set to N. Initial ETL: Drop/Create Execution Y|N Indices Plan Y – all indexes irrespective of any other settings will be dropped and created N . Always Drop & Create Index Bitmap Y|N Y . truncated before a load. The property Always Drop and Create is an index specific property. DAC will create ETL indexes on a loaded table.1. If an index is inactivated in DAC.no indexes will be dropped during an initial ETL Default Value Incremental ETL: Y . The property applies to Oracle data warehouse platform only. If an index is inactivated in DAC. to handle indexes during ETL runs: Parameter Parameter Values Name Type Effect DAC will drop all indexes on a target table. N – an index will not be dropped in an incremental ETL run only. The following table summarizes the list of parameters. It is used mostly in small Execution plans.a Bitmap index will not be dropped in an incremental ETL run only.During the initial ETL run. and then recreate them after loading the table. available in DAC 10.

2. enabled in the DAC metadata repository. created and maintained as part of ETL runs. Query . DAC will re-create the dropped ETL indexes after loading the table. click on the Design button under top menu. Analyze the total time to build indexes and computing statistics during an incremental run. since the indexes will be used to speed up subsequent mappings. Reducing the number of redundant bitmap indexes is an essential step for improving initial and incremental loads. To identify all enabled BITMAP indexes on a table in DAC metadata repository: Log in into your repository through the DAC user interface. especially for dimension and lookup tables. Pre-packaged Oracle BI Applications releases include bitmap indexes.ETL | QUERY Verify And Create NonSystem Existing Indices Index Usage Index ETL . False .DAC will not run any reconciliation checks between its repository and the target database. This parameter specifies the maximum number of indexes that the DAC server will 1 create in parallel for a single table. Click Query sub-tab Enter Table name and check ‘Is Bitmap’ box in the query row and click Go. Decide whether to drop or keep bitmap indexes during incremental loads. - To identify the list of the exposed columns. and therefore. Always Drop and Create Bitmap or Always Drop & N/A Create to True. which should be permanently dropped in the target schema. select your custom container in the pull down menu and select the Indices tab in the right pane. True – The DAC server will verify that all indexes defined in the DAC repository are created in the target database. Num Parallel Physical Indexes per Data Table Source Number Bitmap Indexes handling strategies Review the following recommendations for effective bitmap indexes management in your environment. You can connect to your DAC repository and execute the following queries: 18 . included into filtering conditions in RPD repository. Connect to your target database schema and drop the disabled indexes. connect to BI Server Administration Tool and generate the list of dependencies for each column using Query Repository and Related To features.an index is required to improve subsequent ETL mappings performance. DAC drops ETL indexes on a table if it truncates the table before the load. 1. Disable redundant bitmap indexes in DAC. or you set Drop/Create Indices. and new indexes have been created in the DAC repository since the last ETL run. Rebuild the DAC execution plan. even though the indexed columns might not be used in filtering conditions in the Oracle BI Server repository.an index is required to improve web queries performance. True | False - False This parameter is useful when the current execution plan has Drop/Create Indexes set to True. To disable the identified redundant indexes in DAC and drop them in Data Warehouse: Check the Inactive checkbox against the indexes.

name tbl_name FROM w_etl_index ind . NAME ETL_RUN .START_TS) DAY TO SECOND ) || .sdtl. -.end_ts end_time .row_wid AND ind.start_ts start_time .start_ts DESC -.Indexes build time: SELECT ref_idx.type_cd = 'Create Index' AND sdtl. w_etl_obj_ref tbl_ref .end_ts . ind. START_TS) DAY TO SECOND ) || START_TS) DAY TO SECOND ) || .end_ts .index_wid = ref_idx.row_wid = '<Unique ETL ID from the first query>’.app_wid = ‘<Your custom Execution Plan Name from the second query>’ AND ind_ref.Identify your custom Execution Plan Name: SELECT DISTINCT app. sdtl. w_etl_run_sdtl sdtl . (SELECT ind_ref.soft_del_flg = 'N' AND tbl_ref.run_step_wid = stp.inactive_flg = 'N' ) ref_idx WHERE def.obj_wid .idx_name .Identify your ETL Run and put its format into the subsequent queries: select ROW_WID. sdtl.tbl_name = 'W_OPTY_D' ORDER BY sdtl. w_etl_app app .sdtl.obj_type = 'W_ETL_TABLE' AND tbl_ref.Table Stats computing time: 19 . w_etl_obj_ref ind_ref .SQL> alter session set nls_date_format='DD-MON-YYYY:HH24:MI:SS'.end_ts .obj_ref_wid = ind.etl_defn_wid AND prm.AND ref_idx.obj_wid -.row_wid AND sdtl.app_wid = app.soft_del_flg = 'N' AND ind_ref. tbl.start_ts) DAY TO SECOND) || ' days ' || EXTRACT(HOUR FROM(sdtl.sdtl.app_wid = app.obj_wid = tbl.row_wid AND run.end_ts .row_wid AND tbl_ref. w_etl_table tbl .obj_wid = ind.start_ts) DAY TO SECOND) || ' min ' || EXTRACT(SECOND FROM(sdtl.START_TS) DAY TO SECOND ) || ' ' ' ' days ' hrs ' min ' sec ' PLAN_RUN_TIME -.run_wid AND def. w_etl_defn_prm prm WHERE prm. ref_idx.start_ts) DAY TO SECOND) || ' sec' idx_bld_time FROM w_etl_defn_run def . EXTRACT(DAY FROM(sdtl. w_etl_app app WHERE ind_ref.name idx_name .sdtl.app_wid = ‘<Your custom Execution Plan Name from the second query>’ AND tbl_ref. w_etl_run_step stp .row_wid AND tbl_ref.start_ts) DAY TO SECOND) || ' hrs ' || EXTRACT(MINUTE FROM(sdtl.row_wid FROM w_etl_defn_run run .row_wid = stp.sdtl.tbl_name table_name .table_wid AND ind.etl_defn_wid = run. EXTRACT(DAY FROM (END_TS || EXTRACT(HOUR FROM (END_TS || EXTRACT(MINUTE FROM (END_TS || EXTRACT(SECOND FROM (END_TS from W_ETL_DEFN_RUN order by START_TS DESC.end_ts .row_wid ='<Unique ETL ID from the first query>’ AND sdtl. -.obj_type = 'W_ETL_INDEX' AND ind_ref.

END_TS .STEP_NAME .TYPE_CD = 'Informatica' order by SDTL.RUN_STEP_WID = STP.START_TS desc.ROW_WID ='<Unique ETL ID from the first query>’ and SDTL.SDTL. Option 2: If the incremental volumes are low.TYPE_CD = 'Analyze Table' and SDTL. 20 .START_TS) DAY TO SECOND ) ||' INFA_RUN_TIME from W_ETL_DEFN_RUN DEF .SDTL.Informatica jobs for the selected ETL run: select days ' hrs ' min ' sec' SDTL.ROW_WID=STP. Alternatively.SDTL.END_TS .NAME SESSION_NAME SDTL. and the cumulative incremental load time does not fit into your load window. Option 2 is not recommended for fact tables (%_F).ROW_WID order by SDTL.SDTL.ROW_WID=STP. leave bitmap indexes on the reported tables for the next incremental run and then compare the load times. . It may be used for large dimension tables.END_TS .WRITE_THRUPUT . you can consider two options: days ' hrs ' min ' sec' Option 1: range partition large fact tables if they show up in the report. Important: Bitmap indexes present on target tables during inserts.ROW_WID and SDTL.SDTL.START_TS) DAY TO SECOND ) ||' || EXTRACT(HOUR FROM (SDTL.START_TS) DAY TO SECOND ) ||' || EXTRACT(MINUTE FROM (SDTL. Refer to the partitioning sections for more details. updates or deletes could significantly increase the SQL DML execution time.RUN_STEP_WID = STP.START_TS) DAY TO SECOND ) ||' || EXTRACT(MINUTE FROM (SDTL.START_TS) DAY TO SECOND ) ||' TBL_STATS_TIME from W_ETL_DEFN_RUN DEF .END_TS .START_TS) DAY TO SECOND ) ||' || EXTRACT(SECOND FROM (SDTL. W_ETL_RUN_STEP STP . STP. Refer to the next chapter for the implementation.ROW_WID ='<Unique ETL ID from the first query>’ and SDTL. .SDTL. .SDTL.FAILED_ROWS SDTL. W_ETL_RUN_SDTL SDTL where DEF.START_TS) DAY TO SECOND ) ||' || EXTRACT(HOUR FROM (SDTL.END_TS .NAME TABLE_NAME . If the report shows significant amounts of time to rebuild indexes and compute statistics.RUN_WID and DEF.SDTL. -.SDTL.END_TS . . Configure DAC not to drop selected bitmap indexes during incremental loads. You should measure the cumulative time to run a specific task plus the time to rebuild indexes and compute required database statistics before deciding whether to drop or keep bitmap indexes in place during incremental loads.END_TS .SUCESS_ROWS STP. it would take more time to rebuild the dropped bitmap indexes and compute required statistics.START_TS desc. W_ETL_RUN_SDTL SDTL .TABLE_WID = TBL. EXTRACT(DAY FROM (SDTL. which cannot be partitioned effectively by range.SDTL.ROW_WID and SDTL. The same SQL would complete much faster if the indexes get dropped prior to the query execution.END_TS . W_ETL_TABLE TBL where DEF.READ_THRUPUT SDTL.END_TS .select TBL. W_ETL_RUN_STEP STP .RUN_WID and DEF.START_TS) DAY TO SECOND ) ||' || EXTRACT(SECOND FROM (SDTL. 3.END_TS . EXTRACT(DAY FROM (SDTL.

Check both the check boxes Always Drop & Create and Inactive against the indexes. If you choose to keep some bitmap indexes in place during incremental runs. during an incremental run. Since the Inactive property is used both for true inactive indexes and "hidden from incremental load" indexes. The following script helps to identify all such indexes. with over 20 million records. click on the Design button under the top menu. "&&DAC_OWNER".5 – 1 percent of total records. Depending on end user data and its distribution there may be some indexes on columns with just one distinct value. insert. When an update. consider creating the indexes with the storage parameter PCTFREE value to at least 50 or higher. that will have a large volume of data updates and inserts. All bitmap indexes should be dropped for transaction fact tables. ACCEPT APP_ID PROMPT 'Enter your DAC container from the list above: ' UPDATE "&&DAC_OWNER". consider dropping and recreating the bitmap indexes since the time to rebuild would be short. Since the DAC system property Drop and Create Bitmap Indexes Always overrides the index property Always Drop & Create.w_etl_index SET inactive_flg = 'Y' WHERE row_wid IN ( SELECT ind_ref. since the script requires access to two database schemes: ACCEPT DAC_OWNER PROMPT 'Enter DAC Repository schema name: ' ACCEPT DWH_OWNER PROMPT 'Enter Data Warehouse schema name: ' SELECT row_wid FROM "&&DAC_OWNER". disable them in DAC repository and drop in database. To workaround this limitation: • • • Log in into your repository through DAC user interface. otherwise DAC will not create them after the initial load completion. Oracle RDBMS packs bitmap indexes in a data block much more tightly compared to B*Tree indexes. the bitmap indexes quality will degrade. For large tables with a small number of bitmap indexes.w_etl_index ind. so they can be safely dropped in your Data Warehouse schema and disabled in DAC repository. 4.If your benchmarks show that it is less time consuming to leave bitmap indexes in place on large dimension tables during incremental loads and the incremental volumes are relatively small.obj_wid FROM "&&DAC_OWNER". For large tables with few data updates. the system property defines how DAC will handle all bitmap indexes for all containers in the data warehouse schema. 21 . Important: You must uncheck the Inactive checkbox for these indexes before the next initial load. or delete occurs on table columns with enabled indexes. such as over 0.w_etl_app. Such indexes will not be used in any queries. Click on the Query sub-tab and get the list of all indexes defined on the target table. The higher value of PCTFREE will mitigate the impact to some degree. Additional considerations for handling bitmap indexes during incremental loads. You have to either connect as DBA user or implement additional grants. which should not be dropped during incremental runs. the indexes can be enabled during incremental runs without significant performance degradations. then you can consider keeping the selected indexes in place during incremental loads. - - Disabling Indexes with DISTINCT_KEYS = 1 Oracle BI Applications delivers a number of indexes to optimize both ETL and end user queries performance.w_etl_obj_ref ind_ref. and select the Indices tab in the right pane. the property Always Drop & Create could be used for convenience to distinguish between two different categories.

table_wid AND ind. "&&DAC_OWNER". not used by any end user queries. Create a table in your data warehouse schema to load data from v$object_usage view: CREATE TABLE myobj_usage AS SELECT * FROM v$object_usage. "&&DAC_OWNER".w_etl_obj_ref tbl_ref. spool off. Such indexes can be identified by monitoring index usage in your warehouse over extended period of time (usually 3-4 months).sql Monitoring and Disabling Unused Indexes In addition to indexes with distinct_keys=1 there could be more redundant query indexes in your data warehouse.sql INSERT INTO myobj_usage SELECT * FROM v$object_usage.table_name = tbl.name AND all_ind. 2.soft_del_flg = 'N' AND ind_ref.obj_type = 'W_ETL_INDEX' AND ind_ref. all_indexes all_ind ind_ref. To implement index usage monitoring: 1.@drop_dist_indexes.owner = '&&DWH_OWNER').WHERE -COMMIT. Create the following scripts on DAC tier in the directory <dac_home>/bifoundation/dac/scripts pre_sql.index_name = ind. pre_etl.Execute the spooled SQL file to drop the identified indexes: -. These indexes could impact incremental ETL runtime Informatica mappings performance.bat <ORACLE_HOME>/bin/sqlplus <dwh_user>/<dwh_pwd>@<dwh_db> @<dac_home>/bifoundation/dac/scripts/pre_sql.obj_wid = tbl.row_wid AND ind.sql 3.obj_ref_wid = ind.soft_del_flg = 'N' AND tbl_ref. Set "Script before every ETL" System parameter in DAC to pre_etl.name AND all_ind.row_wid AND tbl_ref.xml 22 .Drop the indexes in the schema: spool drop_dist_indexes.num_rows >= 1 AND ind.app_wid = '&&APP_ID' AND ind_ref.app_wid = '&&APP_ID' AND tbl_ref. 4.' FROM all_indexes WHERE distinct_keys =1 and owner='&&DWH_OWNER'. COMMIT: EXIT.row_wid AND tbl_ref.inactive_flg = 'N' AND all_ind. -.obj_type = 'W_ETL_TABLE' AND tbl_ref.type_cd = 'Query' AND all_ind.obj_wid = ind. "&&DAC_OWNER". Create a backup copy of <dac_home>/bifoundation/dac/CustomSQLs/CustomSQL.distinct_keys = 1 AND all_ind.bat.sql SELECT 'DROP INDEX ' || owner|| '.' || index_name || ' . -.w_etl_app app.w_etl_table tbl.app_wid = app.

BEGIN FOR rec IN c1 LOOP EXECUTE IMMEDIATE 'alter index '||rec. If you implement index monitoring for the first time after completing ETLs. 23 .5. execute immediate 'ALTER INDEx %2 MONITORING USAGE'. execute immediate 'ALTER INDEX %2 MONITORING USAGE'. END LOOP. </SqlQuery> <SqlQuery name = "ETL_ORACLE_CREATE_INDEX"> BEGIN execute immediate 'CREATE %1 INDEX %2 ON %3 ( %4 ) NOLOGGING'. execute immediate 'ALTER INDEX %2 MONITORING USAGE'.xml and replace <SqlQuery name = "ORACLE_CREATE_INDEX">. Open CustomSQL. END. END. END. / To query the unused indexes in your data warehouse execute the following SQL: SELECT DISTINCT index_name FROM myobj_usage WHERE used = 'NO'. </SqlQuery> 6. <SqlQuery name = "ETL_ORACLE_CREATE_INDEX"> and <SqlQuery name = "QUERY_ORACLE_CREATE_INDEX"> sections with: <SqlQuery name = "ORACLE_CREATE_INDEX"> BEGIN execute immediate 'CREATE %1 INDEX %2 ON %3 ( %4 ) NOLOGGING'. </SqlQuery> <SqlQuery name = "QUERY_ORACLE_CREATE_INDEX"> BEGIN execute immediate 'CREATE %1 INDEX %2 ON %3 ( %4 ) NOLOGGING PARALLEL'. END.index_name||' monitoring usage'. execute the following PL/SQL block to enable monitoring for all indexes: DECLARE CURSOR c1 IS SELECT index_name FROM user_indexes WHERE index_name NOT IN (SELECT index_name FROM v$object_usage WHERE MONITORING = 'YES').

Restore <dac_home>/bifoundation/dac/CustomSQLs/CustomSQL.row_wid AND tbl_ref.soft_del_flg = 'N' AND tbl_ref.app_wid = :APP_ID AND tbl_ref. Execute the following PL/SQL block to disable index monitoring: DECLARE CURSOR c1 IS SELECT index_name FROM user_indexes WHERE index_name IN (SELECT index_name FROM v$object_usage WHERE MONITORING = 'YES').obj_wid = ind. Important!!! Make sure you monitor the index usage for the extended period of at least 1-2 months before deciding which additional indexes could be disabled in DAC and dropped in your target schema.row_wid st nd 24 . Disable query indexes -> run an incremental ETL -> enable query indexes -> run another incremental ETL -> run OBIEE reports To summarize. which are not used during ETL but required for OBIEE queries better performance. Disable query indexes -> run an initial ETL -> enable query indexes -> run an incremental ETL -> run OBIEE reports 2. This article discusses several options how to reduce index maintenance such as disabling unused query indexes. w_etl_obj_ref ind_ref. You st nd cannot use this option for 1 ETL –> OBIEE –> 2 ETL sequence. then you need to have query indexes.NAME idx_name. created on the target tables prior to implementing partitioning.xml from its backup copy.app_wid = :APP_ID AND ind_ref. Handling Query Indexes during Initial ETL Oracle BI Applications delivers a number of query indexes.obj_wid. BEGIN FOR rec IN c1 LOOP EXECUTE IMMEDIATE 'alter index '||rec.obj_type = 'W_ETL_INDEX' AND ind_ref.NAME tbl_name FROM w_etl_index ind. tbl.After identifying redundant indexes.soft_del_flg = 'N' AND ind_ref. w_etl_table tbl. you can disable query indexes only for the following pattern: 1 ETL –> 2 ETL –> OBIEE. Important: If you plan to implement partitioning for your warehouse tables and you want to take advantage of conversion scripts in the next section.index_name||' nomonitoring usage'. ind. END.obj_type = 'W_ETL_TABLE' AND tbl_ref. follow the steps below to turn off index monitoring: 1. or partitioning large fact tables and maintain local query indexes on the latest range partitions. END LOOP. 2. Creation of such large number of query indexes can extend both initial and incremental ETL windows. • Identify and preserve all activated query indexes PRIOR to executing the first ETL run: CREATE TABLE psr_initial_query_idx AS SELECT ind_ref. w_etl_app app WHERE ind_ref. Reset "Script before every ETL" System parameter in DAC 3. Most of query indexes are created as BITMAP indexes in Oracle database. You can consider disabling ALL query indexes and reduce your ETL runtime in the following scenarios: 1. disabling them in DAC and dropping in your data warehouse.obj_wid = tbl. w_etl_obj_ref tbl_ref.

• • Execute your first ETL run. Online reports and dashboards should also render results faster.app_wid = app. SQL> commit. • Disable the identified query indexes PRIOR to starting the first ETL run: SQL> UPDATE w_etl_index SET inactive_flg = 'Y' WHERE row_wid IN (SELECT obj_wid FROM psr_initial_query_idx).row_wid ind. Please note that there are some steps. Convert to partitioned tables Perform the following steps to convert a regular table into an range partitioned table. To implement the support for partitioned tables in Oracle Business Analytics Data Warehouse.table_wid ind. but also improve web queries performance.isunique = 'N' ind. with more than 20 million rows.AND AND AND AND AND AND tbl_ref.DRP_CRT_ALWAYS_FLG = 'Y' OR ind. Large fact tables. To build an optimal partitioned table with reasonable data distribution. or convert the populated tables into partitioned objects after the full load. you need to update DAC metadata and manually convert the candidates into partitioned tables in the target database.type_cd = 'Query' (ind.DRP_CRT_BITMAP_FLG = 'Y') Where APP_ID can be identified from: SELECT row_wid FROM w_etl_app. You can either identify and partition target fact tables before initial run. Review the following guidelines for selecting a column for a partitioning key: 25 . quarter. are good candidates for partitioning. Follow the steps below to implement fact table partitioning in your data warehouse schema and DAC repository. which apply for composite range-range partitioning only. Since the majority of inserts and updates impact the last partition(s). Identify a partitioning key and decide on a partitioning interval Choosing the correct partitioning key is the most important factor for effective partitioning. SQL> commit.inactive_flg = 'N' ind. and then rebuild disabled indexes after the load and compute statistics on updated partitions only. since the optimizer would build more efficient execution plans using partitions elimination logic. etc. PARTITIONING GUIDELINES FOR LARGE FACT TABLES Introduction Taking advantage of range and composite range-range partitioning for fact tables will not only reduce index and statistics maintenance time during ETL. year. you would need to disable only local indexes on a few impacted partitions. you can consider partitioning by month.obj_ref_wid = ind. since it defines how many partitions will be involved in web queries or ETL updates. • Execute your second ETL run. DAC will recreate all disabled query indexes. Enable all preserved indexes PRIOR to starting the second ETL run: SQL> UPDATE w_etl_index SET inactive_flg = 'N' WHERE row_wid IN (SELECT obj_wid FROM psr_initial_query_idx).

The recommended partitioning range for most implementations is a month. Connect to the Oracle BI Server repository and check the usage or dependencies on each column in the logical and presentation layers. month. define index and table actions for PREVIOUS and CURRENT partitions Quarterly range: you may consider maintaining just one.• • • • • Identify eligible columns of type DATE for implementing range partitioning. CURRENT partition. Yearly range: you are recommended to maintain only one.e. quarter or year. Analyze the summarized data distribution in the target table by each potential partitioning key candidate and data volumes per time range. The proposed partitioning guidelines assume that the majority of incremental ETL volume data (~90%) is new records. i. - The following table summarizes the recommended partitioning keys for some large Oracle BI Applications Fact tables: Area Financials Financials Financials Financials Financials Financials Sales Sales Sales Sales Siebel Sales Table Name W_AP_XACT_F W_AR_XACT_F W_GL_REVN_F W_GL_COGS_F W_TAX_XACT_F W_GL_OTHER_F W_SALES_ORDER_LINE_F W_SALES_PICK_LINE_F W_SALES_INVOICE_LINE_F W_SALES_SCHEDULE_LINE_F W_REVN_F Partitioning Key POSTED_ON_DT_WID POSTED_ON_DT_WID POSTED_ON_DT_WID POSTED_ON_DT_WID POSTED_ON_DT_WID ACCT_PERIOD_END_DT_WID ORDERED_ON_DT_WID PICKED_ON_DT_WID INVOICED_ON_DT_WID ORDERED_ON_DT_WID CLOSE_DT_WID Consider implementing composite range-to-range partitioning for Projects large fact tables using the following partitioning and sub-partitioning keys: Area Projects Table Name W_PROJ_EXP_LINE_F Partitioning Key CHANGED_ON_DT Sub-partitioning Key EXPENDITURE_DT_WID 26 . Basing on the compiled data. you may consider rebuilding local indexes for the most impacted latest partitions: Monthly range: you are advised to maintain two latest partitions. though you can consider a quarter or a year for your partitioning ranges. CURRENT partition. which end up in the one or two latest partitions. decide on the appropriate partitioning key and partitioning range for your future partitioned table. Depending on the chosen range granularity.

2. If you have already completed the initial load into a regular table and then decided to partition it. Create the partitioned table. subpartition PART_MIN_1999 values less than (20010000) . using range partitioning by year: SQL> create table W_WRKFC_EVT_MONTH_F partition by range (EVENT_YEAR)( partition PART_MIN values less than (2006). partition PART_2008 values less than (2009). The second option would be preferred in high availability data warehouses when you have to carry out partitioning with end users accessing the data.range-partitioning W_PROJ_EXP_LINE_F . or (b) create table exchange partition syntax and then split partitions. The internal tests showed that the first option. or load data into the regular table and then create its partitioned copy and migrate the summarized data. The example below uses the following tables for converting into partitioned objects: • • W_WRKFC_EVT_MONTH_F . subpartition PART_MIN_2002 values less than (20030000) . partition PART_2009 values less than (2010). partition PART_MAX values less than (maxvalue) ) tablespace BIAPPS_DATA nologging parallel enable row movement as select * from W_WRKFC_EVT_MONTH_F_ORIG. subpartition PART_MIN_2003 values less than (20040000) . EVENT_YEAR column in the example above uses number(4) precision. you DO NOT need to re-run the initial load. use the following sample syntax: SQL> create table W_PROJ_EXP_LINE_F partition by range (CHANGED_ON_DT) subpartition by range (EXPENDITURE_DT_WID) (partition PART_MIN values less then (TO_DATE('01-JAN-2008'. subpartition PART_MIN_2005 values less than (20060000) . subpartition PART_MIN_1998 values less than (19990000) . If you implement composite range-range partitioning. partition PART_2010 values less than (2011). then you have to define your partition ranges using format YYYYMMDD. 1.'DD-MON-YYYY')) ( subpartition PART_MIN_MIN values less than (19980000) .composite range-range partitioning. is simpler and faster. partition PART_2006 values less than (2007). create table as select. Rename the original table SQL> rename W_WRKFC_EVT_MONTH_F to W_WRKFC_EVT_MONTH_F_ORIG. subpartition PART_MIN_2007 values less than (20080000) 27 . subpartition PART_MIN_2004 values less than (20050000) . subpartition PART_MIN_2006 values less than (20070000) . subpartition PART_MIN_2001 values less than (20020000) .Projects Projects W_PROJ_COST_LINE_F W_PROJ_REVENUE_LINE_F CHANGED_ON_DT CHANGED_ON_DT PROJ_ACCOUNTING_DT_WID GL_ACCOUNTING_DT_WID Create a partitioned table in Data Warehouse You can pre-create a partitioned table prior to the initial load. so the table partition values are defined using format YYYY. partition PART_2007 values less than (2008). If you choose WID column for a partitioning key. You can consider two options to convert a table into a partitioned one: (a) create table as select.

' FROM USER_INDEXES WHERE TABLE_NAME = 'W_WRKFC_EVT_MONTH_F_ORIG'. subpartition PART_MAX_2008 values less than (20090000) . subpartition PART_200801_2005 values less than (20060000) . subpartition PART_MAX_2005 values less than (20060000) . subpartition PART_200801_1999 values less than (20010000) . subpartition PART_MIN_2009 values less than (20100000) . subpartition PART_MAX_2004 values less than (20050000) .. subpartition PART_200801_2008 values less than (20090000) . subpartition PART_MAX_2006 values less than (20070000) . subpartition PART_MAX_2002 values less than (20030000) . Drop / Rename indexes on renamed table To drop indexes on the renamed table: SQL> spool drop_ind. subpartition PART_200801_2009 values less than (20100000) . Make sure you check partitioning column data type prior to partitioning a table. subpartition PART_MAX_2001 values less than (20020000) . subpartition PART_MAX_1999 values less than (20010000) . subpartition PART_200801_1998 values less than (19990000) . Important: You must use the exact format YYYY. subpartition PART_MAX_1998 values less than (19990000) . so the table partition values are defined using format YYYYMMDD.'DD-MON-YYYY')) ( subpartition PART_200801_MIN values less than (19980000) . partition PART_200801 values less than (TO_DATE('01-APR-2008'. then use the following commands: SQL> spool rename_ind.sql SQL> SELECT 'DROP INDEX '|| INDEX_NAME||'.sql If you want to keep indexes on the original renamed table until successful partitioning conversion completion... subpartition PART_MAX_2003 values less than (20040000) . ‘ FROM USER_INDEXES WHERE TABLE_NAME = ‘W_WRKFC_EVT_MONTH_F_ORIG’. partition PART_MAX values less than (maxvalue) ( subpartition PART_MAX_MIN values less than (19980000) . subpartition PART_200801_2004 values less than (20050000) . subpartition PART_MAX_2009 values less than (20100000) . subpartition PART_200801_2006 values less than (20070000) . The composite range-range example uses Quarter for partitioning and Year for sub-partitioning ranges. subpartition PART_MIN_MAX values less than (maxvalue) ) .sql SQL> SELECT ‘ALTER INDEX ‘|| INDEX_NAME ||’ rename to ‘|| INDEX_NAME || ‘_ORIG. subpartition PART_200801_2003 values less than (20040000) . subpartition PART_200801_MAX values less than (MAXVALUE) ) . subpartition PART_MAX_2007 values less than (20080000) . subpartition PART_200801_2002 values less than (20030000) . 3. SQL> spool off SQL> @rename_ind. subpartition PART_MAX_MAX values less than (maxvalue) ) ) nologging parallel enable row movement as (select * from W_PROJ_EXP_LINE_F_ORIG). subpartition PART_200801_2007 values less than (20080000) . SQL> spool off SQL> @drop_ind. subpartition PART_200801_2001 values less than (20020000) .. . Quarter or Month correspondingly. . subpartition PART_MIN_2008 values less than (20090000) .sql 28 . EXPENDITURE_DT_WID column has number(8) precision.. YYYYQQ or YYYYMMDD for partitioning by Year.

' . then update modify "MAX(DECODE(POSTN. END.sql SQL> SELECT 'CREATE ' ||DECODE(ISUNIQUE. Create Global and Local indexes.ISBITMAP.'Y'.' . Compute Statistics on Partitioned Table SQL> BEGIN dbms_stats..' FROM W_ETL_TABLE T.NAME||' ASC')) ||MAX(DECODE(POSTN.2.))" sentence. tabname => 'W_WRKFC_EVT_MONTH_F'. Configure DAC to support partitioned tables Create new source system parameters 29 .'Y'.NAME ||CHR(10) ||' ON ' ||T.NAME||' ASC')) ||MAX(DECODE(POSTN.INACTIVE_FLG = 'N' GROUP BY T.'||C.'||C.'||C.' .INDEX_WID AND I. Open Workflow Manager -> Connections -> Relational -> edit DataWarehouse -> Update Connection Environment SQL: ALTER SESSION SET SKIP_UNUSABLE_INDEXES=TRUE.NAME||' ASC')) ||') tablespace USERS_IDX ' ||CHR(10) ||DECODE(ISUNIQUE.sql 4. The script creates indexes with maximum seven positions. Configure Informatica to support partitioned tables Enable Row Movement Set skip_unusable_indexes = TRUE in DataWarehouse Relational Connection in Informatica Workflow Manager.ROW_WID = C.'BITMAP ') ||'INDEX ' ||I.ROW_WID = I.NAME||' ASC')) ||MAX(DECODE(POSTN. SQL> @indexes..auto_sample_size.'||C.'||C.NAME.' .NAME||' ASC')) ||CHR(10) ||MAX(DECODE(POSTN.3.NAME. Execute the following queries as DAC Repository owner: SQL> spool indexes.7. CASCADE => true.'Y'.5.Gather_table_stats( NULL.4.6.NAME = 'W_WRKFC_EVT_MONTH_F' AND I.' . W_ETL_INDEX_COL C WHERE T. method_opt => 'FOR ALL INDEXED COLUMNS SIZE AUTO'). W_ETL_INDEX I. Run the spooled file indexes.NAME||' ASC')) ||MAX(DECODE(POSTN.'LOCAL') ||' NOLOGGING.NAME ||' (' ||MAX(DECODE(POSTN.'||C.C. SQL> spool off. 4. If you have indexes with more than seven column positions. estimate_percent => dbms_stats.ISUNIQUE.1.1.TABLE_WID AND T.NAME||' ASC')) ||MAX(DECODE(POSTN.'GLOBAL'.'UNIQUE ') ||DECODE(ISBITMAP.' .2.I.sql in warehouse schema.4.

then you can maintain CURRENT partition only. Define the following source system parameters: • • • Select Design Menu Click on Source System Parameters tab in the right pane Click New Button and define two new parameters with the following attributes: Name: $$CURRENT_YEAR_WID Data Type: SQL Value (click on checkbox icon to define the following parameters): Logical Data Source: DBConnection_OLAP Enter the following SQL: SELECT TO_CHAR(ROW_WID) FROM W_YEAR_D WHERE W_CURRENT_CAL_YEAR_CODE = 'Current' Name: $$PREVIOUS_YEAR_WID Data Type: SQL Value (click on checkbox icon to define the following parameters): Logical Data Source: DBConnection_OLAP Enter the following SQL: SELECT TO_CHAR(ROW_WID) FROM W_YEAR_D WHERE W_CURRENT_CAL_YEAR_CODE = 'Previous' Important: Make sure you select the correct Logical Data Source. Year Partitioning: Disable Local Index Parameter • • • Navigate to Tools -> Seed Data -> Actions -> Index Actions -> New Enter Name: Year Partitioning: Disable Local Index Click on ‘Check’ Icon in Value field 30 . then use the following names / values: Name: $$PREVIOUS_QTR_WID Value: SELECT TO_CHAR(ROW_WID) FROM W_QTR_D WHERE W_CURRENT_CAL_QTR_CODE = 'Previous' Name: $$CURRENT_QTR_WID Value: SELECT TO_CHAR(ROW_WID) FROM W_QTR_D WHERE W_CURRENT_CAL_QTR_CODE = 'Current' Update Index Action Framework Create the following Index Actions in DAC Action Framework: 1.Important: This example below shows how to set up rebuilding indexes and maintaining statistics for last two PREVIOUS and CURRENT partitions for range partitioning by year. when you define these new system parameters. DBConnection_OLAP. If you choose quarterly or yearly range. You should consider implementing PREVIOUS and CURRENT partitions only for monthly or more granular ranges. which points to your target data warehouse. If you choose monthly partitions. Maintaining PREVIOUS partition for partitioning by a quarter or a year may introduce unnecessary overhead and extend your incremental ETL execution time. then use the following names and values: Name: $$PREVIOUS_MONTH_WID Value: SELECT TO_CHAR(ROW_WID) FROM W_MONTH_D WHERE W_CURRENT_CAL_MONTH_CODE ='Previous' Name: $$CURRENT_MONTH_WID Value: SELECT TO_CHAR(ROW_WID) FROM W_MONTH_D WHERE W_CURRENT_CAL_MONTH_CODE = 'Current' If you choose Quarterly partitions.

• • Click on Add button in the new open window Define ‘PREVIOUS_YEAR_WID Local Index’ SQL: Name: Disable PREVIOUS_YEAR_WID Local Indexes Type: SQL Database Connection: target Valid Database Platform: ORACLE • Enter the following command in the lower right Text Area: alter index getIndexName() modify partition PART_@DAC_$$PREVIOUS_YEAR_WID unusable Important!!! Do not use semicolon (. • • Click ‘Add’ button to define the second SQL command. Define ‘CURRENT_YEAR_WID Local Index’ SQL: Name: Disable CURRENT_YEAR_WID Local Index Type: SQL Database Connection: target Valid Database Platform: ORACLE • Enter the following command in the lower right Text Area: alter index getIndexName() modify partition PART_@DAC_$$CURRENT_YEAR_WID unusable • Save the changes. Year Partitioning: Enable Local Index Parameter • • • • • Click ‘New’ in Index Actions window to create a new parameter Enter Name: Year Partitioning: Enable Local Index Click on ‘Check’ Icon in Value field Click on Add button in the new open window Define the following two values: Name Enable PREVIOUS_YEAR_WID Local Index Type: SQL Database Connection: target Valid Database Platform: ORACLE Enter the following command in the lower right Text Area: alter index getIndexName() rebuild partition PART_@DAC_$$PREVIOUS_YEAR_WID nologging Name Enable CURRENT_YEAR_WID Local Index Type: SQL Database Connection: target Valid Database Platform: ORACLE 31 . then use PREVIOUS_MONTH_WID / CURRENT_MONTH_WID or PREVIOUS_QTR_WID / CURRENT_QTR_WID in Action names and SQLs. Month. Quarter. then you need to define separate actions for each range.) at the end of SQLs in Text Area. Note: If you use Quarterly or Monthly partition range. 2. Important!!! If you implement partitioning by Year.

END LOOP. then use PREVIOUS_MONTH_WID / CURRENT_MONTH_WID or PREVIOUS_QTR_WID / CURRENT_QTR_WID in Action names and SQLs. END • Save the changes. Year Partitioning: Enable Local Sub-Partitioned Index Parameter (for composite partitioning only) • • • • • Click ‘New’ in Index Actions window to create a new parameter Enter Name: Year Partitioning: Enable Local Index Click on ‘Check’ Icon in Value field Click on Add button in the new open window Define the following value: Name Enable Local Sub-partitioned Index Type: Stored Procedure Database Connection: target Valid Database Platform: ORACLE Enter the following command in the lower right Text Area: DECLARE CURSOR C1 IS SELECT DISTINCT SUBPARTITION_NAME FROM USER_IND_SUBPARTITIONS WHERE INDEX_NAME='getIndexName()' AND STATUS = 'UNUSABLE'. Year Partitioning: Create Local Bitmap Index Parameter • • • • • Click ‘New’ in Index Actions window to create a new parameter Enter Name: Year Partitioning: Create Local Bitmap Index Click on ‘Check’ Icon in Value field Click on Add button in the new open window Define the following value: Name Create Local Bitmap Indexes Type: SQL Database Connection: target Valid Database Platform: ORACLE Enter the following command in the lower right Text Area: Create bitmap index getIndexName() on getTableName()(getUniqueColumns()) tablespace getTableSpace() local parallel nologging 32 . BEGIN FOR REC IN C1 LOOP EXECUTE IMMEDIATE 'alter index getIndexName() rebuild subpartition '||REC. Note: If you Quarterly or Monthly partition range. 4.SUBPARTITION_NAME||''. 3.Enter the following command in the lower right Text Area: alter index getIndexName() rebuild partition PART_@DAC_$$CURRENT_YEAR_WID nologging • Save the changes.

6.Save the changes. Year Partitioning: Create Global Unique Index Parameter • • • • • Click ‘New’ in Index Actions window to create a new parameter Enter Name: Year Partitioning: Create Global Unique Index Click on ‘Check’ Icon in Value field Click on Add button in the new open window Define the following value: Name Create Local B-Tree Indexes Type: SQL Database Connection: target Valid Database Platform: ORACLE Enter the following command in the lower right Text Area: Create unique index getIndexName() on getTableName()(getUniqueColumns()) tablespace getTableSpace() global parallel nologging Save the changes. Year Partitioning: Gather Partition Stats Parameter • • • Navigate to Tools -> Seed Data -> Actions -> Table Actions -> New Enter Name: Year Partitioning: Gather Partition Stats Click on ‘Check’ Icon in Value field 33 . Year Partitioning: Create Local B-Tree Index Parameter • • • • • Click ‘New’ in Index Actions window to create a new parameter Enter Name: Year Partitioning: Create Local B-Tree Index Click on ‘Check’ Icon in Value field Click on Add button in the new open window Define the following value: Name Create Local B-Tree Index Type: SQL Database Connection: target Valid Database Platform: ORACLE Enter the following command in the lower right Text Area: Create index getIndexName() on getTableName()(getUniqueColumns()) tablespace getTableSpace() local parallel nologging Save the changes. 5. Update Table Action Framework Create the following Table Action in DAC Action Framework: 1.

DEGREE => DBMS_STATS. BEGIN FOR REC IN C1 LOOP DBMS_STATS.PARTITION_NAME FROM USER_IND_PARTITIONS UIP. END LOOP. METHOD_OPT => 'FOR ALL INDEXED COLUMNS SIZE AUTO'. USER_TAB_PARTITIONS UTP WHERE UIP.TABLE_NAME = 'getTableName()' AND UTP. GRANULARITY => 'PARTITION'.AUTO_SAMPLE_SIZE.TABLE_NAME AND UTP. • Save the changes.'PART_@DAC_$$PREVIOUS_YEAR_WID').INDEX_NAME AND UIP.INDEX_NAME=UPI.PARTITION_POSITION AND UPI.PARTITION_POSITION=UIP. then use PREVIOUS_MONTH_WID / CURRENT_MONTH_WID or PREVIOUS_QTR_WID / CURRENT_QTR_WID in Action names and SQLs.GATHER_TABLE_STATS( NULL. END. 2. ESTIMATE_PERCENT => DBMS_STATS. PARTNAME => REC.PARTITION_NAME.DEFAULT_DEGREE). CASCADE => FALSE. Note: If you Quarterly or Monthly partition range.PARTITION_NAME IN ('PART_@DAC_$$CURRENT_YEAR_WID'. Quarter Composite Partitioning: Gather Partition Stats Parameter (for composite partitioning only) • • • • • Navigate to Tools -> Seed Data -> Actions -> Table Actions -> New Enter Name: Quarter Composite Partitioning: Gather Partition Stats Click on ‘Check’ Icon in Value field Click on Add button in the new open window Define the following value: Name: Gather Partition Stats Type: Stored Procedure Database Connection: target Valid Database Platform: ORACLE Enter the following command in the lower right Text Area: DECLARE CURSOR C1 IS 34 .• • Click on Add button in the new open window Define the following value: Name: Gather Partition Stats Type: Stored Procedure Database Connection: target Valid Database Platform: ORACLE Enter the following command in the lower right Text Area: DECLARE CURSOR C1 IS SELECT DISTINCT UTP.TABLE_NAME=UPI. USER_PART_INDEXES UPI. TABNAME => 'getTableName()'.STATUS = 'USABLE' AND UTP.

PARTITION_POSITION AND UPI. PARTNAME => REC. DEGREE => DBMS_STATS. The global index must NOT have any assigned index action tasks. GRANULARITY => 'PARTITION'.PARTITION_POSITION=UIP.PARTITION_NAME IN ('PART_@DAC_$$CURRENT_QTR_WID'. TABNAME => 'getTableName()'.AUTO_SAMPLE_SIZE. BEGIN FOR REC IN C1 LOOP DBMS_STATS. • • • • • • • • • • • • • • Right click your mouse on the generated list (Upper right pane) and select ‘Add Actions’ Select ‘Drop Index’ from Action Type field Select ‘Incremental’ from Load Type field Click on Checkbox icon in Action field Select ‘Year Partitioning: Disable Local Indexes’ Action Name Click OK in Choose Action window Click OK in Add Actions window.'PART_@DAC_$$PREVIOUS_QTR_WID').TABLE_NAME=UPI. Important!!! Make sure you exclude the selected global index from the index query result set. defined in Index Action Framework. END.INDEX_NAME AND UIP. Navigate to Design -> Indices -> Query ->Table Name 'W_WRKFC_EVT_MONTH_F'.STATUS = 'USABLE' AND UTP.INDEX_NAME=UPI. END LOOP.TABLE_NAME = 'getTableName()' AND UTP. Un-checking these properties would signal DAC to skip any actions.PARTITION_NAME. USER_TAB_PARTITIONS UTP WHERE UIP. ESTIMATE_PERCENT => DBMS_STATS.PARTITION_NAME FROM USER_IND_PARTITIONS UIP. METHOD_OPT => 'FOR ALL INDEXED COLUMNS SIZE AUTO'. CASCADE => FALSE.GATHER_TABLE_STATS( NULL. USER_PART_INDEXES UPI. Right click your mouse on the generated list (Upper right pane) and select ‘Add Actions’ one more time Select ‘Create Index’ from Action Type field Select ‘Incremental’ from Load Type field Click on Checkbox icon in Action field Select ‘Year Partitioning: Enable Local Indexes’ Action Name Click OK in Choose Action window Click OK in Add Actions window.DEFAULT_DEGREE). Important!!! DO NOT change ‘Drop / Create Always’ or ‘Drop / Create Always Bitmap’ properties for the modified indexes.SELECT DISTINCT UTP. check ‘Is Bitmap’ checkbox -> Go. Attach Index Action to the desired indexes • Retrieve all local indexes on partitioned tables.TABLE_NAME AND UTP. 35 .

which populates a partitioned table. ‘Year Partitioning: Create Local B-Tree Index’ and ‘Year Partitioning: Create Global Unique Index’ Index Action Tasks.The steps above apply to all indexes. when attaching ‘Year Partitioning: Create Local Bitmap Index’. Attach Table Action to the converted partitioned table • • • • • • • • Retrieve the partitioned tables. Even though you select Drop/Create Index Action Type. ‘Year Partitioning: Create Local B-Tree Index’ and ‘Year Partitioning: Create Global Unique Index’ to the appropriate indexes. If you want to attach the defined Index Actions for an individual index. to validate the correct sequence of steps without executing them. Important: Make sure you choose ‘Initial’ from Load Type field. used in an initial ETL run. If you want to attach the defined Table Action for an individual table. Whenever DAC encounter ‘Analyze Table’ step for an updated table. 36 . it will make it unusable for the last two partitions. and click on ‘Actions’ sub-tab in the lower pane. defined in Index Action Framework. DAC will override these actions with the steps. Unit test the changes for converted partitioned tables in DAC You can generate the list of actions for a single task. Then click ‘New’ button in the lower pane and fill in the appropriate values in the new line. Right click your mouse on the generated list (Upper right pane) and select ‘Add Actions’ Select ‘Analyze Table’ from Action Type field Select ‘Incremental’ from Load Type field Click on Checkbox icon in Action field Select ‘Year Partitioning: Gather partition stats’ Action Name Click OK in Choose Action window Click OK in Add Actions window. it will override the default action by the set of steps from Table Action Framework. and for ‘Create Index’ – rebuild the index for the last two partitions. Navigate to Design -> Tables -> Query -> Name 'W_WRKFC_EVT_MONTH_F' -> Go. retrieved by your query. and click on ‘Actions’ sub-tab in the lower pane. Important!!! Make sure you use ‘Quarter Composite Partitioning: Gather Partition Stats’ parameter for composite range-range tables. Every time. DAC encounter ‘Drop Index’ step for an updated index. then select the desired index in the right upper pane. • Repeat the same steps above to attach ‘Year Partitioning: Create Local Bitmap Index’. Follow the steps below to unit test the sequence of steps for a partitioned table: • • • • • Select ‘Execute’ button from your top sub-menu Select your execution plan in the upper right pane Click ‘Ordered tasks’ sub-tab in the lower right pane Retrieve the task which populates your partitioned table Click ‘Unit test’ button in the lower right pane menu. then select the desired table in the right upper pane. Then click ‘New’ button in the lower pane and fill in the appropriate values in the new line.

POSTED_ON_WID column is based on monthly range partitions with values less than 20041101. W_POSITION_DH. Interval Partitioning Oracle 11G introduced a new partitioning type. The target tables for such mappings should NOT be compressed. Older.0. You must apply the following database patches 8834636 and 8930565. so Oracle wouldn’t create any partitions in-between. 8. TABLE COMPRESSION IMPLEMENTATION GUIDELINES Oracle Database table compression can be applied effectively to optimize the space consumption and reduce memory use in buffer cache in Oracle Business Analytics Data Warehouse. Make sure you carefully benchmark the mappings using compressed tables before implementing the compression in your production data warehouse. updated by SIL_PositionDimensionHierarchy_AsIsUpdate_Full. It’s a valuable feature. There is a smaller set of initial mappings. 20050201. loaded during incremental ETLs. With Interval Partitioning there is no need to pre-create partitions for data in the future. especially for very large incremental volumes.. faster end user query performance. 20041201. Compressed tables require significantly less disk storage and result in improved query performance due to reduced I/O and buffer cache requirements. 20050101. especially in a warehouse environment. If you couldn’t change their Load type to Bulk. Staging tables are truncated during incremental ETLs. After compressing a table you need to rebuild all its indexes (ALTER INDEX …. REBUILD syntax). Consider implementing table compression for Partitioned Fact tables at partition level: a. For example. Oracle Business Intelligence Applications delivers several Informatica mappings. Important!!! DO NOT execute them in your data warehouse. relatively static partitions can be good compression candidates 7. Check with Oracle Support for any additional database patches. The majority of recommended partitioning keys in Oracle BI Applications are using DATE format YYYYMMDD. data volumes and ETL performance benchmarks. Oracle automatically creates new partitions with pre-defined range interval. Interval Partitioning.• • Click ‘Yes’ to proceed with unit testing. should be uncompressed b. where data loaded once. 2. You can specify INTERVAL 100 for such range format. then leave their corresponding target tables uncompressed. which perform mass updates during Initial ETL. Review the following recommendations and guidelines before table compression implementation: 1. while keeping incremental ETL within acceptable execution time frame. Table compression requires careful analysis and planning to take the advantage of efficient space consumption. 37 . Incremental Informatica mappings always use Normal Load mode. Table compression should be implemented for target tables after careful analysis of DML operation types. 4. The majority of Initial Informatica mappings use Bulk Load. • Exit unit testing window. which use Normal Load type in Informatica. etc. is an example of compression exception. Oracle will skip creating partitions for ranges with no data.7 or higher.1. and read many times by end user queries. so their target tables can be compressed to deliver comparable or better ETL performance. In the example with POSTED_ON_WID there is a very large gap between ranges 20041201 and 20050101. 6. The recommended Oracle Database version is 11. 5. so they can be considered for compression. so table compression may cause performance overhead. Active partitions. Validate the generated sequence of steps in the new output window. 3.

so you should avoid using nested loops by incorporating hint USE_HASH for tables with volumes over ten million records.'MM/DD/YYYY HH24:MI:SS') OR PAY_INPUT_VALUES_F. but the overall time for fetching all the records would be reduced quite dramatically. have indexes defined on the joining columns in a WHERE clause.LAST_UPDATE_DATE >= TO_DATE('01/01/2007 00:00:00'.RUN_RESULT_ID. PAY_RUN_RESULTS.LAST_UPDATE_DATE. Initial records fetch may take more time as hash joins are built in memory. PAY_ELEMENT_TYPES_F.LAST_UPDATE_DATE >= TO_DATE('01/01/2007 00:00:00'.ELEMENT_TYPE_ID.ASSIGNMENT_ID. PAY_ELEMENT_TYPES_F. PAY_INPUT_VALUES_F. Specifying the hint USE_HASH would change the execution plan to use a full table scan (in some cases the optimizer might still use indexes. PAY_RUN_RESULTS. PAY_ELEMENT_TYPES_F. PER_TIME_PERIODS. PAY_PAYROLL_ACTIONS.LAST_UPDATED_BY. PAY_PAYROLL_ACTIONS. PAY_INPUT_VALUES_F.RESULT_VALUE. PER_TIME_PERIODS WHERE (PAY_PAYROLL_ACTIONS.PAY_ADVICE_DATE. PAY_PAYROLL_ACTIONS. ETL is a batch process. in spite of the higher estimated query cost.OUTPUT_CURRENCY_CODE. Although this approach may start returning results sooner the overall time to fetch all the records could be considerably longer. so it is important not to kill the query. measured by overall time to load all the records. PAY_ASSIGNMENT_ACTIONS.END_DATE. Important: Oracle might take up to 8-10 hours just to build hashes in memory for very large tables (over 100 million records). PAY_PAYROLL_ACTIONS.ASSIGNMENT_ACTION_ID.START_DATE. PAY_PAYROLL_ACTIONS. PAY_PAYROLL_ACTIONS. PER_TIME_PERIODS.LAST_UPDATE_DATE LAST_UPDATE_DATE2 FROM PAY_RUN_RESULT_VALUES. PAY_RUN_RESULT_VALUES. Table --------------------PAY_RUN_RESULT_VALUES PAY_RUN_RESULTS PAY_ASSIGNMENT_ACTIONS PAY_INPUT_VALUES_F PAY_ELEMENT_TYPES_F PAY_PAYROLL_ACTIONS PAY_ELEMENT_CLASSIFICATIONS PER_TIME_PERIODS No of Rows ---------900 Million 14 Million 50 Million 10000 10000 1445896 1897 52728 SELECT PAY_ASSIGNMENT_ACTIONS. reported in very large volume Oracle Business Analytics Data Warehouses. PAY_RUN_RESULT_VALUES. PAY_ASSIGNMENT_ACTIONS. PAY_ELEMENT_CLASSIFICATIONS. PAY_ELEMENT_TYPES_F.INPUT_CURRENCY_CODE. the optimizer might choose Nested loop join over Hash join accessing a table using an index defined on a column. sometimes database hints can help to improve efficiency and increase overall ETL performance.CREATED_BY. The numbers are applicable to the specific test case configuration. such as index fast full scan) for a table involved in the query.INPUT_VALUE_ID. used in a join.LAST_UPDATE_DATE LAST_UPDATE_DATE1.GUIDELINES FOR ORACLE OPTIMIZER HINTS USAGE IN ETL MAPPINGS Hash Joins versus Nested Loops in Oracle RDBMS Though Oracle optimizer chooses the most efficient plan with the least cost for a query. PAY_RUN_RESULT_VALUES. The real life example below provides the comparison between NESTED LOOPS and HASH JOIN execution. If tables. which would vary depending on hardware specifications and database settings. used in a query.CREATION_DATE.'MM/DD/YYYY HH24:MI:SS') 38 .

EFFECTIVE_DATE BETWEEN PAY_INPUT_VALUES_F.RUN_RESULT_ID = PAY_RUN_RESULTS.EFFECTIVE_END_DATE AND PAY_ELEMENT_CLASSIFICATIONS.TIME_PERIOD_ID = PAY_PAYROLL_ACTIONS.LAST_UPDATE_DATE >= TO_DATE('01/01/2007 00:00:00'.ACTION_POPULATION_STATUS = 'C' AND PAY_ASSIGNMENT_ACTIONS. 'E') The Explain Plan for the query is below: Plan hash value: 1498624813 Id 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 Operation Name Rows 60 55 59 7 38937 5503 1626 5505 3369 3369 3527 15 15 96393 96393 52728 SELECT STATEMENT CONCATENATION NESTED LOOPS HASH JOIN TABLE ACCESS BY INDEX ROWID PAY_ASSIGNMENT_ACTIONS NESTED LOOPS HASH JOIN TABLE ACCESS FULL PAY_ELEMENT_CLASSIFICATIONS MERGE JOIN SORT JOIN HASH JOIN MERGE JOIN SORT JOIN TABLE ACCESS FULL PAY_INPUT_VALUES_F FILTER SORT JOIN TABLE ACCESS FULL PAY_PAYROLL_ACTIONS TABLE ACCESS FULL PER_TIME_PERIODS FILTER SORT JOIN TABLE ACCESS FULL PAY_ELEMENT_TYPES_F INDEX RANGE SCAN PAY_ASSIGNMENT_ACTIONS_N50 TABLE ACCESS FULL PAY_RUN_RESULTS TABLE ACCESS BY INDEX ROWID PAY_RUN_RESULT_VALUES INDEX UNIQUE SCAN PAY_RUN_RESULT_VALUES_PK NESTED LOOPS HASH JOIN NESTED LOOPS NESTED LOOPS NESTED LOOPS NESTED LOOPS NESTED LOOPS TABLE ACCESS FULL PAY_INPUT_VALUES_F TABLE ACCESS BY INDEX PAY_PAYROLL_ACTIONS ROWID INDEX RANGE SCAN PAY_PAYROLL_ACTIONS_N5 TABLE ACCESS BY INDEX PER_TIME_PERIODS ROWID INDEX UNIQUE SCAN PER_TIME_PERIODS_PK TABLE ACCESS BY INDEX ROWID PAY_ASSIGNMENT_ACTIONS INDEX RANGE SCAN PAY_ASSIGNMENT_ACTIONS_N50 TABLE ACCESS BY INDEX ROWID PAY_RUN_RESULTS INDEX RANGE SCAN PAY_RUN_RESULTS_N50 TempS Cost (%CPU) Time pc 14040 111K (2) 00:22:23 Bytes 12870 12980 8064K 147 7604K 961K 47154 806K 355K 355K 292K 675 675 3765K 11M 3765K 1184K 83423 83304 7 47490 9053 13 9039 8931 8930 8579 156 155 8424 7424 349 106 105 3 20007 3 2 19634 19630 19524 14863 8538 6974 6740 155 6585 341 23 147 20 1 0 7 3 4 2 (2) (2) (0) (1) (4) (0) (4) (4) (4) (4) (3) (2) 00:16:42 00:16:40 00:00:01 00:09:30 00:01:49 00:00:01 00:01:49 00:01:48 00:01:48 00:01:43 00:00:02 00:00:02 (4) 00:01:42 (5) 00:01:30 (1) 00:00:05 (3) (2) (0) (4) (0) (0) (1) (1) (1) (1) (1) (1) (1) (2) 00:00:02 00:00:02 00:00:01 00:04:01 00:00:01 00:00:01 00:03:56 00:03:56 00:03:55 00:02:59 00:01:43 00:01:24 00:01:21 00:00:02 654 27468 654 27468 35 9986K 190M 1 14 1 4 936 4 820 1460 232K 1552 225K 1579 198K 223 24084 234 19890 1 45 241 72295 1 1 7 35 1 20 9640 (1) 00:01:20 (1) 00:00:05 (0) 00:00:01 (0) (0) (0) (0) (0) 00:00:01 00:00:01 00:00:01 00:00:01 00:00:01 39 .RUN_RESULT_ID AND PAY_RUN_RESULT_VALUES.SOURCE_TYPE IN ('I'.ACTION_STATUS = 'C' AND PAY_INPUT_VALUES_F.EFFECTIVE_START_DATE AND PAY_ELEMENT_TYPES_F.ELEMENT_TYPE_ID = PAY_ELEMENT_TYPES_F.NAME = 'Pay Value' AND CLASSIFICATION_NAME NOT LIKE '%Information%' AND CLASSIFICATION_NAME NOT LIKE '%Employer%' AND CLASSIFICATION_NAME NOT LIKE '%Balance%' AND PAY_RUN_RESULTS.INPUT_VALUE_ID = PAY_INPUT_VALUES_F.ELEMENT_TYPE_ID AND PAY_ASSIGNMENT_ACTIONS.ASSIGNMENT_ACTION_ID AND PAY_RUN_RESULTS.ASSIGNMENT_ACTION_ID = PAY_ASSIGNMENT_ACTIONS.'MM/DD/YYYY HH24:MI:SS')) AND PAY_PAYROLL_ACTIONS.EFFECTIVE_END_DATE AND PAY_PAYROLL_ACTIONS.ACTION_STATUS = 'C' AND PAY_PAYROLL_ACTIONS.OR PAY_ELEMENT_TYPES_F.EFFECTIVE_START_DATE AND PAY_INPUT_VALUES_F.EFFECTIVE_DATE BETWEEN PAY_ELEMENT_TYPES_F.TIME_PERIOD_ID AND PAY_INPUT_VALUES_F.PAYROLL_ACTION_ID AND PAY_PAYROLL_ACTIONS.CLASSIFICATION_ID = PAY_ELEMENT_TYPES_F.CLASSIFICATION_ID AND PER_TIME_PERIODS.UOM = 'M' AND PAY_RUN_RESULT_VALUES.INPUT_VALUE_ID AND PAY_RUN_RESULTS.PAYROLL_ACTION_ID = PAY_PAYROLL_ACTIONS.

41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 TABLE ACCESS BY INDEX ROWID INDEX UNIQUE SCAN TABLE ACCESS FULL TABLE ACCESS BY INDEX ROWID INDEX UNIQUE SCAN NESTED LOOPS NESTED LOOPS HASH JOIN TABLE ACCESS BY INDEX ROWID NESTED LOOPS NESTED LOOPS NESTED LOOPS MERGE JOIN SORT JOIN TABLE ACCESS FULL FILTER SORT JOIN TABLE ACCESS FULL TABLE ACCESS BY INDEX ROWID INDEX UNIQUE SCAN TABLE ACCESS BY INDEX ROWID INDEX RANGE SCAN INDEX RANGE SCAN TABLE ACCESS FULL TABLE ACCESS BY INDEX ROWID INDEX UNIQUE SCAN TABLE ACCESS BY INDEX ROWID INDEX UNIQUE SCAN PAY_RUN_RESULT_VALUES PAY_RUN_RESULT_VALUES_PK PAY_ELEMENT_TYPES_F PAY_ELEMENT_CLASSIFICATION _S PAY_ELEMENT_CLASSIFICATION _PK 1 1 9873 1 1 1 1 1 1 213 217 31 32 14 14 939 939 1 1 7 35 20 9873 1 1 1 1 14 404K 29 3 2 105 1 0 (0) 00:00:01 (0) 00:00:01 (2) 00:00:02 (0) 00:00:01 (0) 00:00:01 (4) (4) (4) (0) (4) (4) (5) (5) (3) (2) 00:01:46 00:01:46 00:01:46 00:00:01 00:01:45 00:01:34 00:01:32 00:01:31 00:00:02 00:00:02 PAY_RUN_RESULTS PAY_INPUT_VALUES_F 234 205 191 20 31737 27993 3348 2720 630 630 37560 37560 23 8809 8808 8805 4 8699 7829 7612 7580 156 155 7424 7423 1 0 PAY_PAYROLL_ACTIONS PER_TIME_PERIODS PER_TIME_PERIODS_PK PAY_ASSIGNMENT_ACTIONS PAY_ASSIGNMENT_ACTIONS_N50 PAY_RUN_RESULTS_N50 PAY_ELEMENT_TYPES_F PAY_RUN_RESULT_VALUES PAY_RUN_RESULT_VALUES_PK PAY_ELEMENT_CLASSIFICATIONS PAY_ELEMENT_CLASSIFICATION_ PK (5) 00:01:30 (5) 00:01:30 (0) 00:00:01 (0) 00:00:01 (0) 00:00:01 (0) (0) (2) (0) (0) (0) 00:00:01 00:00:01 00:00:02 00:00:01 00:00:01 00:00:01 147 7 3 2 105 3 2 1 0 404K 14 29 (0) 00:00:01 The query took more than 48 hours to execute and produced 128 million records even though the first record was fetched within 1. The reported throughput achieved is 700 RPS. and then joined the result sets using Nested Loops. Note: The optimizer chose to access the tables through index paths. the query completed much faster. After adding the hint USE_HASH(PAY_RUN_RESULT_VALUES PAY_RUN_RESULTS PAY_INPUT_VALUES_F PAY_ASSIGNMENT_ACTIONS PAY_ELEMENT_TYPES_F PAY_PAYROLL_ACTIONS PAY_ELEMENT_CLASSIFICATIONS PER_TIME_PERIODS) to the preceding query.5 hours of the execution. the optimizer produced the following execution plan: Plan hash value: 3421230164 Id 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Operation SELECT STATEMENT HASH JOIN HASH JOIN TABLE ACCESS FULL HASH JOIN HASH JOIN HASH JOIN TABLE ACCESS FULL HASH JOIN HASH JOIN TABLE ACCESS FULL TABLE ACCESS FULL TABLE ACCESS FULL TABLE ACCESS FULL TABLE ACCESS FULL TABLE ACCESS FULL Rows 10 10 10 PAY_INPUT_VALUES_F 15 103K 1624 1700 PAY_ELEMENT_TYPES_F 10527 670K 682K PAY_PAYROLL_ACTIONS 96393 PAY_ASSIGNMENT_ACTIONS 10M PAY_RUN_RESULTS 9986K PER_TIME_PERIODS 52728 PAY_RUN_RESULT_VALUES 912M PAY_ELEMENT_CLASSIFICATIONS 1626 Name Bytes TempSpc 2340 2340 2050 675 15M 231K 204K 431K 51M 47M 39M 4896K 3765K 203M 190M 1184K 11G 47154 Cost (%CPU) 932K (5) 932K (5) 932K (5) 155 (2) 932K (5) 167K (3) 166K (3) 105 (2) 166K (3) 128K (3) 7424 (5) 105K (3) 20007 (4) 349 (1) 751K (4) 13 (0) Time 03:06:29 03:06:29 03:06:28 00:00:02 03:06:27 00:33:28 00:33:23 00:00:02 00:33:22 00:25:48 00:01:30 00:21:03 00:04:01 00:00:05 02:30:21 00:00:01 Even though the estimated cost went up. Below is the summary of two executions: 40 .

which helped to improve Oracle Business Intelligence Applications 7. OM FIN.9.5. Adapter Mapping name ETL Recommended hints mode Common Dimensions Siebel. Initial Initial Incr. SIL_Agg_ResponseCampaign 41 . SIL_PartyDimension_Person SCA OM Siebel PRJ. PRJ. SCA. PRJ. SCA SIL_GLAccountDimension_SCDUpdate Incr.6 The following table summarizes the database hints. SCA. OM. Initial / Incr. SCM. Initial SIL_PartyDimension_Person Initial SIL_Agg_OverlappingCampaign_Accou Incr. SDE_ORA_PartyOrganizationDimensio OM. DOM_REL) */ /*+ USE_HASH(HZ_ORGANIZATION_PROFILES HZ_PARTIES) */ /*+ INDEX (TARGET_TABLE W_GL_ACCOUNT_D_U1) INDEX (SCD_OUTER W_GL_ACCOUNT_D_U1)*/ $$HINT1:/*+ INDEX(PP HZ_PARTIES_U1)*/ $$HINT2: /*+ USE_HL(OC TMP1)*/ /*+ FULL(PER_ALL_PEOPLE_F) */ Siebel CRM SIL_ResponseFact_Full Initial /*+ NO_INDEX(w_regn_d) NO_INDEX(w_segment_d) NO_INDEX(offer) NO_INDEX(terr) NO_INDEX(W_WAVE_D) NO_INDEX(w_ld_wave_d) NO_INDEX(w_source_d) */ $$HINT1: /*+ USE_HASH(PTY PER DS) FULL(PTY) */ $$HINT1 /*+ NO_INDEX(SRC) NO_INDEX(OSRC) */ $$HINT2 /*+ FULL(W_CAMP_HIST_F) */ $$HINT3 /*+ FULL(W_CAMP_HIST_F) */ $$HINT1 /*+ NO_INDEX(SRC) NO_INDEX(OSRC) */ $$HINT2 /*+ FULL(W_CAMP_HIST_F) */ $$HINT3 /*+ FULL(W_CAMP_HIST_F) */ /*+ FULL(W_PARTY_PER_D) */ EBS Supply Chain 11. /*+ USE_HASH(PTY PER DS) NO_INDEX(PTY) */ /*+ NO_INDEX(ORG) */ set DTM Buffer Size to 32000000 set Default Buffer Block Size to 128000 $$HINT1: /*+ USE_HASH(PER PTY CNP SUP)*/ $$HINT2: /*+ USE_HASH(PP) */ $$HINT1: /*+ USE_HASH(HZ_ORGANIZATION_PROFILES HZ_PARTIES ) */ $$HINT2: /*+USE_HASH(DOM_ULT_DUNS. SCM.10 SDE_ORA_PurchaseReceiptFact SDE_ORA_StandardCostGeneral_Full SIL_ExpenseFact_FULL SIL_APInvoiceDistributionFact_Full Initial / Incr. HCM. nts SIL_Agg_OverlappingCampaign_Conta cts Incr. OM SIL_PartyDimension_Organization SDE_PartyPersonDimension SDE_ORA_PartyPersonDimension_Cu stomer Initial Initial Initial / Incr. SDE_ORA_PartyContactStaging SDE_ORA_INVENTORYPRODUCTDI MENSION_FULL Incr. PRJ n_Customer PRJ FIN. PRJ n_Customer_Full SCA.6 mappings performance in internal performance tests. SDE_ORA_PartyOrganizationDimensio OM. OM.Query CPU Cost First records Fetch Start Time After 1 hour 30 min After 5 hours Reported Informatica Throughput 700 rows / sec 3000 rows / sec Mapping Execution Time 48 hours 10 hours No Hints (nested loops) Hash Join hint 111K 923K Suggested hints for Oracle Business Intelligence Applications 7. SIL_Agg_ResponseCampaignOffer and Incr. Initial Initial /*+ FULL(RCV_TRANSACTIONS) */ /+ USE_HASH(MTL_SYSTEM_ITEMS_B)/ /*+ USE_HASH(W_PROJECT_D) */ /*+ USE_HASH(W_AP_INV_DIST_FS PO_PLANT_LOC PO_RCPT_LOC SCA.9.

4) use_hash(AP_INVOICES_ALL AP_INVOICE_DISTRIBUTIONS_ALL PO_HEADERS_ALL PO_DISTRIBUTIONS_ALL PO_LINES_ALL)*/ /*+ PARALLEL (W_ORA_GL_JOURNALS_F_TMP. Incr.OPERATING_UNIT_ORG PAYABLES_ORG PURCHASE_ORG W_LEDGER_D INV_TYPE DIST_TYPE SPEND_TYPE APPROVAL_STATUS PAYMENT_STATUS W_AP_TERMS_D W_PROJECT_D EXPENDITURE_ORG CREATED_BY CHANGED_BY W_XACT_SOURCE_D W_Financial_Resource_D W_GL_ACCOUNT_D W_PARTY_D W_SUPPLIER_ACCOUNT_D) */ SDE_ORA_BOMHeaderDimension_Full Initial SDE_ORA_PROJECT_HIERARCHYDI MENSION_STAGE1 SDE_ORA_TASKS Initial / Incr. W_AP_XACT_F_M1) */ /*+ full(W_GL_ACCOUNT_D) full(W_STATUS_D) full(W_AP_XACT_F) full(W_XACT_TYPE_D) full(D1) full(D2) full( D3)*/ EBS Projects R12 SDE_ORA_ProjectFundingHeader Initial / /*+ USE_HASH(PA_PROJECTS_ALL PA_TASKS PA_AGREEMENTS_ALL Incr. /*+ FULL(M) */ /*+ USE_HASH(PPV1 PPV2 POR1 POR2 PPEVS1 PPE1 PPE2 PPA2) */ $$HINT1 /*+ USE_HASH(PA_TASKS PA_TASK_TYPES PA_PROJ_ELEMENT_VERSIONS PA_PROJ_ELEMENTS PA_PROJECT_STATUSES PA_PROJ_ELEM_VER_STRUCTURE PA_PROJECTS_ALL PA_PROJECT_TYPES_ALL PA_PROJ_ELEM_VER_SCHEDULE) */ $$HINT2 /*+ USE_HASH(PA_PROJECTS_ALL PA_PROJECT_TYPES_ALL PA_TASKS) */ $$HINT3 /*+ USE_HASH(PE PEV PPS) */ SIL_PRODUCTTRANSACTIONFACT SIL_PURCHASECOSTFACT SIL_APINVOICEDISTRIBUTIONFACT Initial Initial Incr. Initial / Incr. E_LOAD PLP_WorkforceEventFact_Month Initial /*+ parallel(W_PAYROLL_FS. Initial / Incr. /*+ USE_HASH(SRC_PRO_D TO_PRO_D) */ /*+ USE_HASH(W_PROJECT_D) */ Apply hint to Lkp_W_AP_INV_DIST_F query: /*+ INDEX(TARGET_TABLE) */ EBS Human Resources R12 SDE_ORA_PayrollFact_Full Initial $$HINT1: /*+ USE_HASH( PAY_RUN_RESULT_VALUES PAY_RUN_RESULTS PAY_INPUT_VALUES_F PAY_ASSIGNMENT_ACTIONS PAY_ELEMENT_TYPES_F PAY_PAYROLL_ACTIONS PAY_ELEMENT_CLASSIFICATIONS PER_TIME_PERIODS ) */ $$HINT2: /*+ ORDERED USE_HASH( PAY_RUN_RESULT_VALUES PAY_RUN_RESULTS PAY_INPUT_VALUES_F PAY_ASSIGNMENT_ACTIONS PAY_ELEMENT_TYPES_F PAY_PAYROLL_ACTIONS PAY_ELEMENT_CLASSIFICATIONS PER_TIME_PERIODS ) */ $$HINT3: /*+ FULL(PER_ALL_ASSIGNMENTS_F) FULL(PER_ALL_PEOPLE_F) */ SDE_ORA_PayrollFact_Agg_Items_Der Initial ive_Full PLP_RECRUITMENTHIREAGGREGAT Incr. /*+ parallel(AP_INVOICE_DISTRIBUTIONS_ALL. 4) */ /*+ USE_HASH (HZ_PARTIES)*/ /*+ USE_HASH(AR_PAYMENT_SCHEDULES_ALL RA_CUSTOMER_TRX_ALL RA_CUSTOMER_TRX_ALL1 AR_PAYMENT_SCHEDULES_ALL1 AR_DISTRIBUTIONS_ALL) */ /*+ index(W_AP_XACT_F. PLP_APXactsGroupAccount_A_Stage_ Initial Full 42 . Distribution SDE_ORA_Stage_GLJournals_Derive SDE_ORA_CustomerFinancialProfileDi mension SDE_ORA_ARTransactionFact_Credit MemoApplication PLP_APIncrActivityLoad Incr.4)*/ $$HINT1: /*+ USE_HASH (FACT MONTH PERF LOC SOURCE AGE EMP)*/ /*+ FULL(suph) */ EBS Financials R12 SDE_ORA_APTransactionFact_Liability Incr.

6 Workflow Manager Check out the corresponding session and drag it to Task Developer palette Open the session 43 .10 SDE_ORA_EntitlementDimension SDE_ORA_AgreeDimension SDE_ORA_AbsenceEvent SIL_ActivityFact_Full Initial Initial Initial Initial /*+ parallel(OKC_K_LINES_TL.6 Designer Check out the selected mapping and drag it to Mapplet Designer palette Navigate to Mapplets menu -> Parameters and Variables Click on the Add New Variable icon Fill in the following fields in a new line: o o o o o o Name: $$HINT1.5. You can manually define $$HINT variables in your DAC and Informatica repositories by following the steps below: Connect to Informatica PowerCenter 8. etc. These hints are not included into the packaged mappings. EBS Order Management (Enterprise Sales) 11. SDE_ORA_ProjectInvoiceLine_Fact SDE_ORA_ProjectCostLine_Fact Initial Initial PA_SUMMARY_PROJECT_FUNDINGS) */ /*+ USE_HASH(pa_draft_invoice_items pa_tasks pa_draft_invoices_all pa_projects_all pa_agreements_all pa_lookups) */ /*+ USE_HASH(pa_cost_distribution_lines_all pa_expenditure_items_all pa_expenditures_all pa_implementations_all pa_implementations_all_1 gl_sets_of_books pa_project_assignments pa_resource_list_members pa_lookups pa_projects_all pa_project_types_all pa_expenditure_types) */ /*+ INDEX(LOOKUP_TABLE W_PARTY_D_M3) */ SIL_ProjectFundingHeader_Fact Incr. You can consider applying them to your environments after verifying mappings execution with the hints in your test environment.4) */ /*+ NO_MERGE(fndv) */ /*+ use_hash(per_absence_attendances per_all_assignments_f per_absence_attendance_types per_abs_attendance_reasons ) */ /*+ use_hash(W_ACTIVITY_FS W_FS_ACT_CST_FS W_SOURCE_D W_ENTLMNT_D W_AGREE_D W_REGION_D W_SRVREQ_D W_ASSET_D) */ You may consider using the recommended hints for the mappings above for other versions only after careful testing and benchmarking ETL runtime and performance.Incr.10 SIL_SalesPickLinesFact_Full SIL_SalesOrderLinesFact_Full SIL_SalesInvoiceLinesFact_Full SIL_SalesScheduleLinesFact_Full Initial Initial Initial Initial /*+ FULL(A18) FULL(A19) FULL(A20) FULL(A21) FULL(A22) */ /*+ FULL(A18) FULL(A19) FULL(A20) FULL(A21) FULL(A22) */ /*+ FULL(A18) FULL(A19) FULL(A20) FULL(A21) FULL(A22) */ /*+ FULL(A18) FULL(A19) FULL(A20) FULL(A21) FULL(A22) */ EBS Service 11. 2.4) parallel (OKC_K_LINES_B. defined in DAC.5. Each mapping may have $$HINT placeholders. Type: Parameter Datatype: String Precision: make sure you specify the sufficient precision to cover your hint value Click OK Save the changes and check in the mapping into the Informatica repository Connect to Informatica PowerCenter 8.

1 invokes Informatica PowerCenter 8. Oracle CBO determines whether a query would benefit from dynamic sampling at the query compile time. However.xml Replace each occurrence of <-lpf> with <-paramfile> in the configuration file Save the changes Restart DAC server and test the solution.3. Using Oracle Optimizer Dynamic Sampling for big staging tables A typical Source Dependent Extract (SDE) task contains the following steps: Truncate staging table Extract data from one or more OLTP tables into staging table Analyze staging table The last step computes statistics on the table to make sure that Oracle Cost Based Optimizer (CBO) builds the best execution plan for the next task. yet accurate enough alternative to use dynamic sampling instead of gathering table statistics.1. Informatica may not pick the valid parameter values. you can resolve the issue by implementing the following steps: Connect to your machine.4. Important: DAC 10. The purpose of dynamic sampling is to improve server performance by determining more accurate estimates for predicate selectivity and statistics for tables and indexes. during the initial loads that process very large data volumes. Some of the recommended hints can be very long and not fit into a single line. If your DAC and Informatica servers share the same machine. that the Analyze Table job would take many hours to complete. Oracle RDBMS offers a faster. the staging table may become so large (hundreds of millions of rows).6 command line API with <–lpf> option.- Click on Mapping tab and select SQ (SQL Qualifier) under Sources folder in the left pane Click on Select Query attribute value Insert the defined $$HINT? Variable Save the changes Connect to DAC client Select the custom container Click on Design button and select Tasks menu in the right pane Retrieve the task which corresponds to the selected Informatica mapping Click on Parameters menu in the lower pane Fill in the fields in a new line: o o o o o Name: use the exact variable name defined in Informatica above Data Type: Text Load Type: select the load type from the list of values Value: enter the hint value here Save the changes - Verify the changes by inspecting the session log for the select mapping during the next ETL. As a result. Oracle Optimizer would issue a recursive SQL statement to 44 . running DAC and Informatica servers Open <DAC_HOME>\Conf\infa_command.

CUSTOM INDEXES IN ORACLE EBS FOR INCREMENTAL LOADS PERFORMANCE Introduction Oracle EBS source database tables contain mandatory LAST_UPDATE_DATE columns. you can abort the execution plan in DAC. which run the queries against the large staging table by inserting Dynamic Sampling hints into the appropriate mapping SQLs. performed on large staging tables. Below are the details of one of the internal benchmark tests: Hardware configuration: 8 CPU cores x 16Gb RAM x 2Tb NAS server with Linux 64bit OS Target Database: Oracle 10. and to apply the relevant single table predicates to estimate selectivity for each predicate. show that optimizer can produce efficient execution plans by utilizing dynamic sampling feature at much shorter time compared to gathering table stats using conventional methods. introduced in Oracle EBS Release 12. which do not have indexes on LAST_UPDATE_DATE in any EBS releases. joined with two smaller dimension tables Test Scenarios No statistics were collected on the staging table. The creation of custom indexes on LAST_UPDATE_DATE columns for tables in this category has been reviewed and 45 . The optimizer estimated the identical run time for both cases execution plans.6 does not disable computing statistics at a table level.3 64bit Test configuration: query involves a large staging table with over 100 Million rows. Tables that have indexes on LAST_UPDATE_DATE columns. The internal tests. In some cases sample cardinality can also be used to estimate table cardinality. but there are no performance implications reported with indexes on LAST_UPDATE_DATE column. Some source tables used by Oracle BI Applications do not have an index on LAST_UPDATE_DATE column. - Custom OBIEE indexes in EBS 11i and R12 systems The first category covers tables. Refer to the publication Oracle Database Performance Tuning Guide (10g Release 2) for more details. Computed statistics on the staging table using DBMS_STATS package. Enabling Dynamic Sampling at the system level may cause additional performance overhead.6 sec Statistics computing: 53 min 26 sec Query Execution Time 2 hours 27 min 45 sec 2 hours 20 min 43 sec The overall run time for the second case was approximately 45 minutes longer compared to the dynamic sampling scenario. To workaround this limitation. mark the task Analyze Table for your staging table as Completed and restart the Execution Plan. Note that the DAC version released with Oracle Business Intelligence Applications Version 7. There are three categories of such source EBS tables: Tables that do not have indexes on LAST_UPDATE_DATE in the latest EBS releases. Tables that cannot have indexes on LAST_UPDATE_DATE because of serious performance degradations in the source EBS environments.9. Statistics / Sampling Execution Time Dynamic sampling: 10.0. which hampers performance of incremental loads.2. which are used by Oracle BI Applications for capturing incremental data changes. so it should be selectively applied only to the mappings.scan a small random sample of the table's blocks.

HZ_CUST_ACCOUNT_ROLES(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> . CREATE index CST.OBIEE_AP_HOLDS_ALL ON AP.AP_PAYMENT_SCHEDULES_ALL(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .9 or lower and it has been migrated to OATM* then replace <IDX_TABLESPACE> with APPS_TS_TX_IDX prior to running the DDL. CREATE index AP. CREATE index AR. replace <IDX_TABLESPACE> with <PROD>X. If your source system is on of the following: EBS R12 EBS 11i release 11.AP_EXPENSE_REPORT_HEADERS_ALL(LAST_UPDATE_DATE) CREATE index AP.approved by Oracle’s EBS Performance Group.OBIEE_HZ_ORGANIZATION_PROFILES ON AR. where <PROD> is an owner of the table which will be indexed on LAST_UPDATE_DATE column.5. CREATE index AR.HZ_CONTACT_POINTS(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .OBIEE_AP_INVOICE_PAYMENTS_ALL ON tablespace <IDX_TABLESPACE> . AP. CREATE index AR. CREATE index AR.OBIEE_HZ_PARTY_SITES ON AR.CST_COST_TYPES(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .OBIEE_HZ_CONTACT_POINTS ON AR.5.OBIEE_AP_PAYMENT_SCHEDULES_ALL ON AP.AP_INVOICE_PAYMENTS_ALL(LAST_UPDATE_DATE) CREATE index AP. CREATE index GL.HZ_ORGANIZATION_PROFILES(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .OBIEE_HZ_CUST_SITE_USES_ALL ON AR.9 or lower and it has not been migrated to OATM*.HZ_PERSON_PROFILES(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .10 EBS 11i release 11.OBIEE_HZ_CUST_ACCT_SITES_ALL ON AR.5. CREATE index AP. CREATE index AP. If your source system is EBS 11i release 11.OBIEE_AP_AE_HEADERS_ALL ON AP. CREATE index AR.OBIEE_AP_EXP_REP_HEADERS_ALL ON AP. All Oracle EBS 11i and R12 customers should create the custom indexes using the DDL script provided below. CREATE index AR.OBIEE_GL_JE_HEADERS ON GL. CREATE index AR.OBIEE_HZ_RELATIONSHIPS ON AR.HZ_LOCATIONS(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .OBIEE_AP_INVOICES_ALL ON AP.HZ_CUST_SITE_USES_ALL(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .AP_AE_HEADERS_ALL(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> . DDL script for custom index creation: CREATE index AP. CREATE index AR. CREATE index AR.HZ_RELATIONSHIPS(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .OBIEE_HZ_PERSON_PROFILES ON AR.HOLDS_ALL(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .OBIEE_CST_COST_TYPES ON CST. tablespace <IDX_TABLESPACE> .GL_JE_HEADERS(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> . HZ_CUST_ACCT_SITES_ALL(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .HZ_PARTY_SITES(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .AP_INVOICES_ALL(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .OBIEE_HZ_CUST_ACCOUNT_ROLES ON AR. 46 .OBIEE_HZ_LOCATIONS ON AR.

5. 47 . In such cases conflicting OBIEE_ indexes should be dropped and Autopatch restarted.10 EBS 11i release 11. where <PROD> is an owner of the table which will be indexed on LAST_UPDATE_DATE column. If your source system is one of the following: EBS R12 EBS 11i release 11. Important: Make sure you use FND_STATS to compute statistics on the newly created indexes and update statistics on newly indexed table columns in the EBS database.PO_DISTRIBUTIONS_N13 ON PO. CREATE index ONT.OE_ORDER_HEADERS_ALL(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .RCV_TRANSACTIONS (LAST_UPDATE_DATE) INITIAL 4K NEXT 2M MINEXTENTS 1 MAXEXTENTS 50 PCTINCREASE 0 INITRANS 2 MAXTRANS 255 PCTFREE 10 tablespace <IDX_TABLESPACE> . Important: Since all indexes in this section have the prefix OBIEE_ and do not follow standard Oracle EBS Index naming conventions.OBIEE_OE_ORDER_HOLDS_ALL ON ONT. CREATE index WSH.CREATE index ONT.RCV_SHIPMENT_LINES (LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> . which have indexes on LAST_UPDATE_DATE.9 or lower and it has not been migrated to OATM*.9 or lower and it has been migrated to OATM* then replace <IDX_TABLESPACE> with APPS_TS_TX_IDX prior to running the DDL. CREATE index WSH.PAY_ELEMENT_TYPES_F (LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .5.RCV_SHIPMENT_HEADERS (LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .5. All Oracle EBS 11i and R12 customers should create the custom indexes using the DDL script provided below.OBIEE_WSH_DELIVERY_DETAILS ON WSH.OE_ORDER_HOLDS_ALL(LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .OBIEE_PAY_INPUT_VALUES_F ON PER. replace <IDX_TABLESPACE> with <PROD>X. Make sure you don't change the index name to avoid any future patch or upgrade failures on the source EBS side.OBIEE_WSH_NEW_DELIVERIES ON WSH. Custom EBS indexes in EBS 11i source systems The second category covers tables.OBIEE_RCV_SHIPMENT_LINES ON PO. CREATE index PER. DDL script for custom index creation: CREATE index PO.OBIEE_OE_ORDER_HEADERS_ALL ON ONT.OBIEE_AR_CASH_RECEIPTS_ALL ON AR. CREATE index PO.RCV_TRANSACTIONS_N23 ON PO. CREATE index PO. CREATE index PO. If you source system is EBS 11i release 11. Autopatch might fail during future upgrades if Oracle EBS introduces indexes on LAST_UPDATE_DATE columns for these tables.WSH_NEW_DELIVERIES (LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .OBIEE_PAY_ELEMENT_TYPES_F ON PER.OBIEE_RCV_SHIPMENT_HEADERS ON PO. CREATE index PER. officially introduced Oracle EBS Release 12.AR_CASH_RECEIPTS_ALL (LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> . CREATE index AR.PAY_INPUT_VALUES_F (LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .PO_DISTRIBUTIONS_ALL (LAST_UPDATE_DATE) INITIAL 4K NEXT 2M MINEXTENTS 1 MAXEXTENTS 50 PCTINCREASE 0 INITRANS 2 MAXTRANS 255 PCTFREE 10 tablespace <IDX_TABLESPACE> .WSH_DELIVERY_DETAILS (LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .

OATM uses 12 locally managed tablespaces across all products.10 releases can migrate to OATM using OATM Migration utility.PO_REQUISITION_HEADERS_N6 ON PO.5. producing heavy inserts / updates into the tables below.PO_REQUISITION_HEADERS_ALL (LAST_UPDATE_DATE) INITIAL 4K NEXT 250K MINEXTENTS 1 MAXEXTENTS 50 PCTINCREASE 0 INITRANS 4 MAXTRANS 255 PCTFREE 10 tablespace <IDX_TABLESPACE> .RA_CUSTOMER_TRX_N14 ON AR.PO_HEADERS_ALL (LAST_UPDATE_DATE) INITIAL 4K NEXT 1M MINEXTENTS 1 MAXEXTENTS 50 PCTINCREASE 0 INITRANS 2 MAXTRANS 255 PCTFREE 10 tablespace <IDX_TABLESPACE> . one for the tables and one for the indexes. Refer to Oracle Metalink Note 248857. Oracle BI Applications customers may consider creating custom indexes on LAST_UPDATE_DATE for these tables only after benchmarking incremental ETL performance and analyzing OLTP applications impact. so introduction of indexes on LAST_UPDATE_DATE may cause additional overhead for some OLTP operations.RA_CUSTOMER_TRX_ALL (LAST_UPDATE_DATE) INITIAL 4K NEXT 4M MINEXTENTS 1 MAXEXTENTS 50 PCTINCREASE 0 INITRANS 4 MAXTRANS 255 PCTFREE 10 tablespace <IDX_TABLESPACE> .PO_LINE_LOCATIONS_ALL (LAST_UPDATE_DATE) INITIAL 4K NEXT 2M MINEXTENTS 1 MAXEXTENTS 50 PCTINCREASE 0 INITRANS 2 MAXTRANS 255 PCTFREE 10 tablespace <IDX_TABLESPACE> . Oracle EBS 11.9 and lower uses two tablespaces for each Oracle Applications product. you can generate an Automatic Workload Repository (AWR) report during the execution of OLTP batch programs. Customers running pre-11.PO_REQ_DISTRIBUTIONS_N6 ON PO. Important: Make sure you use FND_STATS to compute statistics on the newly created indexes and update statistics on newly indexed table columns in the EBS database.PO_REQUISITION_LINES_ALL (LAST_UPDATE_DATE) INITIAL 4K NEXT 250K MINEXTENTS 1 MAXEXTENTS 50 PCTINCREASE 0 INITRANS 4 MAXTRANS 255 PCTFREE 10 tablespace <IDX_TABLESPACE> . CREATE index PO.PO_REQ_DISTRIBUTIONS_ALL (LAST_UPDATE_DATE) INITIAL 4K NEXT 250K MINEXTENTS 1 MAXEXTENTS 50 PCTINCREASE 0 INITRANS 4 MAXTRANS 255 PCTFREE 10 tablespace <IDX_TABLESPACE> . CREATE index PO.5.PO_LINE_LOCATIONS_N11 ON PO. any future upgrades would not be affected.10 and R12 use the new Oracle Applications Tablespace Model. For example.PO_LINES_N10 ON PO. CREATE index AR. Oracle EBS tables with high transactional load The following Oracle EBS tables are used for high volume transactional data processing. respectively. CREATE index PO. To analyze the impact on EBS source database.1 for more details. *) Oracle Applications Tablespace Model (OATM): Oracle EBS release 11. Since all custom indexes above follow Oracle EBS index standard naming conventions.PO_HEADERS_N9 ON PO.5. Indexes on transaction tables are held in a separate tablespace APPS_TS_TX_IDX.PO_REQUISITION_LINES_N17 ON PO. designated for transaction table indexes. The majority of the customers will not have any significant impact on OLTP Applications performance. The old tablespace model standard naming convention for tablespaces is a product's Oracle schema name with the suffixes D for Data tablespaces and X for Index tablespaces. CREATE index PO.CREATE index PO. CREATE index PO. and review 48 .PO_LINES_ALL (LAST_UPDATE_DATE) INITIAL 4K NEXT 4K MINEXTENTS 1 MAXEXTENTS 50 PCTINCREASE 0 INITRANS 2 MAXTRANS 255 PCTFREE 10 tablespace <IDX_TABLESPACE> . the default tablespaces for Oracle Payables tables and indexes are APD and APX.

You can use the same guidelines for creating 49 . Refer to Oracle RDBMS documentation for more details on AWR usage. which can be used by Oracle BI Applications for capturing initial data subsets. Make sure you use the following pattern for creating custom indexes on the listed tables below: CREATE index <Ppod>. You may consider creating custom indexes on CREATION_DATE if your initial ETL extracts a subset of historic data.OBIEE_<Table_Name> ON <Prod>. Prod AP AP AP AP AR AR AR AR BOM BOM CST GL GL GL INV INV ONT PER PO Table Name AP_EXPENSE_REPORT_LINES_ALL AP_INVOICE_DISTRIBUTIONS_ALL AP_AE_LINES_ALL AP_PAYMENT_HIST_DISTS AR_PAYMENT_SCHEDULES_ALL AR_RECEIVABLE_APPLICATIONS_ALL RA_CUST_TRX_LINE_GL_DIST_ALL RA_CUSTOMER_TRX_LINES_ALL BOM_COMPONENTS_B BOM_STRUCTURES_B CST_ITEM_COSTS GL_BALANCES GL_DAILY_RATES GL_JE_LINES MTL_MATERIAL_TRANSACTIONS MTL_SYSTEM_ITEMS_B OE_ORDER_LINES_ALL PAY_PAYROLL_ACTIONS RCV_SHIPMENT_LINES WSH WSH_DELIVERY_ASSIGNMENTS WSH WSH_DELIVERY_DETAILS Custom EBS indexes on CREATION_DATE in EBS 11i source systems Oracle EBS source database tables contain another mandatory column CREATION_DATE.Segment Statistics section for resource contentions caused by custom LAST_UPDATE_DATE indexes.<Table_Name> (LAST_UPDATE_DATE) tablespace <IDX_TABLESPACE> .

consider rebuilding wide tables with over 255 columns and moving the columns with NULLs to the end. Since the unused columns will store NULLs. W_PERSON_D. After rebuilding a wide table make sure all ETL and Query indexes get created as well. Wide tables structure optimization Since the wide dimension tables were designed to consolidate attributes from multiple source databases. Oracle would have to generate recursive calls to dynamically allocate space for the chained rows during their read/write time. 50 . which would use all pre-defined attributes. Oracle does not allocate space to NULL columns at the end of the table. WIDE TABLES WITH OVER 255 COLUMNS PERFORMANCE Introduction Oracle Database supports relational tables with up to 1000 columns. Oracle will allocate another block for the next row-piece.custom indexes on CREATION_DATE columns for improving initial ETL performance after careful benchmarking of EBS source environment performance. Oracle BI Applications physical data model contains several wide dimension tables. The table below shows the comparison statistics for a sample W_ORG_D with 254 and 300 columns: W_ORG_D with 300 columns Time: 186 sec Statistics ---------------------------------------------------------657 recursive calls 0 db block gets 134975 consistent gets 134867 physical reads 0 redo size 382 bytes sent via SQL*Net to client 372 bytes received via SQL*Net from client 2 SQL*Net roundtrips to/from client 6 sorts (memory) 0 sorts (disk) 1 rows processed W_ORG_D with 254 columns Time: 54 sec Statistics ---------------------------------------------------------0 recursive calls 0 db block gets 134888 consistent gets 134864 physical reads 0 redo size 382 bytes sent via SQL*Net to client 372 bytes received via SQL*Net from client 2 SQL*Net roundtrips to/from client 0 sorts (memory) 0 sorts (disk) 1 rows processed Depending on the queries complexity the amount of physical reads also could be much higher for wide tables with more than 255 columns. Even if there is enough free space in a single block. W_SOURCE_D. So. there are very few customers’ implementations. any ‘ALTER TABLE’ command would not resolve the chaining problem. which could have over 255 columns after end user customizations. since the existing tables already have the chained rows. the Oracle will split wide table rows into 255 row-pieces for tables. exceeding 255 columns limit. Important: Optimized wide tables must be created from scratch. The described limitation would have critical impact on Oracle BI Applications Dashboards performance. Though there aren’t any differences in logical wide table structure. so it would not create chained row-pieces. such as W_ORG_D. As the result.

etc. such as number of source databases. A physical standby database must be physically identical to its primary database on a block-for-block basis. Global businesses. environment configuration. created from its backup. The internal benchmarks on a low-range outdated hardware have showed four times faster Redo Apply on a physical standby database compared to ETL execution on a primary database: Step Name Row Count Redo Size ETL SQL time on Primary DB 01:59:31 04:11:07 09:17:19 00:24:31 Redo Apply time 00:10:20 00:16:35 03:16:04 00:08:23 SDE_ORA_SalesProductDimension_Full SDE_ORA_CustomerLocationDimension_Full SDE_ORA_SalesOrderLinesFact_Full W_SALES_ORDER_LINE_F_U1 Index 2621803 4221350 22611530 621 Mb 911 Mb 12791 Mb 610 Mb 51 . hardware specifications. OBIEE does not require write access to BI Applications Data Warehouse for either executing end user logical SQL queries or developing additional contents in RPD or Web Catalog. causing invalid or incomplete results on dashboards ETL runs may result in significant hardware resource consumption. Redo Apply for Physical Standby option synchronizes a Standby Database much faster compared to SQL Apply for Logical Standby. High Availability with Oracle Data Guard and Physical Standby Database Oracle Data Guard configuration contains a primary database and supports up to nine standby databases. A logical standby database has to be open all the times to allow Data Guard to perform SQL updates.ORACLE BI APPLICATIONS HIGH AVAILABILITY Introduction Both initial and incremental data loads into Oracle BI Applications Data Warehouse must be executed during scheduled maintenance or blackout windows for the following reasons: End user data could be inconsistent during ETL runs. each source database incremental volume. As the result. slowing down end user queries The time to execute periodic incremental loads depends on a number of factors. Important: A primary database must run in ARCHIVELOG mode all the times. Data Guard synchronizes a physical standby database with its primary one by applying the primary database redo logs. but it later can be altered to a different structure. Data Guard synchronizes a logical standby database by transforming the data from the primary database redo logs into SQLs and executing them in the standby database. A logical standby database is created as a copy of a primary database. The advantage of a physical standby database is that Data Guard applies the changes very fast using low-level mechanisms and bypassing SQL layers. Data Guard with Physical Standby Database option provides both efficient and comprehensive disaster recovery as well as reliable high availability solution to Oracle BI Applications customers. physical and logical. A standby database is a copy of a production database. There are two types of standby databases. operating 24 hours around o’clock not always could afford few hours downtime. Such customers can consider implementing high availability solution using Oracle Data Guard with a physical Standby database. The standby database can be opened in read-only mode in-between redo synchronizations. The standby database must be kept in recovery mode for Redo Apply. incremental loads may not always complete within a predefined blackout window and cause extended downtime.

SQL> ALTER DATABASE OPEN. with both Primary and Standby databases deployed on the same server. - - - 52 . DBA starts Redo Apply in Data Guard to apply the generated redo logs to the Physical Standby Database. deployed on separate servers. DBA opens Physical Standby Database in read-only mode and starts OBIEE tier: SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL. DBA shuts down OBIEE tier and switches the Physical Standby database into ‘RECOVERY’ mode.Creation Total 29454683 14933 Mb 15:52:28 03:51:22 The target hardware was configured intentionally on a low-range Sun server. are expected to deliver up to 8-10 times better Redo Apply time on a physical standby database. The Physical Standby instance runs in read-only mode during ETL execution on the Primary database. DBA schedules the downtime or blackout window on the Standby database for applying redo logs. The modern production systems with primary and standby database. The diagram below describes Data Guard configuration with Physical Standby database: The primary instance runs in “FORCE LOGGING” mode and serves as a target database for routine incremental ETL or any maintenance activities such as patching or upgrade. compared to the ETL execution time on the primary database. When the incremental ETL load into the Primary database is over. to imitate heavy incremental load.

9 GHz 64Gb Target IBM 9117-570 8 x 1. and so on. They are provided for reference purposes within the context of each specific configuration.0 Adapter Environment configuration: Tier Model CPU RAM Storage 1. Switch OBIEE from Primary to Standby before starting another ETL. ‘FORCE LOGGING’ mode would increase the incremental load time into a Primary database. High Availability Solution to Oracle BI Applications Data Warehouse 2.0.2.6 GHz 8Gb IBM AIX 5.4 ETL Load type: Full Load of two years of historic data.1. various tiers configurations.3 Siebel CRM 8. - Additional considerations for deploying Oracle Data Guard with Physical Standby for Oracle BI Applications: 1. Reliable backup solution ORACLE BI APPLICATIONS ETL PERFORMANCE BENCHMARKS The execution time for each ETL run depends on such factors as hardware specifications.5Tb iSCSI OS Software Source IBM 9117-570 8 x 1.0. Siebel CRM 8. Oracle BI Applications 7. 2.0 / Oracle 10.3. However it offers these benefits: 1. Disaster recovery and complete data protection 3.9.3 Informatica 8.6 SP4 / OBIEE 10. it also requires additional hardware to keep two large volume databases and store daily archived logs.3 Oracle 11. DB tiers loads.7 64-bit 500Gb Local HDD IBM AIX 5.5Tb iSCSI 1. Such deployment results in more complex configuration. since Oracle would logging index rebuild DDL queries. 3. Throughput. ETL run time: 11 hours 26 min The following table contains the execution details for the longest mappings in the full ETL run: Session Name SDE_PartyPersonDimension SIL_ResponseFact_Full Run Time 2:01:37 1:57:28 Success Rows Read Write Throughput. In such configuration the downtime can be minimized to two short switchovers: Switch OBIEE from Standby to Primary after ETL completion into Primary database.6.1.Easy-to-manage switchover and failover capabilities in Oracle Data Guard allow quick role reversals between primary and standby. so customers can consider switching OBIEE from the Standby to Primary.4 64-bit IBM AIX 5.9 GHz 64Gb ETL IBM 9115-505 4 x 1. and before starting Redo Apply into Standby database. source data volumes. rows / sec rows / sec 21294734 3943 4480 32245373 4594 5746 53 . Important!!! The following numbers apply only to the specific hardware configurations and source data sets.1. and then start applying redo logs to the Standby instance. Primary database has to be running in ARCHIVELOG mode to capture all REDO changes.

rows / sec rows / sec 128723375 1459 1496 117891397 2283 2363 68597993 1609 1685 68648978 2339 2884 129439913 4690 7102 117918424 7074 7161 7187362 1757 1783 1740225 523 1697 3076049 955 957 7187362 3142 7704 Oracle BI Applications 7. Oracle EBS 11i10 Enterprise Sales Adapter Environment configuration: Tier Model CPU RAM Storage OS Software 54 .3.6 Ghz PE6850 Intel Xeon CPUs Dell 2 x dual-core 3.1.7 64-bit Informatica 8.1.0.SIL_PartyPersonDimension_Full SDE_ResponseFact SIL_PartyPersonDimension_UpdateCampaignOfferInfo SIL_ActivityFact_Full SDE_ResponseDimension SIL_ResponseDimension_Full SDE_ActivityFact SIL_PartyDimension_Person SIL_RevenueFact_Full SIL_PersonFact_Full SIL_CampaignHistoryFact_Full 1:21:29 0:54:44 0:53:20 0:52:16 0:48:25 0:46:11 0:45:03 0:44:28 0:42:20 0:42:12 0:37:45 21294735 32245373 4109910 10505208 32271503 32271504 10505208 21294734 5626059 9151737 10490109 4657 10334 1416 3395 11753 11909 3948 8100 2251 3671 4711 4696 11959 1397 4426 12509 12318 4728 9877 2923 6740 5867 Oracle BI Applications 7.2.4 Target Dell 2 x quad-core 3.6 SP4 / OBIEE 10.9. Throughput.6.4 Ghz PE2850 Intel Xeon CPUs ETL 4Gb 200Gb Local HDD ETL Load type: Full Load of seven years of historic data.3 64-bit Windows 2003 Windows 2003 Oracle 11.9. The following table contains the execution details for the longest Projects mappings in the full ETL run: Session Name SIL_ProjectCostLine_Fact SIL_ProjectExpLine_Fact SIL_ProjectRevenueLine_Fact SDE_ORA_ProjectRevenueLine SDE_ORA_ProjectCostLine SDE_ORA_ProjectExpLine SIL_ProjectTaskDimension SIL_ProjectRevenueHdr_Fact_Full SDE_ORA_ProjectInvoiceLine_Fact SDE_ORA_Project_Tasks Run Time 24:31:59 14:21:31 11:51:12 8:16:54 7:40:36 4:38:22 1:08:45 0:56:05 0:54:16 0:38:44 Success Rows Read Write Throughput.1.0.6. Oracle EBS R12 Projects Adapter Environment configuration: Tier Source Model Sun E6500 CPU RAM Storage OS Software 16 x 900Mhz UltraSparc 16Tb NetApp Network 32Gb II CPUs Attached Storage (NAS) 16Gb 2Tb Netapp NAS Storage Sun Solaris Oracle EBS R12 / Oracle 9 10.1.

1. Throughput.9.1.2.4 OBIEE 10.4 Target Dell 2 x quad-core 1. rows / sec rows / sec 61076675 1729 3357 44797448 1423 2194 44912891 1428 2204 61076675 2194 2494 44797448 2130 2482 44797448 2910 5363 44912891 3071 3397 44797448 3967 3968 4377020 521 471 6101903 627 783 6101903 997 1494 7128617 911 5690 2519900 419 8630 2620885 664 665 2246234 978 74875 2620886 2186 2170 Oracle BI Applications 7.3.0.3 64-bit Oracle 11. The following table contains the execution details for the longest Sales mappings in the full ETL run: Session Name SIL_SalesInvoiceLinesFact_Full SIL_SalesOrderLinesFact_Full SIL_SalesScheduleLinesFact_Full SDE_ORA_SalesInvoiceLinesFact_Full SDE_ORA_SalesOrderLinesFact_Full PLP_SalesCycleLinesFact_Load_Full SDE_ORA_SalesScheduleLinesFact_Full SIL_SalesBookingLinesFact_Load_OrderLine_Debt PLP_SalesOrderLinesFact_RollupAmt_Update_Full SDE_ORA_SalesPickLinesFact_Full SIL_SalesPickLinesFact_Full PLP_SalesOrderLinesAggregate_Load_Full PLP_SalesInvoiceLinesAggregate_Load_Full SDE_ORA_SalesProductDimension_Full SDE_ORA_SalesCycleLinesFact_HoldDurationExtract SIL_SalesProductDimension_Full Run Time 9:50:02 8:45:51 8:45:08 7:44:06 5:52:47 4:17:19 4:04:34 3:08:54 2:48:34 2:43:05 1:42:34 2:11:12 1:40:52 1:06:16 0:48:23 0:22:17 Success Rows Read Write Throughput. rows / sec rows / sec 82351451 2371 2464 55 .1.0.1.0.3 64-bit Oracle 11. Throughput.86 Ghz 16Gb 1Tb Netapp NAS Storage & ETL PE2950 Intel Xeon CPUs ETL Load type: Full Load of seven years of historic data.6 SP4 / RedHat 3.3.2. Oracle EBS 11i10 Supply Chain Adapter Environment configuration: Tier Source Model Sun E6500 CPU RAM Storage OS Software 16 x 400Mhz UltraSparc 16Tb NetApp Network 20Gb II CPUs Attached Storage (NAS) Sun Solaris Oracle EBS R12 / Oracle 9 10.1.0.86 Ghz 16Gb 1Tb Netapp NAS Storage & ETL PE2950 Intel Xeon CPUs ETL Load type: Full Load of seven years of historic data.Source Sun E6500 16 x 400Mhz UltraSparc 16Tb NetApp Network 20Gb II CPUs Attached Storage (NAS) Sun Solaris Oracle EBS R12 / Oracle 9 10.4 OBIEE 10.7 64-bit / Linux Informatica 8.6. The following table contains the execution details for the longest Supply Chain mappings in the full ETL run: Session Name SIL_APInvoiceDistributionFact_Full Run Time 9:40:13 Success Rows Read Write Throughput.6 SP4 / RedHat 3.4 Target Dell 2 x quad-core 1.7 64-bit / Linux Informatica 8.

56 .9.6. If you observe any performance issues with your Oracle BI Applications implementation.SDE_ORA_APInvoiceDistributionFact_Full SDE_ORA_EmployeeExpenseFact_Full SIL_ExpenseFact_Full SIL_ProductTransactionFact_Full SDE_ORA_ProductTransactionFact_Full SDE_ORA_PartyContactStaging_Full SDE_ORA_PurchaseReceiptFact_Full SDE_ORA_CustomerLocationDimension_Full SDE_ORA_InventoryProductDimension_Full SIL_PurchaseCostFact_Full SDE_ORA_CustomerFinancialProfileDimension_Full SIL_PurchaseScheduleLinesFact_Full SDE_ORA_PurchaseCostFact_Full SIL_PurchaseOrderFact_Full SDE_ORA_PurchaseRequisitionLinesFact_Full SIL_RequisitionLinesCostFact_Full SDE_ORA_PurchaseScheduleLinesFact_Full SDE_ORA_RequisitionLinesCostFact_Full SDE_ORA_PurchaseOrderFact_Full SIL_InventoryProductDimension_Full SIL_PurchaseRequisitionLinesFact_Full SIL_CustomerFinancialProfileDimension_Full SIL_PurchaseReceiptFact_Full 7:55:10 5:17:33 5:12:05 4:37:47 4:20:57 3:06:30 1:58:32 1:32:53 1:31:25 1:17:32 1:09:07 0:59:24 0:52:47 0:52:18 0:37:10 0:31:15 0:30:13 0:26:31 0:26:14 0:22:42 0:19:19 0:18:52 0:18:25 82351451 40789178 40789180 19955307 19955307 27123133 3147105 4224659 5241770 2922581 4678902 2837469 2922581 2859692 2520984 2581337 2837469 2581337 2859692 2620886 2520984 2855450 3147105 2894 2145 2189 1202 1280 2439 450 761 5553 632 1309 803 931 923 1145 1410 1586 1663 1868 1976 2257 2640 2953 4063 2394 2500 1985 3531 8032 2565 915 6138 806 1775 941 1400 1216 1970 1980 2395 2934 2449 2143 2697 2684 3470 CONCLUSION This document consolidates the best practices and recommendations for improving performance for Oracle Business Intelligence Applications Version 7. before implementing the changes in the production environment. make sure you trace various components. and carefully benchmark any recommendations or solutions discussed in this article or other sources.This list of areas for performance improvements is not complete.

Amar Batham. PeopleSoft. This document is not warranted to be error-free.506.A.650.6 Performance Recommendations January 2010 Contributors: Pavel Buynitsky.S. without our prior written permission. Nitin Aggarwal Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores. This document is provided for information purposes only and the contents hereof are subject to change without notice. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document.7000 Fax: +1. Eugene Perkov. All rights reserved. Other names may be trademarks of their respective owners.506. This document may not be reproduced or transmitted in any form or by any means. CA 94065 U. Oracle. nor subject to any other warranties or conditions.9. Oracle. for any purpose. whether expressed orally or implied in law. and Siebel are registered trademarks of Oracle Corporation and/or its affiliates.Oracle Business Intelligence Applications Version 7.650. JD Edwards.com Copyright © 2010. 57 . including implied warranties and conditions of merchantability or fitness for a particular purpose.7200 oracle. Worldwide Inquiries: Phone: +1. electronic or mechanical.