A production AWR report flagged a query with an INDEX FULL SCAN operation consuming significant I/O. The developer assumed it was an index range scan gone wrong. It was not. The optimizer had a reason — and understanding that reason is what separates reactive troubleshooting from deliberate tuning. Tested on: Oracle Database 19c (19.28) · Read more about Oracle Index Full Scan: When and Why It Fires[…]