Hi folks,
I have a report that runs a complicated query against the Oracle
Inventory Application MTL_MATERIAL_TRANSACTIONS table. This table is the
heart of the Inventory Application and gathers all the transactions
(receipts and issues) that go on. Accordingly it grows very large w=very
quickly. Performance of the report was not noticeably bad in
development. However, the number of rows in the table was low. Now the
table has reached only 40,000 rows in TEST and performance has already
become unacceptable.
My approach is to look at the complicated report queries and functions
and run the query against Explain PLan. It must be doing a full table
scan. I also will look at optimizing the report by creating special
indexes for it. Despite all that, I am not optimistic about the future
of this report. My ultimate approach is to create a data warehouse which
gets nightly downloads from MTL_MATERIAL_TRANSACTIONS and the report can
run against this, thus not affecting On-Line performance.
Are there any other areas that I could look at ?
Suggestions welcome...
TIA
Dermot Nolan
Received on Mon Apr 13 1998 - 14:19:14 CDT
