working slow due to partitions added

[PSoni]

hi all,
we are using Oracle 8.1.7 / Form 6i
on W2K server.
We are using Commercial package for steel manufacturing industry.


We have added new partitionas on our transaction tables. Since then, users are complaning that slow working in making new transactions and running reports.
our partitions are based on two columns
1. company varchar2(2)
1. transaction_date

partition is

value less then ('company code ',yearenddate)

what could be reason for bewing slow of working.

[davey23uk]

do a 10046 level 8 trace to see the execution plan and see what you are waiting on.

Stats up to date?

[slimdave]

How many transactions do you have? Local or global indexes? Just insert that's slow, or select/update/delete also?

[marist89]

Analyze the tables after adding partitions?

[abhaysk]

Originally posted by slimdave
Local or global indexes?

Does this matter for transactions to get slow? (in the sense global/local.. all it matters is number of indexes)

[mike9]

• - How many partitions did you have before adding the new one?
  - How do you access this table (fts/index)?
  - Which is the exacte definitions of the indexes of this table?
  - Why are you using ('company code ',yearenddate) as partitioning key? Are you sure that this makes sense and did you really understand the concept of "Multicolumn Partitioning Keys"?

[reydp]

Originally posted by mike9

• - Why are you using ('company code ',yearenddate) as partitioning key? Are you sure that this makes sense and did you really understand the concept of "Multicolumn Partitioning Keys"?

I believe this is the closest answer. It's like creating a bitmap index on a high-cardinality columns or even worst.