Troubleshoot: confused optimizer

If the Oracle optimizer chooses inefficient execution plans on queries that use MAX or MIN, it is possible that this is bug 5611962.

Need Help?

Fill in these details and I will be in touch as soon as possible.