Oracle Ebusiness Suite Performance Tuning
The Six Tuning Areas
Upgrade to latest Architecture & Techstack versions to get improved performance, this is especially true for JDBC.
Execute RDA where you find it necessary.
- TUNING THE CLIENT
- For 11i 232833.1
- For R12 405293.1
- For 11i 232833.1
- TUNING THE MIDDLE-TIER
- ONE OR MORE MACHINES?
- THE JAVA VIRTUAL MACHINE
- MAPPING USERS
- ON-DEMAND DOWNLOADING
- APACHE
- FORMS RUNTIME DIAGNOSTICS
- PERFORMANCE COLLECTOR
- ONE OR MORE MACHINES?
- TUNING THE DATABASE
- Performance tuning flow chart 233112.1
- Enhanced Explain Plan Utility 215187.1
- STATSPACK/AWR/ADDM
- COST AND RULE BASED OPTIMIZATION
- MONITORING GROWTH
- BLOCK SIZE AND RELATED SETUP
- PACKAGE PINNING STRATEGY
- SHARED POOL RESERVED ALLOCATION
- LATCHING
- HIT RATIO
- MANAGING THE SYSTEM LOAD
- Partitioning of custom tables 554539.1
- Purging routines should be run on a systematic basis.
- Database Initialization parameters 396009.1
- Performance tuning flow chart 233112.1
- TUNING THE SERVER
- DISK I/O: OFA VS RAW PARTITIONS
- MEMORY BOTTLENECKS
- PAGING AND SWAPPING BOTTLENECKS
- CPU BOTTLENECKS
- DISK I/O: OFA VS RAW PARTITIONS
- TUNING THE SQL ACCESS PATHS
- TRACING MODULES
- ENCAPSULATING SQL
- USING EVENT 10046
- IDENTIFYING LITERAL SQL
- ANALYZING LITERAL SQL
- FINDING DYNAMIC FORM SQL
- HIGH WATER MARKS
- EXPENSIVE SQL
- CUSTOMIZED VIEWS
- TRACING MODULES
- TUNING THE NETWORK
- ISN'T BANDWIDTH ENOUGH?
- PACKET SHAPERS
- QUALITY OF SERVICE
- ANALYZING THE NETWORK
- DIAGNOSTIC TOOLS
- ISN'T BANDWIDTH ENOUGH?
- TUNING CONCURRENT PROCESSING
- MONITORING CONCURRENT PROGRAMS
- ENABLING SQL TRACE
- APPLICATION OR PROGRAM TRACE/DEBUG PARAMETER
- USING THE FDSQLCHK ENVIRONMENT VARIABLE
- ENABLING TRACE FOR A REPORT
- USING ORACLE TRACE
- MONITORING CONCURRENT JOBS USING STANDARD SCRIPTS
- ANALYZING HISTORICAL INFORMATION
- ENHANCING CONCURRENT PROCESSING
- MONITORING CONCURRENT PROGRAMS
- TUNING THE USERS
- QUERYING FORMS
- RECORD RETRIEVAL
- QUERYING FORMS
No comments:
Post a Comment