Professional Documents
Culture Documents
Copyright 2015, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential Internal/Restricted/Highly Restricted
Program Agenda
1
Application
Database
WebLogic Server
Global Single
Data Model
BC4J
UIX 11g
JDBC/SQL Net
HTTP/S
Web Listener
WebLogic JSP
BI Publisher
Edition-Based
Redefinition
Forms
For 12.2, apply the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (MOS ID
1617461.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 consolidated in this
note
Upgrade techstack components to the latest certified levels
Check http://blogs.oracle.com/stevenChan/resource/certifications.html
For background engines via Concurrent Manager, set the Process Stuck parameter to No
Identification of stuck workflows is resource intensive
Start a separate background engine to handle stuck/timed out processes with a low
frequency i.e. once a day
Use deferred activities to improve online response times for flows such as Scheduling, PO
Document Approval, etc.
Verify that runtime tables are partitioned for improved performance and scalability MOS ID:
260884.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
WLS Domain
Admin Server
oacore_cluster 1
oacore_server1
forms_cluster 1
forms_server1
oafm_cluster 1
oafm_server1
forms-c4ws_cluster 1
Forms-c4ws_server1
Use one JVM per 1-2 CPUs (dependent on the CPU speed)
12
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 and Xmx2048M
Setting -Xms and -Xmx to the same value avoids the need for heap memory re-allocation
during runtime
Consider using jstat to monitor and review each of the heap generations for possible tuning
Increase the number of JVMs to scale up for more users with faster GC times.
Each JVM has a smaller Xmx,Xms memory footprint so full GCs will be faster!
13
Managed JVM instances sizing should consider both memory and CPU domains.
On 64bit environment, we do not recommend allocating huge heap sizes, but rather have
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 most
installations, 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 guidance
for 12.2 can be found in the Database and Application Tier Sizing Guidelines section of the
Oracle E-Business Suite Installation Guide: Using Rapid Install (Part No. E22950)
Managing Configuration of Oracle HTTP Server and Oacore, Oafm, Forms and Forms-c4ws
Applications in Oracle E-Business Suite Release 12.2 (MOS ID 1905593.1)
14
Care should be taken to size for the concurrent manager components, especially java
concurrent programs.
Copyright 2015, Oracle and/or its affiliates. All rights reserved. |
15
16
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 profile
17
18
19
20
Edition-Based Redefinition
File System 1
File System 2
Developer 10.1.2
Developer 10.1.2
APPL_TOP
Synchronization managed
by patching tools
COMMON_TOP
INST_TOP
APPL_TOP
COMMON_TOP
INST_TOP
APPL_TOP_NE
PATCH_TOP
LOGS
Copyright 2015, Oracle and/or its affiliates. All rights reserved. |
22
MOS ID 556738.1 - Network Test Utilities Best Practices: Explains how the Network Test form
works and how you interpret the output.
Also explains how to use this with the standard ping command to determine whether you have: a
network latency issue, network congestion problem or a problem with the Applications Tier
Copyright 2015, Oracle and/or its affiliates. All rights reserved. |
MOS ID 967992.1 Symmetrical Network Acceleration with Oracle E-Business Suite R12
Symmetric Network Acceleration already in use within several companies. If you have some form
of compression, then use uncompressed concurrent report formats, otherwise, if bandwidth is a
premium especially over satellites, then consider using PDF output rather than HTML or Excel.
Copyright 2015, Oracle and/or its affiliates. All rights reserved. |
27
(MOS now has a HOT TOPICS feature to be alerted when favorite notes have been updated)
Apply Required Patches & Fixes/Workarounds for Known Issues
Recommended Performance Patches - MOS ID 244040.1
Required Patching Interoperability Notes
Size SGA and PGA memory for maximum projected concurrency levels, buffer cache and shared pool sizing
specially critical
Use Large/Huge pages. For example on Linux Huge Pages See 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 only start if
sufficient Huge Pages are available See MOS ID 1392497.1
Copyright 2015, Oracle and/or its affiliates. All rights reserved. |
28
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_IO MOS ID 727062.1
29
Pin top Apps PL/SQL packages by executions to help avoid shared pool fragmentation and reloads
Check for cursor leaks and SQL statements using literals with large execution counts. Cursor
leaks/literals can result in ORA-4031 errors
Tune cache sizes for hot sequences where possible (e.g. 1,000 or higher) in order to minimize index key
contention for the Apps surrogate keys
Make sure to use FND_STATS to gather statistics
30
31
Use the GATHER_AUTO option to gather incrementally. This will re-analyze objects which
currently have no statistics and objects with stale statistics
32
33
34
35
36
Make sure that the I/O subsystem sized for performance, not just storage; write optimized
Increase the buffer Cache by at least 10%
Top 5 Database and/or Instance Performance Issues in RAC Environment (MOS ID 1373500.1)
RAC and Oracle Clusterware Best Practices and Starter Kit (Platform Independent) (MOS ID 810394.1)
Use Parallel Query Instance Affinity (Set PX affinity local to each node)
From 11gR2 - PARALLEL_FORCE_LOCAL =TRUE
37
38
39
40
Globalization
99%
Performance
Simplified deployments
Increased competitiveness
41
Globalization
Lifecycle
99%
Performance
Platinum services
Fewer variations
42
EBS
Exalogic
VM
Templates
Import into
EM Ops
Center
12.2.3
APP
12.1.3
DB
12.1.3
APP
VM
Customize &
Save VMs
as Gold
Images
VM
3
Instantiate
vServers in
Exalogic
Oracle VM on Exalogic
http://www.oracle.com/technetwork/database/availability/ebs-maa-2158952.pdf
Standard hardware
E-Business Suite
Order to Cash
3x better Response Time
2x better Scalability
E-Business Suite
HR Self Service / Procurement
8x better Response Time
2x better Scalability
Response Time
Response Time
2.23 s
11.94 s
3X
8X
Higher throughput
Push more transactions through a single Exa
core
0.74 s
Linear Scaling
1.42 s
More robust connection harvesting while optimizing resource and connection pool usage on
the middle tier with huge savings on PGA memory requirements on the database for high
concurrency levels
Disable the EBS data source parameter Oracle Enable JavaNet Fastpath, which reduces JDBC data
source connection pool exhaustion & stuck threads
Enable the EBS data source parameter Oracle Optimize UTF8 Conversion, which reduces excessive
and sporadic JDBC connections
Set EBS Profile Options AuditTrail Activate to No and Sign-On: Audit Level to None
56
Allows you to store columns, tables, partitions and materialized views in memory using a
columnar format, rather than the typical row format thereby improving performance when
scanning and/or processing large numbers of rows
This feature results in a Dual-format approach, which maintains data in both the classic
Oracle row format, and a new in-memory column format optimized for analytical
processing
Both formats are simultaneously active and transactionally consistent. The Oracle database
automatically uses the new in-memory column format for analytic queries and the existing
row format for OLTP operations
57
Memory
SALES
SALES
Row
Format
Column
Format
58
Oracle In-Memory Advisor (MOS ID 1965343.1) is also available to identify candidates for InMemory
Queries that scan many rows but only references or accesses a small subset of columns
from a table, partition, or materialized view.
Aggregation based queries that use arithmetic functions such as sum, mean or average.
Grouping based queries that processes data in groups such as 'sales per calendar month',
use buckets, or involves very large tree-walks.
Delete and update statements that are in turn based on sub-queries that perform full table
scans of large tables.
Description
Receiving Transaction
Processor
In-Memory Objects
Baseline Run
OE_ORDER_LINES_ALL
OE_ORDER_HEADERS_ALL
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
RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
195 Secs
In-Memory
Run
18 Secs
51 Mins
13 Mins
10.2 Hours
2.6 Hours
3470
3460
3450
3440
Time (minutes)
3430
50
40
23mins 56sec
30
20
3mins 27sec
10
With 12c
In-memory option
Commodity HW
With 12c
In-memory option
Exadata X4-2
63
64
Active
Less
Active
Low
Volume
Data Volume
Activity
1
Months
available online?
10
Years
65
66
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
67
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
Human
Resources
Alert
Support Notes:
(MOS ID 138264.1) General Ledger Archive/Purge FAQ
Workflow
General
Ledger
Payables
iExpense
(MOS ID 752322.1) : Reducing Your Oracle E-Business Suite Data Footprint using Archiving, Purging, and ILM
68
FNDLGPRG
CSTCSPCT
FNDSCPRG
APXIIPRG
RAXINVPG
POXCDXPG
FNDCPPUR
POXSSPG
PNVPURGE
FNDWFPR
PAYLINK(PURGE)
DELPURTC
FNDLGPRG
CSTCSPCT
FNDSCPRG
APXIIPRG
69
70
Many E-Business Suite tables do not have a natural partitioning key which would apply to all
customers
Based on your own requirements, customers are free to partition the tables in a logical
manner
Copyright 2015, Oracle and/or its affiliates. All rights reserved. |
71
This is a batch queue table. When a user requests a batch job, Oracle inserts a row into the queue. The
Concurrent Managers are processes that periodically query the queue, pick up requests to be run, and
update the requests' statuses
To reduce Real Application Clusters overhead, partition the FND_CONCURRENT_REQUESTS based on
the APPLICATION_ID column. Performance gains will be more visible with higher throughput
72
73
74
Latest news
Certification announcements
Primers, FAQs, tips
Desupport reminders
Latest upgrade recommendations
Statements of Direction
Subscribe by email or RSS
75
Join us on Facebook
76
NOW!
education.oracle.com/streams/ebusinesssuite
Copyright 2015, Oracle and/or its affiliates. All rights reserved. |
77
Additional Resources
79
Additional Resources
Diagnostic Data Collection
Start with MOS ID 1121043.1 for How-to & Best Practices
SQL Tuning
Trace files
PL/SQL Tuning
Product logs
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.1,278868.1)
OS - OSWatcher (MOS ID: 301137.1)
Network Test Utilities Best Practices (MOS ID: 556738.1)
80
Additional Resources
Optimizing 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)
81
Additional Resources
Tuning the Concurrent Manager
1359612.1 Webcast 'E-Business Suite - RAC & Parallel Concurrent Processing
82
Additional Resources
EBS Upgrade and Platform Migration
Best Practices for Minimizing Oracle E-Business Suite Release 12 Upgrade Downtime (MOS ID 1581549.1)
Express Diagnosis of Oracle E-Business Suite Release 12 Upgrade Performance Issues (MOS ID 1583752.1)
R12.1 documentation roadmap (MOS ID 790942.1)
Oracle E-Business Suite Release 12.1 Info center (MOS ID 806593.1)
Oracle Applications Tablespace Model (OATM) Release 11i - Tablespace Migration Utility (MOS ID 248857.1)
Copyright 2015, Oracle and/or its affiliates. All rights reserved. |
83
Additional Resources
EBS Upgrade and Platform Migration
EBS R12.1 Upgrade related Reports
White papers
Planning Your Oracle E-Business Suite Upgrade from Release 11i to Release 12.1 (MOS ID 987516.1)
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 (MOS ID 1901242.1)
84
Additional Resources
E-Business Suite: Archiving & Purging
Archive/Purge Product Information
https://blogs.oracle.com/stevenChan/entry/e_business_suite_technology_learning
85
Additional Resources
Oracle 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.html
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 column stores are populated
on 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 how data is populated.
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
86