This content has been marked as final. Show 4 replies
Can we get one of the oracle experts to comment on this being a new issue or something they have seen before?
We don't even know if an 18 hour run is normal for this conversion tool nor do we know if we need to open an SR.
this seams indeed slow,
you might want to do log an SR
if you do , update the thread with the sr nr please
This looks like an issue with the "Calculating the Tablesplit Threshold" step of the scan. This step should be short as it is only there to calculate the optimal scan method. Please, open an SR so that we can look at your configuration in detail.
I found that the initialization parameter in my DB was not set properly. I have changed the following initialization parameter which is a dynamic parameter and the table split step completed in just 1 minute.
optimizer_features_enable = 10.2.0.5
My database was 10.2.0.5 and the value for optimizer_features_enable was set to 9.2.0
Becasue of this parameter the explain plan went for nested loop query rather than going for Hash join.
This caused the performance issue and costed me 8 hrs to calculate the table split threashold.
Now after changing the value the DMU conversion is really fast.