ebs performance

7/25/2019 Ebs performance

1/87


2/87

Copyright 2015, Oracle and/or its affiliates. All rights reserved. |

Achieving Optimal Performance

with Oracle E-Business Suite

Samer BarakatDirector, Applications Performance Group

Applications Technology Group, Oracle E-Business Suite DevelopmentOctober 26, 2015

Oracle ConfidentialInteCopyright 2015, Oracle and/or its affiliates. All rights reserved. |


3/87


Program Agenda

Optimizing Applications Tier

Optimizing Database Tier

Optimizing E-Business Suite on RAC

Optimizing E-Business (Engineered Systems)

Optimizing E-Business (Database In-Memory)

Optimizing E-Business Data Management

1

2

3

4

5

6


4/87


Client

JDBC

/SQLNet

HT

TP/S

Application Database

RAC & A

Global S

Data Mo

Edition-

Redefin

WebLogic JSP

Forms

BI Publisher

BC4J

WebListener

UIX 11g

WebLogic Server

Optimizing E-Business Suite


5/87


Optimizing E-Business SuiteApplications Tier


6/87


Optimizing E-Business Suite Applications TierStay Current

Keep the system currenton AD/ATG/OAM code e.g. apply latest AD/ATG RUPs. review ETCC compchecker recommendations

Apply the latest EBS Family Packs + Recommended Patch List

Critical EBS patches are also listed in the E-Business Suite 12.2 readme files

For 12.2, review Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technolog(MOS ID 1594274.1). Use the Database and Middle Tier E-Business Business Technology Complia

For 12.2, apply the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 121617461.1)

Apply Recommended Performance Patches for the Oracle E-Business Suite, MOS ID 244040.1

Recommended performance patches for all the modules and tech stack components are consonote

Upgrade techstack components to the latest certified levels

Check http://blogs.oracle.com/stevenChan/resource/certifications.html
http://blogs.oracle.com/stevenChan/resource/certifications.htmlhttp://blogs.oracle.com/stevenChan/resource/certifications.html


7/87


Optimizing E-Business Suite Applications Tier

Use Optimal Logging Settings

As logging and enabling debug messages have considerable impact on performancmake sure that the associated profiles are set properly while keeping logging levelsminimum.

FND: Debug Log Enabled - Set it to Yes (12.0 RUP3+, 12.1.x, 12.2)

FND: Debug Log Level - Set to Unexpected (Level=6)

Query FND_LOG_MESSAGES to check the logging traffic

Note that with above profile configuration If the query shows a large number of rows being created, there are likely to be e

and errors that need to be investigated


8/87



Optimize Workflow Processes

Purge runtime data (Concurrent Program: FNDWFPR)

Can run by ITEM_TYPE

Monitor/Troubleshoot old workflows that are not properly closed

Purge frequently

For background engines via Concurrent Manager, set the Process Stuck paramete

Identification of stuck workflows is resource intensive

Start a separate background engine to handle stuck/timed out processes with a lofrequencyi.e. once a day

Use deferred activities to improve online response times for flows such as ScheduDocument Approval, etc.


9/87Copyright 2015, Oracle and/or its affiliates. All rights reserved. |


Optimize Workflow Processes

Run $FND_TOP/sql/wffngen.sql to translate the activity function calls into static ca

Edit & add heavily used ITEM_TYPES

For example, itemtypelist_t (WFSTD,FNDFFWF)

Generate wffncal2b.pls in utl_file_dir to recreate package.

Disable retention on Workflow Queues

DBMS_AQADM.ALTER_QUEUE(queue_name=>:b1,retention_time=>0);

Verify that runtime tables are partitioned for improved performance and scalabili260884.1

For high volume batch processing in RAC use ITEM_TYPE to Node affinity

Define node affinity at the program level (MOS ID 1129203.1)


10/87Copyright 2015, Oracle and/or its affiliates. All rights reserved. |

Optimizing E-Business Suite Applications TierOptimize Forms Processes

Reduce load on the database server: train applications users to optimally utilize the

Forms interfaces by: Avoiding blind queries with unselective filtering criteria

Providing selective criteria in find windows and LOVs (to enable index use)

Minimize network traffic and form open times: train applications users to

Avoid opening and closing forms across transactions

Combine forms from multiple-products on a single menu

Reducing system load and network overhead, is especially important for deploymenuser concurrency levels and high latency connections

Monitor concurrency levels and system load on the applications tier

Generate complete SQL Trace and Forms Runtime Diagnostics (FRD) to debug perfissues


11/87


From a simplistic point of view,Oracle E-Business Suite is

A handful of web applications

Deployed on clustersof managedservers

Managed by anAdmin Server Deployed within a WebLogic Server

Domain

Size The Middle Tier For Concurrency

WLS Domain

ooacore_cluster 1

fforms_cluster 1

oafm_cluster 1

Forforms-c4ws_cluster 1



12/87


Optimizing E-Business Suite Applications TierSize The Middle Tier For Concurrency (JVM Heaps)

The main contributors to the middle tier memory are theJVMs heaps, forms (frmw

memory and concurrent manager components, especially java concurrent program

To calculate physical memory for the oacore JVM heap, the following formula can b

M= (N/ 150 ) * 1 GB

Where M = total memory used by oacore VMsN = total number of concurrent Self-Service users

Use one JVM per 1-2 CPUs (dependent on the CPU speed)

Aim to have around 100-150 concurrent users per JVM


13/87



Size The Middle Tier For Concurrency (JVM Heaps)

Total available memory is the most important factor affecting GC performance.

Monitor the frequency of collections, especially major collections (i.e. Full GC)

Enable verbose GC to tune heap sizes based on the GC traffic

Start with: -Xms2048M andXmx2048M

Setting -Xms and -Xmx to the same value avoids the need for heap memory re-allduring runtime

Consider usingjstat to monitor and review each of the heap generations for possib

Increase the number of JVMs to scale up for more userswith faster GC times.

Each JVM has a smaller Xmx,Xms memory footprint so full GCs will be faster!


14/87


Size The Middle Tier For Concurrency (JVM Heaps)

Managed JVM instances sizing should consider both memory and CPU domains.

On 64bit environment, we do not recommend allocating huge heap sizes, but rather more managed instances in the cluster to scale up to the target concurrency levels

For 12.2, for Admin Server sizing, the default size of 512MB is not enough for mostinstallations, we recommend setting the XMS to at least 1 GB and the XMX to 2GB

The default sizing is set to 1GB

For 12.2, consider additional sizing requirements for online patching. Initial sizing g

for 12.2 can be found in the Database and Application Tier Sizing Guidelines section oOracle E-Business Suite Installation Guide: Using Rapid Install (Part No. E22950)

Managing Configuration of Oracle HTTP Server and Oacore, Oafm, Forms and FormApplications in Oracle E-Business Suite Release 12.2 (MOS ID 1905593.1)



15/87



Size The Middle Tier For Concurrency (Forms)

To calculate physical memory for Forms frmweb processes, the following formula

uses used:

M= N * 40MB

Where

M = total memory used by Forms frmweb processes

N = total number of concurrent Forms users

40 MB is the average memory used by the frmweb process

Care should be taken to size for the concurrent manager components, especially jconcurrent programs.


16/87


Optimizing E-Business Suite Applications TierOptimize the Concurrent Manager

Manage CM Jobs Lifecycle: 50% of performance tuning is in the business!

Review long-running auto resubmitted jobs to ensure that they are still required

Review jobs that have a huge variance in run time to ensure all users are using separameters

Dont purge jobs that the users then have to run again

Trim the fat: Review and eliminate concurrent jobs that are not required and/orbeing used by users.

Manage CM Managers:More managers/workers != more throughput

Avoid enabling an excessive number of standard or specialized managers.

A common guideline is between 1-2 target process per CPU, but this needs to bewith resources required by online activity

Utilize Parallel Concurrent Processing (PCP) to leverage the Cluster (RAC)


17/87



Optimize the Concurrent Manager

Manage CM Schedules:

Use specialization rules and work shifts to bind specific jobs to specific time windows

Avoid scheduling resource intensive batch requests during peak user/on-line activity

Reschedule some programs to run when the concurrent managers have available capacity

Define Workload Management Strategy based on job average duration and system usage

Manage CM State Data:

Purge the FND tables on a regular basis using the Purge Concurrent Request and Manaprogram

High throughput: Keep *.out and *.log on fast disks. Use separate disks if throughput seeespecially on NFS Filers

Truncate the reports.log file in log directory. Watch for 2GB limit on any output files(MOS ID 842850.1)


18/87


Optimizing E-Business Suite Applications TierOptimize the Concurrent Manager

Manage CM State Data:

Double check the NFS parameters as per MOS ID 1375769.1 and verify if any further tunapplied. Mainly the read and write sizes should be set to at least 64KB

Double check the concurrent manager jobs activities and load on the system. Each concprogram has a parameter, SHELF_LIFE, which can be used to specify how long the logs andfrom the program should be kept.

Optimize log directory access time by reducing the inode file entries. In Oracle E-BusinR12.2,there is a new environment variable, APPLLDM, which was introduced to specify wand out files are stored in a single directory for all Oracle E-Business Suite products, or in subdirectory per product

Check Managing Concurrent Manager Log and Out Directories (MOS ID 1616827.1)


19/87


Optimize the Concurrent Manager: Workload Management Strategy

Avoid Short Sleep Times

*Enough for a couple of minutes of work

**Set cache size to at least twice the number of workers

Specialization rules and work shifts

Bind specific jobs to specific time windows

Profile Option: Concurrent: Active Request Limit can be used restrict the number of concurrethat may be run simultaneously by each user

Specialize if there are too many jobs in a specific category



20/87



Optimize the Concurrent Manager

Conflict Resolution Manager Sleep Time:

To maximize throughput for jobs which spawn parallel workers (i.e. Auto Invoice, Payroll),reducing the sleep time of the Conflict Resolution Manager (CRM)

Default is 60s, consider 5 or 10 seconds

Concurrent Manager Sleep Time:

Define dedicated queues for short and frequent requests and increase the sleep times fowhich do not require near real-time job execution

Reducing sleep time to a very low value many cause excessive CPU utilization

Transaction Manager Sleep Time:

Set the profile Concurrent:Wait for Available TM to 1 (second) to minimize TM latencysets the total time to wait for a TM before switchover to next available TM

Set Sleep time on Transaction Managers to 30 minutes. this avoids constant polls to checshutdown requests.


21/87


Dual File System

Synchronization managed

by patching tools

Edition-Based Redefinition

Non-Editioned File System

Developer 10.1.2

COMMON_TOP

APPL_TOP

INST_TOP

Oracle HTTP Server (OHS)

WebLogic Server (WLS)

File System 1

Developer 1

COMMON_

APPL_TO

INST_TO

Oracle HTTP Serv

WebLogic Serve

File Syste

PATCH_TOP

APPL_TOP_NE

LOGSMore inform

Patching FA

Optimizing E-Business Suite Applications TierOptimize Online Patching Process


22/87


Optimizing E-Business Suite Applications TierOptimize Online Patching Process

Ensure the underlying file IO subsystem is configured properly :

Double check the NFS parameters as per (MOS ID 1375769.1) and verify if any furthebe applied. Mainly the read and write sizes should be set to at least 64KB

Manage online patching load on the system:

Make sure that the number of online patching processes is set properly based on theactivity and number of available CPU cores

Control the number of editions:

As each online patching cycle is completed, the database will accumulate an additiondatabase edition. If the number of these grows too large, system performance will staffected.

When the number of old database editions reaches 20 or more, you should considerold database editions by running the adop actualize_all phase and then performing cleanup


23/87


Network, WAN, and PC Performance Tuningrecorded presentation

https://blogs.oracle.com/stevenChan/entry/e_business_suite_technology_learning

Concepts Manual: Oracle E-Busin

very well with average latencies

and is usually found to give acce

performance with latencies up to

Optimizing E-Business Suite Applications TierOptimize for Network Latencies
http://oukc.oracle.com/static05/opn/login/?t=checkusercookies&r=-1&c=1148110336http://oukc.oracle.com/static05/opn/login/?t=checkusercookies&r=-1&c=1148110336


24/87



Performance Charts for a Range of Latencies and Bandwidths

As seen in the chart, network latency has a visible impact on forms response times.

Reducing forms network traffic by following the guidelines in this presentation will consimprove forms performance under latency constrains.


25/87



MOS ID 556738.1 - Network Test Utilities Best Practices: Explains how the Network Tesworks and how you interpret the output.

Also explains how to use this with the standard ping command to determine whether ynetwork latency issue, network congestion problem or a problem with the Applications


26/87


Riverbed Compression Report


MOS ID 967992.1 Symmetrical Network Acceleration with Oracle E-Business Suite R12

Symmetric Network Accelerationalready in use within several companies. If you haveof compression, then use uncompressed concurrent report formats, otherwise, if bandwpremiumespecially over satellites, then consider using PDF output rather than HTM


27/87


Optimizing E-Business Suite Database T


28/87


Optimizing E-Business Suite Database TierOptimize Database

Tune init.ora Parameters:

Ensure mandatory init.ora parameters are set correctly.

MOS ID 396009.1 & 216205.1 (R12 & 11i respectively)

(MOS now has a HOT TOPICSfeature to be alerted when favorite notes have been upda

Apply Required Patches & Fixes/Workarounds for Known Issues

Recommended Performance Patches - MOS ID 244040.1

Required PatchingInteroperability Notes

Size SGA and PGA memory for maximum projected concurrency levels, buffer cache and shspecially critical

Use Large/Huge pages. For example on Linux Huge PagesSee MOS ID 744769.1

Only SGA allocation benefits from large/huge pages, PGA allocation does not

Set the parameter USE_LARGE_PAGES=only for each instance so that the instance will osufficient Huge Pages are available See MOS ID 1392497.1
https://blogs.oracle.com/stevenChan/entry/be_notified_of_mos_notehttps://blogs.oracle.com/stevenChan/entry/be_notified_of_mos_note


29/87


Optimizing E-Business Suite Database Tier

Optimize Disk I/O

Ensure kernel asynchronous I/O is enabled and supported for the underlying file sy

(if file systems are being used for the DB files)

Configure & verify direct I/O is used (if file systems are being used for the DB files)

Improves performance/scalability by simulating raw devices, avoiding file system cache traffic

Ensure your I/O subsystem can handle your peak I/O load & IOPS

Consider RAID, S.A.M.E. configuration with sufficient spindles

Measure with ORION tool or in 11g

DBMS_RESOURCE_MANAGER.CALIBRATE_IOMOS ID 727062.1

Reduce the I/O workload

Tune expensive SQL

Trim the workload of unnecessary tasks

Do 3X less I/O on average with 11g Advanced Compression Option


30/87



Optimize Backend Code Execution Path

Use PL/SQL Native Compilation

Pin top Apps PL/SQL packages by executions to help avoid shared pool fragmentation an

Check for cursor leaks and SQL statements using literals with large execution counts. Culeaks/literals can result in ORA-4031 errors

Tune cache sizes for hot sequences where possible (e.g. 1,000 or higher) in order to mincontention for the Apps surrogate keys

Make sure to use FND_STATS to gather statistics


31/87



Gather Applications Statistics

Statistics gathering strategy should not be based on time

It should always be based on rate of change in the data and is an iterative process

Disable the 11g automatic job to gather stats

Do not gather statistics excessively on entire schemas or the entire database such anightly or weekly

Do not gather statistics on Global Temporary Tables

Avoid gathering statistics during peak hours

Gather statistics after large data load and when mix/max values have changed


32/87


Optimizing E-Business Suite Database TierGather Applications Statistics

New note MOS ID 1586374.1 for "Best Practices for Gathering Statistics with Oracle

Suite" Use only FND_STATS or the Gather Schema / Table Statistics Concurrent Programs

Do NOT USE the analyze or dbms_stats command directly. It is not supported, anin sub-optimal plans.

When Gather Schema Statistics concurrent program is used fnd_stats does the bofor the run.

FND_STATS supports column histograms.

Histograms can be seeded by calling to fnd_stats.load_histogram_cols.

Use the GATHER_AUTO option to gather incrementally. This will re-analyze objects currently have no statistics and objects with stale statistics


33/87


Optimizing E-Business Suite Database TierGather Applications Statistics

Analyze all schemas at 10%, then for some specific objects use higher sampling x%

Due to data skew, some tables benefit from higher sampling %

From11g, can use value of zero (AUTO_SAMPLE_SIZE)

Do not invalidate cursors

While submitting concurrent request to gather statistics set Invalidate Dependeparameter to No.

Consider locking statistics for very volatile tables once a representative set is gathe For example, interface tables, ap_selected_invoices, wsh_pr_workers etc.

These intermediate tables are used in batch processes.

Use FND_STATS.LOAD_XCLUD_TAB to skip tables as needed.


34/87



Gather Dictionary Stats

Gather dictionary object statistics when there is a significant change in dictionary,

example, lot of new objects created (upgrade, major patching)

exec dbms_stats.gather_dictionary_stats;

Dictionary Statistics should be gathered:

After any associated platform or DB upgrade that is part of the overall Oracle

Business Suite upgrade After the Release 12 upgrade

After moving to OATM


35/87


Gather Fixed Stats

Gather fixed object statistics with reasonable load on the system

exec dbms_stats.gather_fixed_objects_stats

Fixed Object Statistics should be gathered:

After any associated platform or database upgrade that is part of the overalOracle E-Business Suite upgrade

After init.ora parameters have changed

Fixed stats should be collected when there is representative activity on the s

Dictionary and Fixed stats should be gathered manually as they are not gatheredautomatically in the Release 12 upgrade by adstats.sql or any other method.



36/87




37/87


Optimizing E-Business Suite on RACVerify Optimal HW/DB Configurations

Interconnecta Private; GigE or Infiniband

Network ConfigurationUse Jumbo frames for the interconnect

ifconfig mtu 9000

Recommendation for the Real Application Cluster Interconnect and Jumbo Frames (MO

Make sure that the I/O subsystem sized for performance, not just storage; write optimiz

Increase the buffer Cache by at least 10%

Top 5 Database and/or Instance Performance Issues in RAC Environment (MOS ID 1373

RAC and Oracle Clusterware Best Practices and Starter Kit (Platform Independent) (MO

Use Parallel Query Instance Affinity (Set PX affinity local to each node)

From 11gR2 - PARALLEL_FORCE_LOCAL =TRUE


38/87



Utilize Instance Affinity and PCP

Follow recommendation in EBS RAC conversion MOS documents for patch and parame

information Configuring and Managing Oracle E-Business Suite Release 12.2.x Forms and Concurr

for Oracle RAC (MOS ID 2029173.1)

Configuring and Managing Oracle E-Business Suite Release 12.1.x Application Tiers fo(MOS ID 1311528.1)

Use Affinity: Direct some workload components to specific RAC nodes to maximize scalminimizing inter-node communication and synchronization work

Utilize Parallel Concurrent Processing (PCP) to leverage the Cluster (RAC).

Starting from 12.1, you can define node affinity at the program level (MOS ID 112


39/87



Utilize Instance Affinity and PCP

PCP: Maintain 11 correspondence of CM nodes to RAC nodes

Set per CM node to tie to a specific RAC instance.

Do not use a load balanced TNS entry for the value of s_cp_twotask. The request msessions are load balanced.

Define primary/secondary CM nodes for Failover

Extend Affinity to the Applications Tier (Forms)

Set Profile Option "Database Instance" at App or Resp level which can be tied to tw

a service

For 12.1.3, Extend Affinity to the Applications Tier (Self-service)

Set Profile Options App%Agent to web tier hosts configured for specific services

Set Profile Option "Applications Database ID" to node specific DBC file name


40/87


Optimizing E-Business (Engineered Syst


41/87


Instance consolidationGlobalexpansion

Reducedtotal cost of ownership

99%IncreasedcompExecute busines

Improvedprodu

Simplifieddeployments

Rapiddeployments acrossenterprise

Reducedata center footprint

Uninterruptedmbusiness proces

Reducedbusine

Reduced failure

Globalization Performance

Lifecycle Support

Optimizing E-Business (Engineered Systems)Why EBS on Exalogic and ExadataBusiness Value


42/87


IT Infrastructure reduced

All Applications, FMW, DB run ona singleplatform

Easily support largeimplementations

99%Online responseBatch processin

Ability to scalew

Fasterbackups / clones

Reducedpatching downtime

OVM templatedeployment

Platinum servic

Fewer variation

Fully redundant

Globalization Performance

Lifecycle Support

Optimizing E-Business (Engineered Systems)Why EBS on Exalogic and ExadataTechnical Benefits


43/87


Performance and Scalability

Oracle E-Business Suite Characteristics:

Workloads are CPU intensive Requires large SGA and PGA due to high concurrency online workloads

Requires high I/O and low latency for data intensive batch processing

Benefits of deploying Oracle E-Business Suite on Engineered Systems:

Up to 3Xperformance improvements in batchprocessing

Up to 8Xperformance improvements in responsivenessto end user

Large memory capacity of Engineered Systems

Dramatically fasterbackups, cloning and other routine operation tasks

Improved scalabilityallows adding more users and higher transaction volum



44/87


Consolidation | Exadata

With higher performance and throughput and smaller footprint, it becomes possib

the number of instances by aggregating more applications and databases

Resource Manager can help database consolidation in two ways.

Control CPU usage and manage CPU contention through instancecaging

Control disk I/O usage and contention through IORMs inter-database resource p

Configuring and Monitoring Instance Caging (MOS ID 1362445.1)

Master Note for Oracle Database Resource Manager (MOS ID 1339769.1)



45/87


Consolidation | ExaLogic

Mission-critical server virtualization offers a whole new level of consolidation whevirtual machines are sharing a single physical server in order to maximize the utilizhardware, while minimizing associated costs

Exalogic has been engineered to leverage a technique known as Single-Root I/O Vireliminate virtualization overhead and deliver the maximum performance and scala

Oracle E-Business Suite Release 12.1.3 Database Tier and Application Tier Templates for Oracle Exalogic (M

Oracle VM Templates for Oracle E-Business Suite for Exalogic Deployment Guide, Release 12.2.3 (MOS ID 1



46/87


Instantiate

vServers in

Exalogic

12.2.3

DB

12.2.3

APP

Oracle VM on Exalogic

Oracle VM Server Pool

E-Business Suite VM Templates for Exalogic

Download from Oracle E-Delivery

Pre-built, pre-configured Exalogic VM

Templates for E-Business Suite

12.1.3 and 12.2.3

MOS Docs 1499132.1& 1633952.1

Import into

EM Ops

Center

EBS

ExalogicVM

Templates

VM

Save days / weeks in installation and config

12.1.3

DB

12.1.3

APP

1

2

3

VM

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1499132.1&displayIndex=2https://support.oracle.com/epmos/faces/DocumentDisplay?id=163952.1&displayIndex=3https://support.oracle.com/epmos/faces/DocumentDisplay?id=163952.1&displayIndex=3https://support.oracle.com/epmos/faces/DocumentDisplay?id=1499132.1&displayIndex=2


47/87


Maximum Availability

Best practices for deploying Oracle E-Business Suite on Exadata Database Machine availability and disaster recovery have been documented and validated by the AppMAA/Exadata team

Configure EBS using our MAA best practices (MOS ID 986690.1)

Load balanced web and forms servers

Parallel concurrent processing

Oracle RAC and Oracle Data Guard

Oracle Maximum Availability Architecture - MAA

http://www.oracle.com/goto/maa

http://www.oracle.com/technetwork/database/availability/ebs-maa-2158952.pdf

http://www.oracle.com/goto/maahttp://www.oracle.com/technetwork/database/availability/ebs-maa-2158952.pdfhttp://www.oracle.com/technetwork/database/availability/ebs-maa-2158952.pdfhttp://www.oracle.com/technetwork/database/availability/ebs-maa-2158952.pdfhttp://www.oracle.com/technetwork/database/availability/ebs-maa-2158952.pdfhttp://www.oracle.com/technetwork/database/availability/ebs-maa-2158952.pdfhttp://www.oracle.com/technetwork/database/availability/ebs-maa-2158952.pdfhttp://www.oracle.com/goto/maa


48/87


EBS Performance Analysis

Exalogic Hardware Management

Exalogic Software Management

Manage from EBS though tVirtualization, and underlyconsole

Manage EBS and Exalog

health with Dashboards Deploy Exalogic OVM te

scale up and scale down

Discovery and organizat(Forms and CP Servers, A

Maximize productivity wManagement Tools for

Advanced configuration

or between instances Advanced performance

compliance with RUEI

Exalogic Monitoring, MeAlerting

Automatic Exalogic FaulRequest Creation

Optimizing E-Business (Engineered Systems)EBS Monitoring and Management on Exalogic


49/87


Exalogic and Exadata for R12.1.3

E-

HR Self

8x bette

2x bette

Re

811.

E-Business Suite

Order to Cash

3x better Response Time

2x better Scalability

Response Time

2.23 s

0.74 s

Faster Response:

3xFor O2C Forms transactions

8xFor Self Service transactions

Higher productivity for online users

Users per core:

Twiceas many users per core

Headroom for additional loads

Higher throughput

Push more transactions through a single Exacore

Linear Scaling

Support very large deployments with ease

Standard hardware Exa

3X



50/87


Optimizing E-Business (Engineered Systems)Exalogic and Exadata for R12.1.3


51/87


Exalogic and Exadata for E-Business 12.2.x

Oracle Fusion Middleware 11g included

WebLogic Server replaces OC4J

WebLogic Server and Exalogic

Native support for huge pages allowing faster memory access

More robust connection harvesting while optimizing resource and connectio

the middle tier with huge savings on PGA memory requirements on the data

concurrency levels

E-Business Suite OVM templates for Exalogic



52/87


Exalogic and Exadata for 12.2.x

Excellent scalability and response times were achieved based on the results of our internal ben

5000 self service users in full concurrency with 20 managed instances.



53/87



Excellent scalability and response times were achieved based on the results of our internal ben4000 forms users in full concurrency with 20 managed forms instances (servlet mode).



54/87



Additional Application Tier Recommendations:

It is recommended to have OHS state files as well as the shared memory file on local disNFS mount point

When using ExaLogic with ZFS Storage Appliance, Hot Files can easily be found using Advanced Analytics. (MOS ID 1472716.1)

Disable the EBS data source parameter Oracle Enable JavaNet Fastpath, which reducsource connection pool exhaustion & stuck threads

Enable the EBS data source parameter Oracle Optimize UTF8 Conversion, which reduand sporadic JDBC connections

Set EBS Profile Options AuditTrail Activate to No and Sign-On: Audit Level to None



55/87



Additional Database Recommendations:

Ensure the Infiniband MTU is set to 64k

Adjust the result cache setting on the database to a higher value (600MB for 4000 userfree events

Carefully review ETCC compliance checker and apply required patches, as per the follow

(MOS ID 1623879.1)- Interoperability Notes Oracle E-Business Suite Release 12.2 wiDatabase 11g Release 2 (11.2.0)

(MOS ID 1594274.1)- Oracle E-Business Suite Release 12.2: Consolidated List of PatTechnology Bug Fixes

(MOS ID 1392527.1 ) - Database Patches Required by Oracle E-Business Suite on OraSystems: Exadata Database Machines and SuperClusters



56/87


Optimizing E-Business (Database In-Me


57/87



Overview

ORACLE Database 12.1.0.2 introduced a new feature Database In-Memory

Allows you to store columns, tables, partitions and materialized views in memcolumnar format, rather than the typical row format thereby improving perfoscanning and/or processing large numbers of rows

This feature results in a Dual-format approach, which maintains data in botOracle row format, and a new in-memory column format optimized for analytprocessing

Both formats are simultaneously active and transactionally consistent. The Orautomatically uses the new in-memory column format for analytic queries androw format for OLTP operations


58/87


BOTH row and column same table

Simultaneously active atransactionally consiste

Analytics & reporting arcandidates to use new i

column format.

OLTP transactional flowformat.

Memory Memory

SALES SALES

RowFormat

ColumnFormat

Optimizing E-Business (Database In-Memory)Overview


59/87


Memory Configuration: Increase SGA for In-Memory Area



60/87


Candidate Entities: Identify Candidate Query/Tables for the In-Memory L

Run flows with SQL Trace, Generate and review AWRs, ASH reports, identify queries tha

full table scans and find hot table segments Identify large processes, specifically reports and processes that access very large amou

that would benefit from using a columnar format. Typically these will be month/periodjobs or long running reports. For example, Financial Statement Generator reports or FAup reports

SQLs with full table access path (or wide index range scans) with high block reads wouldthe most from In-Memory access.

Indexes that are used as part of the transactional context should not be dropped, as theindexes are crucial for the performance of OLTP online flows

Oracle In-Memory Advisor (MOS ID 1965343.1)is also available to identify candidates fMemory



61/87


When to Use Database In-Memory:

The following types of operations benefit most with the In-Memory columnar format

Queries that scan many rows but only references or accesses a small subset of colufrom a table, partition, or materialized view.

Aggregation based queries that use arithmetic functions such as sum, mean or ave

Grouping based queries that processes data in groups such as 'sales per calendar muse buckets, or involves very large tree-walks.

Delete and update statements that are in turn based on sub-queries that perform fscans of large tables.



62/87


Program Name Description In-Memory Objects Baselin

Order Organizer Form Searching of Orders based on user

entered criteria

OE_ORDER_LINES_ALL

OE_ORDER_HEADERS_ALL

195 Se

Initialize Credit

Summaries

Credit checking in Oracle Quoting

allows the user to determine the

credit worthiness of a customer

while working on a quote.

OE_ORDER_HEADERS_ALL

HZ_CUST_ACCOUNTS

OE_ORDER_LINES_ALL

HZ_CUST_ACCT_SITES_ALL

OE_PRICE_ADJUSTMENTS

HZ_CUST_SITE_USES_ALL

OE_PAYMENTS

RA_INTERFACE_LINES_ALL

OE_PAYMENT_TYPES_ALL

51 Min

Receiving Transaction

Processor

RCVTP processes pending or

unprocessed receiving transactions

RCV_HEADERS_INTERFACE

RCV_TRANSACTIONS_INTERFACE

10.2 Ho

Optimizing E-Business (Database In-Memory)Database In-Memory Sample Results :

New published whitepaper (MOS ID 2025309.1): Using Oracle Database In-Memory wBusiness Suite


63/87


Significant performance gains with Oracle 12c

Database In-Memory option

Achieved 145xfaster performance with 12cDatabase In-Memory option on commodityhardware

Achieved over 1003xfaster performance with 12cDatabase In-Memory option on Exadata X4-2

Database In-Memory: In-Memory Cost Management

From 58hrs to 3mi

23mins 56se

EBS Cost Rollup

without 12C

In-memory option

With 12c

In-memory opt

Commodity H

Time

(minutes)

10

20

30

40

50

3470

3460

3450

3440

3430

58 hours (3460 mins)



64/87


Optimizing E-Business Data Manageme


65/87


Low

Volume

HighVolume

Activity

D

ataVolume

Active

Less

Active

0 1 1 5 10

Months Years

FACT: More than 80% of data is inactive

From Day 0 data starts to grow

Data comes from many sources

Transactional e.g. Orac

Transient data (e.g. log

requests etc..)

Reference/Seeddata e

Is all this data needed or requir

available online?


What Do We Know About Data


66/87


Optimal Data Management

Reduced hardware cost

Reduced backup time

Reduced upgrade time and associateddowntime

Increased Transactions Per Second (TPS)

Improved operating performance

Reduced Total Cost of Ownership (TCO)

Available Oracle Solution

Data Growth Control Methods

Archive/Purge Functionality

E-Business Suite

Data Management Methods

Database Partitioning

Database Compression

Information Lifecycle Manag

These methods can be used together


Data Management


67/87



E-Business Suite: Archiving & Purging

Where possible try to utilize the standard Oracle supplied

programs Purge/Archive programs provided at the module level in the E-Business

Suite

Many documented standard programs available (260 purge and archiveprograms in R12)

Purge Portal

Purge Portal introduced in 11i10

Single purge/archive management console

Purge programs can be configured, initiated and monitored

Set the execution frequency as well as view history of purge programs

Accessing the Purge Portal

System Administration > Oracle Applications Manager >Purging/Critical Activities
https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=406982.1https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=406982.1


68/87



E-Business Suite: Archiving & Purging

E-Business Suite provides Purge/Archive solutions for the key transactional entities

The native E-Business Suite purge and archive programs are synchronized with the data model

Oracles solution considers cross-product dependencies

Example: We cant simply delete data in Oracle Payables

Archive/Purge Product Information

Product User guidesGL/AP/AR/FA/OM

Support Notes:

(MOS ID 138264.1)General Ledger Archive/Purge FAQ

(MOD ID 144431.1)Fixed Assets Archive/Purge FAQ

(MOS ID 136919.1)General Ledger Archive/Purge Setup and Usage

(MOS ID 752322.1) : Reducing Your Oracle E-Business Suite Data Footprint using Archiving, Purging, and ILM

Payables

Human

Resources

Workflow


69/87


Optimizing E-Business Data ManagementE-Business Suite: Examples: Purge Programs

Purge Debug Log FNDLGPRG

Purge Cost Information CSTCSPCT

Purge Signon Audit data FNDSCPRG

Payables Open Interface Purge APXIIPRG

Purge Invoice Extract Output Table RAXINVPG

Catalog Data Purge POXCDXPG

Purge Concurrent Request/Manager Data FNDCPPUR

Purge System Saved Requisition POXSSPG

Purge Interface Tables PNVPURGE

Purge Obsolete Workflow Runtime Data FNDWFPR

BEE Batch Process (Purge) PAYLINK(PURGE)

Delete/Purge Timecards (OTL) DELPURTC

Purge Debug Log FNDLGPRG

Purge Cost Information CSTCSPCT

Purge Signon Audit data FNDSCPRG

Payables Open Interface Purge APXIIPRG


70/87


Optimizing E-Business Data ManagementE-Business Suite: Partitioning

When?

Many times it will be an implementation decision driven by huge data volume

Can be physical data model decision to improve performance

Situations where partitioning can help

Large deletes could become simple truncates of a partition

Re-population/refreshing of large portions of data could become a partition exchan

Very large tables & their indexes can be split into smaller segments, reducing I/O

Partition Key

Should be a key that most statements will have in the WHERE clause to reap the bepartition pruning & elimination as well as index I/O (local index)

Data should not change often to avoid row-movement between partitions


71/87


Optimizing E-Business Data ManagementE-Business Suite: Partitioning

E-Business Suite Release 12 is certified with the Oracle Database 11g Partitioning

(MOS ID 554539.1) Database Partitioning for Oracle E-Business Suite The Oracle E-Business Suite uses partitioning out-of-the-box with few modules:

200+ tables

Tables have a natural and logical partition key

Majority of the runtime access path (of the standard product) is based on this napartition key

Changing out of the out of the box partitioned tables is not supported.

Many E-Business Suite tables do not have a natural partitioning key which would apcustomers

Based on your own requirements, customers are free to partition the tables in a manner


72/87



This is a batch queue table. When a user requests a batch job, Oracle inserts a row into Concurrent Managers are processes that periodically query the queue, pick up requestsupdate the requests' statuses

To reduce Real Application Clusters overhead, partition the FND_CONCURRENT_REQUEthe APPLICATION_ID column. Performance gains will be more visible with higher throug

FND_CONCURRENT_REQUESTS table partitioning


73/87


Optimizing E-Business Data ManagementApplication Data Purge/Archive and Custom Partition


74/87



E-Business Suite: Advanced Compression (ACO)

Advanced Compression (ACO) option is an ideal choice for saving space with read-intenoperations and can reduce the associated Disk I/O. ACO reduces storage requirement b

In our benchmarks, online workload showed up to 30% improvement with up to 6% inconsumption

As for the batch programs, Order-to-Cash batch runtime increased by only 0.43%, whileprocess runtime reduced by 17% with additional 3.7% CPU usage

Oracle E-Business Suite Release 12.1 with Oracle Database 11g Advanced Compression [MOS I


75/87


E-Business Suite Technology Stack Blog

Direct from EBS Development

Latest news

Certification announcements

Primers, FAQs, tips

Desupport reminders

Latest upgrade recommendations

Statements of Direction

Subscribe by email or RSS

blogs.oracle.com/stevenchan


76/87


E-Business Suite: System Management

Join us on Facebook

facebook.com/groups/EBS.SysAdmin


77/87


Preview the Learning Stream

NOW!education.oracle.com/streams/ebusinesssuite

OracleE-Business Suite Learning StreamKeep Your Skills Current through Continuous Learning

Oracle Confidential

Expert DeliveredAccess to 300+ instructional videos delivered by Oracle

subject matter experts

Training Across the Entire E-Business SuiteFor professionals of all experience levels looking toregularly broaden and deepen their knowledge

Continuously Refreshed ContentCovers technical and functional aspects of Oracle E-Business Suite solutions

Request Topics that Interest YouSubscription Service


78/87


Questionsand Answers


79/87


Additional Resources


80/87


Diagnostic Data Collection

Start with MOS ID 1121043.1 for How-to & Best Practices

SQL Tuning

Trace files

SQLT output (MOS ID: 215187.1)

Trace Analyzer (MOS ID: 224270.1)

AWR Report (MOS ID: 748642.1)

11g SQL Monitor Report

AWR SQL Report (awrsqrpt.sql)

PL/SQL Tuning Product logs

PL/SQL Profiler (MOS ID: 808005.1)

Reports Tracing (MOS ID: 111311.1)

Database Tuning

AWR Report (MOS ID: 748642.1) ADDM report (MOS ID: 250655.1)

Active Session History (ASH)

Forms Tuning

Forms Tracing (MOS ID: 373548.1)

FRD Log (MOS ID: 445166.1)

Generic note (MOS ID: 438652.1)

Middle tier Tuning

JVM Logs

JVM Sizing/Tuning (MOS ID: 362851

OS - OSWatcher (MOS ID: 301137.1)

Network Test Utilities Best Practices (MO

Additional Resources


81/87


Additional ResourcesOptimizing E-Business Suite Database Tier

1121043.1 Collecting Diagnostic Data for Performance Issues in Oracle E-Business Suite

1362660.1 Enhanced Performance Diagnostics for Oracle E-Business Suite Release 12.1.3

301137.1 OSW Document

461053.1 OSWg Document

215187.1 SQLTXPLAIN (SQLT)

224270.1 Trace Analyzer (TRCA)

39817.1 Interpreting Raw SQL_TRACE files

280391.1 How to Retrieve SID Information For a Running Request


82/87


Additional ResourcesTuning the Concurrent Manager

1359612.1 Webcast 'E-Business Suite - RAC & Parallel Concurrent Processing

1367676.1 Webcast 'E-Business Suite - Concurrent Manager Performance

164085.1 Enhancing and Automating Oracle Applications Concurrent Processing

1057802.1 Best Practices for Performance for Concurrent Managers

1304305.1 E-Business Concurrent Processing Information Center

2029173.1 Configuring and Managing Oracle E-Business Suite Release 12.2.x Forms and ConcurrOracle RAC

1311528.1 Configuring and Managing Oracle E-Business Suite Release 12.1.x Application Tiers fo


83/87


Additional ResourcesEBS Upgrade and Platform Migration

Best Practices for Minimizing Oracle E-Business Suite Release 12 Upgrade Downtime (MOS ID 15

Express Diagnosis of Oracle E-Business Suite Release 12 Upgrade Performance Issues (MOS ID 15

R12.1 documentation roadmap (MOS ID 790942.1)

Oracle E-Business Suite Release 12.1 Info center (MOS ID 806593.1)

Database preparation guidelines for R12.1 upgrade (MOS ID 761570.1)

Patching FAQs (MOS ID 459156.1, 225165.1)

Staged or shared APPL_TOP and distributed AD (MOS ID 734025.1, 384248.1, 236469.1)

OAM Patch Wizard overview and FAQ (MOS ID 976188.1, 976688.1)

AD Command Line Options for Release R12 (MOS ID 1078973.1)

Recommended Performance Fixes (MOS ID 244040.1)

R12 Upgrade Sizing & Best Practices (MOS ID 399362.1)

Oracle Applications Tablespace Model (OATM) Release 11i - Tablespace Migration Utility (MOS I


84/87


Additional ResourcesEBS Upgrade and Platform Migration

EBS R12.1 Upgrade related Reports

EBS 12.1.3 Data Model Comparison Report (MOS ID 1290886.1)

EBS ATG Seed Data Comparison Report (MOS ID 1327399.1)

EBS File Comparison Report (MOS ID 1446430.1)

EBS pre-install patches Report (MOS ID 1448102.1)

White papers

Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 (MOS ID 987

R12 Upgrade considerations by product: Financials (MOS ID 889733.1)

Oracle E-Business Suite Upgrades and Platform Migration (MOS ID 1377213.1)

Oracle E-Business Suite Release 12.2 Information Center - Upgrade (MOS ID 1583158.1)

Script to Diagnose adop and Other AD-TXK Issues in Oracle E-Business Suite Release 12.2 (M


85/87


Additional ResourcesE-Business Suite: Archiving & Purging

Archive/Purge Product Information

Product User guidesGL/AP/AR/FA/OM

Support Notes:

(MOS ID 138264.1)General Ledger Archive/Purge FAQ

(MOD ID 144431.1)Fixed Assets Archive/Purge FAQ

(MOS ID 136919.1)General Ledger Archive/Purge Setup and Usage

(MOS ID 752322.1): Reducing Oracle E-Business Suite Data Footprint

E-Business Suite: Technology Learning

https://blogs.oracle.com/stevenChan/entry/e_business_suite_technology_learning

Additi l R
https://blogs.oracle.com/stevenChan/entry/e_business_suite_technology_learninghttps://blogs.oracle.com/stevenChan/entry/e_business_suite_technology_learning


86/87


Additional ResourcesOracle Database In-Memory with Oracle E-Business Suite

(MOS ID 2025309.1): Using Oracle Database In-Memory with Oracle E-Business Suite

Oracle Database In-Memory White Paper on Oracle Database In-Memory

http://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633

Oracle Optimizer blog: https://blogs.oracle.com/In-Memory/

Oracle Database In-Memory on RAC - Part I: This article starts with background information on how the IM columnon Oracle RAC and then discusses how to manage parallelization.

https://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_on

Oracle Database In-Memory on RAC - Part 2: This article explains how Oracle RAC services can be used to control h

https://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_on1

Oracle Database In-Memory on RAC - Part 3: This article reviews the DUPLICATE and DUPLICATE ALL sub-clauses.

https://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_on2

The Oracle Database In-Memory Advisor (MOS ID 1965343.1)

Oracle Database In-Memory Advisor Best Practices white paper:

http://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdf
http://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633.htmlhttps://blogs.oracle.com/In-Memory/https://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_onhttps://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_on1https://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_on2http://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdfhttp://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdfhttp://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdfhttp://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdfhttp://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdfhttp://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdfhttp://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdfhttp://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdfhttp://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdfhttp://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdfhttp://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdfhttp://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdfhttps://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_on2https://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_on2https://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_on2https://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_on1https://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_on1https://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_on1https://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_onhttps://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_onhttps://blogs.oracle.com/In-Memory/entry/oracle_database_in_memory_onhttps://blogs.oracle.com/In-Memory/https://blogs.oracle.com/In-Memory/https://blogs.oracle.com/In-Memory/http://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633.htmlhttp://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633.htmlhttp://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633.htmlhttp://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633.htmlhttp://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633.htmlhttp://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633.htmlhttp://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633.htmlhttp://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633.htmlhttp://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633.htmlhttp://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633.htmlhttp://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633.htmlhttp://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633.htmlhttp://www.oracle.com/technetwork/database/in-memory/overview/twp-oracle-database-in-memory-2245633.html


87/87

ebs performance

Documents