Performance Tuning Overview in Oracle Apps 11i Contd..

This Performance Tuning is an Overview of from where to start if users start complaining
that Oracle Applications is running slow. If you have not read previous post on
Performance Checks on 11i visit
http://becomeappsdba.blogspot.com/2006/09/performance-tuning-apps-11i.html

If performance issue is with entire application questions you should have in mind
Is your applications sized properly ?
Is initialization parameters set up correctly ?
Are there any runaway processes in oracle database tier or application tier ?
Is network connectivity between users & application server is fine , there is no delays ?
Latest techstack including jdbc drivers, forms, database, jdk can improve performance
considerably Check if system level trace is enabled ?
Is Purge schedule ?
Is gather stats scheduled ?

If Issue is with only particular type of reports
Check if there are no performance bugs with that module ?
Are you on latest patchset for that product ?
Is it standard report or custom ? (If custom enable trace & use tkprof, If standard then
check in metalink if there is any issues reported by others)
If Issue is only during particular time lets say during night Check what’s running during that time Is it because of backups ?
Is it because all resource intensive requests running in night ?

If Issue is with specific users Check
if trace is enabled at user level ?
Is user client machine performing well ?
Is connectivity from client machine to server fine ?

This is just overview or starting point to check Performance Issues in Oracle applications
11i for Tuning Individual component like , Apache, JVM, Concurrent manager I’ll post in my
future posts.

One of reader asked how to schedule Gather Stats or How to schedule Purge Concurrent
Program or Obsolete workflow data.
These are concurrent requests & if you have “System Administrator Responsibility” login
with that then go to Request -> View -> Select “Specific Request” and under “Name” Text
Search for following requests
Gather Schema Statistics ( supply parameter schema name , apps & others)
Purge Concurrent Request and/or Manager Data ( supply retention period usually 90 days)Purge Signon Audit data
Purge Obsolete Workflow Runtime Data
Purge Obsolete Generic File Manager Data
If you are not aware of what is concurrent request or how to check don’t worry wait for sometime till we come to sysadmin section & I’ll update what to read & from where to read about Oracle Application Sysadmin related to concurrent requests.

If you want to understand How to proceed with Oracle Applications 11i tuning check Metalink Note 69565.1 A Holistic Approach to Performance Tuning Oracle Applications Systems (Though quite old guide from year 2001 but good for approach)

About the Author Masroof Ahmad

Leave a Comment:

8 comments
Add Your Reply