| Tuning/Indexing Ebusiness suite tables [message #213156] |
Tue, 09 January 2007 12:24  |
Anand Ramaswamy
Messages: 111
Registered: January 2005
|
Senior Member |
|
|
Hi All,
It is about 1 year after EBusiness Suite 11.5.10 implementation in our Organization.
After implementation there were lot of discoverer reports that were designed to be used.
The implementation team(external consultant) created views (Level 1) from Oracle base tables/views and created more views using Level 1 views and so on..
These views were used in Discoverer for showing the reports. Now since database has grown considerably, the reports designed has become too slow (Some of the reports take more than an hour to show).
I have no clue how to make it fast. Is there any particular approach that needs to be followed in this case? Can we index Oracle Tables (Ebusiness suite tables)?
Would appreciate some response for this.
Thanks in advance
qA
|
|
|
|
| Re: Tuning/Indexing Ebusiness suite tables [message #213240 is a reply to message #213156] |
Tue, 09 January 2007 23:58  |
adragnes
Messages: 241
Registered: February 2005
Location: Oslo, Norway
|
Senior Member |
|
|
Anand,
There are several things you can consider such as:
- tuning the queries - use the explain plan to see if you can rewrite them such that they go faster
- materialized views - this basically stores the result of the query in the database so that when you run the report you get the results very quickly.
- partitioning tables - partitioning table can improve performance if you are not interested in all the data when you run the reports, but only subsets
- archive and purge - this reduces the amount of data in the tables, hence speeding the queries, but having to do this after only one year seems a bit too soon.
In some cases you can also add indexes without losing support such as on the GL_CODE_COMBINATIONS table.
--
Aleksander Dragnes
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
