Wednesday, July 18, 2007

Performance Tuning Overview in Oracle Apps 11i

This Performance Tuning is an Overview of from where to start if users start complaining that Oracle Applications is running slow.

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 applications11i for Tuning Individual component like , Apache, JVM, Concurrent manager.

One of the common questions asked is how to schedule Gather Stats or How to schedule Purge ConcurrentProgram 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"

TextSearch for following requestsGather Schema Statistics ( supply parameter schema name , apps & others)Purge Concurrent Request and/or Manager Data ( supply retention period usually 90 days)Purge Signon Audit dataPurge Obsolete Workflow Runtime DataPurge Obsolete Generic File Manager Data.

If you want to understand How to proceed with Oracle Applications 11i tuning check Metalink Note 69565.1 .

No comments: