Does the MaxDB Optimizer fail to decide on the best access path?
If a detailed analysis of the SQL statement shows that MaxDB does not decide on the optimal access path, you should firstly check whether the optimizer statistics correctly reflect the current dataset. When the work load is minimal at the weekend, the statistics should be updated once a week for the tables whose size has changed. Other reasons for an incorrect access path are incorrect MaxDB parameterization or the use of an obsolete Support Package. For more information, see Note 767635. Note 817934 is also available for MaxDB Support for further analysis.
