Index full scan min/max scans returning wrong results on partitioned tables
A developer has recently shown me an interesting wrong results issue in one of our 12.1.0.2 databases. Having investigated it, I identified the root cause of that issue and constructed a simple test case that can be used to reproduce it.